Uploaded image for project: 'Server Deployments and Scale'
  1. Server Deployments and Scale
  2. SCALE-79

core dependencies install fails due to unattended-upgrades running

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • master
    • Azure Templates
    • None
    • Severity 3 - Minor

      Issue Summary

      When attempting to bring up a new Jira node using Azure Marketplace template (link) there's an error when installing core dependencies.

      On the client who reported the error, they are running Ubuntu and it seems to be running unnatended-upgrades, blocking dpkg.

      As the source image gets older, the OS may require more and more upgrades, increasing the time required to be available for new installation.

      Info on unnatended-upgrades: https://linuxhint.com/enable-disable-unattended-upgrades-ubuntu/

      I believe adding a sleep or retry mechanism for the installations on prepare_install.sh:

        # Packages done on different lines as yum command will fail if unknown package defined. Some future proofing.
        pacapt install --noconfirm cifs-utils
        pacapt install --noconfirm curl
        pacapt install --noconfirm rsync
        pacapt install --noconfirm netcat
        pacapt install --noconfirm jq
      

      This is reproducible on Data Center: Not consistent.

      Steps to Reproduce

      1. Attempt to bring up Jira using Azure Template from Azure Marketplace.

      Expected Results

      Deployment installs core dependencies and proceed to next steps.

      Actual Results

      After a single failure at each install attempt, deployments fails.

      The below exception is thrown in the log file:

      VM has reported a failure when processing extension 'jira-install-script'.
      Error message: "Enable failed: failed to execute command: command terminated with exit status=1
      [stdout] ./prepare_install.sh: line 87: yum: command not found
      --2022-09-02 12:58:56-- https://github.com/icy/pacapt/raw/ng/pacapt Resolving github.com (github.com)... 140.82.114.3
      Connecting to github.com (github.com)|140.82.114.3|:443... connected.
      HTTP request sent, awaiting response... 302
      Found Location: https://raw.githubusercontent.com/icy/pacapt/ng/pacapt [following]
      --2022-09-02 12:58:56-- https://raw.githubusercontent.com/icy/pacapt/ng/pacapt
      Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.108.133, 185.199.109.133, 185.199.110.133, ...
      Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.108.133|:443... connected.
      HTTP request sent, awaiting response... 200 OK Length: 57765 (56K) [text/plain] Saving to: '/usr/local/bin/pacapt' 0K .......... .......... .......... .......... .......... 88% 47.0M 0s 50K ...... 100% 41.4M=0.001s 2022-09-02 12:58:56 (46.3 MB/s)
      - '/usr/local/bin/pacapt' saved [57765/57765]
      
      E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
      E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
      E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
      E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
      E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
      E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
      E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
      E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
      E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
      E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
      [install_core_dependencies]: Error downloading core dependencies! [stderr] " More information on troubleshooting is available at https://aka.ms/VMExtensionCSELinuxTroubleshoot
      

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available.

              Unassigned Unassigned
              a3c7c2a06f95 Filipi Lima
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: