The issue seems to be that a change an SRU to the 'shim-signed' package in Trusty has renamed shim.efi.signed to shimx64.efi.signed. MAAS expects the file shim.efi.signed to be available, hence the failure.
On Tue, Aug 29, 2017 at 11:10 AM, Zack Williams <[email protected]> wrote: > From a system set up yesterday - Is the upstream image for Ubuntu 14.04 > broken? On a working system, there is usually one snapshot directory. > > /var/lib/maas/boot-resources$ ls > cache snapshot-20170829-080223 > snapshot-20170829-094723 snapshot-20170829-113223 snapshot-20170829-131737 > snapshot-20170829-062010 snapshot-20170829-080723 > snapshot-20170829-095223 snapshot-20170829-113723 snapshot-20170829-132223 > snapshot-20170829-062223 snapshot-20170829-081223 > snapshot-20170829-095723 snapshot-20170829-114223 snapshot-20170829-132723 > snapshot-20170829-062723 snapshot-20170829-081727 > snapshot-20170829-100223 snapshot-20170829-114723 snapshot-20170829-133223 > ... > > /var/lib/maas/boot-resources$ ls snapshot-20170829-* | wc -l > 569 > /var/lib/maas/boot-resources$ dpkg -s maas > Package: maas > Status: install ok installed > Priority: optional > Section: net > Installed-Size: 45 > Maintainer: Ubuntu Developers <[email protected]> > Architecture: all > Version: 1.9.5+bzr4599-0ubuntu1~14.04.1 > Depends: maas-cluster-controller (= 1.9.5+bzr4599-0ubuntu1~14.04.1), > maas-region-controller (= 1.9.5+bzr4599-0ubuntu1~14.04.1), > python-django-maas (= 1.9.5+bzr4599-0ubuntu1~14.04.1) > Description: MAAS server all-in-one metapackage > > More context: https://gist.github.com/zdw/064fa5c2eea2dbfb3747fd6fdcd8bd23 > > Any ideas? > > Thanks, > Zack > -- > Maas-devel mailing list > [email protected] > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/maas-devel > -- Andres Rodriguez Engineering Manager, MAAS Canonical USA, Inc.
-- Maas-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/maas-devel
