Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-8767

Jenkins failures due to "Could not get lock /var/lib/dpkg/lock"

    XMLWordPrintableJSON

Details

    • ghx-label-1

    Description

      The rat-check-ub1604 Jenkins job recently failed due to the following issue:

      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

      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.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. IMPALA-8115 some jenkins workers slow to do real work due to dpkg lock conflicts

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. IMPALA-9319 Automate keeping build images up to date on jenkins.impala.io

          • Major - Major loss of function.
          • Open

          Activity

            People

              laszlog Laszlo Gaal
              stakiar Sahil Takiar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: