You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Laszlo Gaal (Jira)" <ji...@apache.org> on 2020/01/22 21:03:00 UTC

[jira] [Resolved] (IMPALA-8767) Jenkins failures due to "Could not get lock /var/lib/dpkg/lock"

     [ https://issues.apache.org/jira/browse/IMPALA-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Laszlo Gaal resolved IMPALA-8767.
---------------------------------
    Fix Version/s: Not Applicable
       Resolution: Fixed

This job runs on a stock Ubuntu AMI published by the Ubuntu project, pulled directly from the Ubuntu account.
The Ubuntu project publishes an AMI locator at http://cloud-images.ubuntu.com/locator/ec2/. 
I updated the base AMI for this job to the most recent found in the locator service, making the autoupdate process a lot faster.

I will create another Jira to track the effort of automating all this housekeeping activity and link it here.

> Jenkins failures due to "Could not get lock /var/lib/dpkg/lock"
> ---------------------------------------------------------------
>
>                 Key: IMPALA-8767
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8767
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>            Reporter: Sahil Takiar
>            Assignee: Laszlo Gaal
>            Priority: Major
>              Labels: broken-build
>             Fix For: Not Applicable
>
>
> The rat-check-ub1604 Jenkins job recently failed due to the following issue:
> {code}
> 01:33:27 + sudo apt-get -qq update
> 01:33:30 + sudo apt-get -qq --yes install git python
> 01:33:30 E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
> 01:33:30 E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
> 01:33:30 + rm -rf /home/ubuntu/tmp.JeHAki5H1s
> 01:33:30 Build step 'Execute shell' marked build as failure
> 01:33:30 Set build name.
> 01:33:30 New build name is '#8717 master'
> 01:33:32 Finished: FAILURE
> {code}
> It looks like the job got unlucky and ran at the same time as another process was running apt-get. Only seen once so far, but tracking here in case it happens more often.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)