[1.9] Unable to install 14.04, shim.efi.signed renamed

So, the reason the suggested workaround doesn't work is because this file is extracted from a copy of the package which is downloaded on the fly by /usr/lib/python2.7/dist-packages/provisioningserver/boot/uefi.py

On line 146, you need to change shim.efi.signed to shimx64.efi.signed to reflect the file's updated name/location in the shim-signed package. You then either need to restart maas services or reboot so that bytecode (pyc) is refreshed/recompiled.

/usr/lib/python2.7/dist-packages/provisioningserver/boot/uefi.py is part of maas-provisioning-server

HTH

I should correct myself, the package name where the .py file resides is actually python-maas-provisioningserver

Hi John,

There's a patch attached which you can apply to resolve this issue. We are working to get this SRU'd.

Thanks!

Hi Andres,

Thank you for that, and thank you to the reporter - I actually spent quite a bit of time struggling with this today, and the bug report and reference to shim-signed pointed me in the right direction.

Cheers,

John.

Status changed to 'Confirmed' because the bug affects multiple users.

Will this fix only work with the version of grub in trusty-updates? Does there need to be compatibility with the version in trusty-security?

Yes, this will work only with the version in trusty-updates, provided that all of our known customers/users are already using trusty-updates, and as such, we do not need to be compatible with trusty-security.

Status changed to 'Confirmed' because the bug affects multiple users.

If this change is incompatible with the version of grub in trusty-security, then I think this should be a versioned dependency.

@Brian,

I've uploaded a new version of the package including this change, but I think you may have to reject the previous upload as it shares the same version.

Hello zdw, or anyone else affected,

Accepted maas into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/maas/1.9.5+bzr4599-0ubuntu1~14.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

The update in proposed fix this problem for me on Trusty.

Updating tag per comment #13.

This bug was fixed in the package maas - 1.9.5+bzr4599-0ubuntu1~14.04.2

---------------
maas (1.9.5+bzr4599-0ubuntu1~14.04.2) trusty-proposed; urgency=medium

  * Stable Release Update.
    - debian/patches/fix-shim-name-lp1713795.patch: Grub package in Trusty
      has changed the name of the shim and has caused MAAS to being unable
      to import new images. (LP: #1713795)
    - debian/control: Bump depends on grub-common to ensure latest is
      always installed.

 -- Andres Rodriguez <email address hidden> Thu, 31 Aug 2017 15:22:08 -0400

The verification of the Stable Release Update for maas has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.