[Bionic] Unable to deploy BIonic via MAAS due to kernel dependency issues

Bug #1751111 reported by Jeff Lane 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I'm trying to deploy Bionic on a MAAS node today and this is failing with the following dependency errors in the logs. The node in question is booting in EFI mode with Secure Boot enabled.

curtin: Installation started. (17.1-11-ga4c9636b-0ubuntu1~16.04.1)
third party drivers not installed or necessary.
Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Get:3 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [65.5 kB]
Hit:4 http://archive.ubuntu.com/ubuntu bionic-security InRelease
Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1016 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [8526 kB]
Get:7 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [151 kB]
Fetched 9994 kB in 11s (902 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-signed-generic : Depends: linux-signed-image-generic (= 4.15.0.10.11) but it is not going to be installed
                        Depends: linux-headers-generic (= 4.15.0.10.11) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Unexpected error while running command.
Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmp64l_1ty8/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', '--option=Dpkg::options::=--force-unsafe-io', '--option=Dpkg::Options::=--force-confold', 'install', 'linux-signed-generic']
Exit code: 100
Reason: -
Stdout: ''
Stderr: ''
curtin: Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'curthooks']
Exit code: 3
Reason: -
Stdout: Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
        Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
        Get:3 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [65.5 kB]
        Hit:4 http://archive.ubuntu.com/ubuntu bionic-security InRelease
        Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1016 kB]
        Get:6 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [8526 kB]
        Get:7 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [151 kB]
        Fetched 9994 kB in 11s (902 kB/s)
        Reading package lists...
        Reading package lists...
        Building dependency tree...
        Reading state information...
        Some packages could not be installed. This may mean that you have
        requested an impossible situation or if you are using the unstable
        distribution that some required packages have not yet been created
        or been moved out of Incoming.
        The following information may help to resolve the situation:

        The following packages have unmet dependencies:
         linux-signed-generic : Depends: linux-signed-image-generic (= 4.15.0.10.11) but it is not going to be installed
                                Depends: linux-headers-generic (= 4.15.0.10.11) but it is not going to be installed
        E: Unable to correct problems, you have held broken packages.
        Unexpected error while running command.
        Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmp64l_1ty8/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', '--option=Dpkg::options::=--force-unsafe-io', '--option=Dpkg::Options::=--force-confold', 'install', 'linux-signed-generic']
        Exit code: 100
        Reason: -
        Stdout: ''
        Stderr: ''

Stderr: ''

Jeff Lane  (bladernr)
tags: added: hwcert-server
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1751111

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: bionic
Revision history for this message
Jeff Lane  (bladernr) wrote :

Marking this as Invalid. I've tried a few more times and have been unable to reproduce this myself, so I'm going to chalk it up to "incompatible bit-registration operators" (Per the BOFH excuses generator).

If this happens again, I'll revisit it at that time, but for now, the issues seem resolved. They incompatible bit-registration operators
may also have been related to some equipment reboots occurring upstream too.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
tags: added: kernel-da-key
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.