[Bug 1472384] [NEW] grub-install doesn't include raid5rec.mod

2015-07-07 Thread Lee Trager
Public bug reported: I just did a fresh install of Ubuntu 14.04.2 using the official install medium onto my NAS. My NAS contains three drives which I run in a RAID5 configuration with LVM on top. I setup each drive to have a 128MB EFI partition which stores grubx64.efi and put the rest of the

[Bug 1472384] Re: grub-install doesn't include raid5rec.mod

2015-08-18 Thread Lee Trager
With the latest Wily image I still get the same error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472384 Title: grub-install doesn't include raid5rec.mod To manage notifications about this bug

[Bug 1472384] Re: grub-install doesn't include raid5rec.mod

2015-11-09 Thread Lee Trager
I've fixed the issue with the branch linked to above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472384 Title: grub-install doesn't include raid5rec.mod To manage notifications about this bug

[Bug 1472384] UdevLog.txt

2015-07-07 Thread Lee Trager
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1472384/+attachment/4425992/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472384 Title:

[Bug 1472384] ProcCpuinfo.txt

2015-07-07 Thread Lee Trager
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1472384/+attachment/4425988/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472384

[Bug 1472384] ProcModules.txt

2015-07-07 Thread Lee Trager
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1472384/+attachment/4425990/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472384

[Bug 1472384] UdevDb.txt

2015-07-07 Thread Lee Trager
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1472384/+attachment/4425991/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472384 Title:

[Bug 1472384] Re: grub-install doesn't include raid5rec.mod

2015-07-07 Thread Lee Trager
apport information ** Tags added: apport-collected trusty ** Description changed: I just did a fresh install of Ubuntu 14.04.2 using the official install medium onto my NAS. My NAS contains three drives which I run in a RAID5 configuration with LVM on top. I setup each drive to have a

[Bug 1472384] Card1.Codecs.codec.0.txt

2015-07-07 Thread Lee Trager
apport information ** Attachment added: Card1.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/1472384/+attachment/4425983/+files/Card1.Codecs.codec.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1472384] ProcInterrupts.txt

2015-07-07 Thread Lee Trager
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1472384/+attachment/4425989/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1472384] WifiSyslog.txt

2015-07-07 Thread Lee Trager
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1472384/+attachment/4425993/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1472384] PciMultimedia.txt

2015-07-07 Thread Lee Trager
apport information ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/1472384/+attachment/4425987/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1472384] Card0.Codecs.codec.0.txt

2015-07-07 Thread Lee Trager
apport information ** Attachment added: Card0.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/1472384/+attachment/4425982/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1472384] BootDmesg.txt

2015-07-07 Thread Lee Trager
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1472384/+attachment/4425981/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472384

[Bug 1472384] CurrentDmesg.txt

2015-07-07 Thread Lee Trager
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1472384/+attachment/4425984/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472384

[Bug 1472384] Lsusb.txt

2015-07-07 Thread Lee Trager
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1472384/+attachment/4425986/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472384 Title:

[Bug 1472384] Lspci.txt

2015-07-07 Thread Lee Trager
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1472384/+attachment/4425985/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472384 Title:

[Bug 1472384] Re: grub-install doesn't include raid5rec.mod

2015-12-16 Thread Lee Trager
Debian has accepted the patch and its included with 2.02~beta2-33 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472384 Title: grub-install doesn't include raid5rec.mod To manage notifications

[Bug 1518440] [NEW] tgt fails to install in LXD

2015-11-20 Thread Lee Trager
Public bug reported: When trying to install tgt in an LXD container the post install script fails. I've tried setting the container profile as uncontained as per https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-apparmor to no avail. This is preventing MAAS from being able to be run in an LXD

[Bug 1518440] Re: tgt fails to install in LXD

2015-11-20 Thread Lee Trager
** Description changed: - When trying to install tgt in an LXD container the post install script - fails. I've tried setting the container profile as uncontained as per - https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-apparmor to no - avail. This is preventing MAAS from being able to be run

[Bug 1518440] Re: tgt fails to install in LXD

2015-11-20 Thread Lee Trager
** Description changed: - When trying to install tgt in an LXD container the post install script - fails. I've tried setting the container profile as uncontained as per - https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-apparmor to no - avail. This is preventing MAAS from being able to be run

[Bug 1518440] [NEW] tgt fails to install in LXD

2015-11-20 Thread Lee Trager
Public bug reported: When trying to install tgt in an LXD container the post install script fails. I've tried setting the container profile as uncontained as per https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-apparmor to no avail. This is preventing MAAS from being able to be run in an LXD

[Bug 1039701] Re: Wrong RAM memory size

2016-06-03 Thread Lee Trager
Verified that 02.17-1.1ubuntu3.1 fixes the issue and the proper amount of RAM is shown. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1039701] Re: Wrong RAM memory size

2016-05-24 Thread Lee Trager
smbios-noscan.patch was introduced upstream in this bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740034 ** Bug watch added: Debian Bug tracker #740034 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740034 -- You received this bug notification because you are a member of Ubuntu

[Bug 1579996] Re: lshw does not report all CPU cores

2016-05-24 Thread Lee Trager
smbios-noscan.patch was introduced upstream in this bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740034 ** Bug watch added: Debian Bug tracker #740034 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740034 -- You received this bug notification because you are a member of Ubuntu

[Bug 1579996] Re: lshw does not report all CPU cores

2016-05-24 Thread Lee Trager
** Description changed: - lshw B.02.17 is not reporting all available CPU cores. This is fixed - with B.02.18. + lshw B.02.17 is not reporting all available CPU cores. smbios- + noscan.patch is causing this issue. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1579996] Re: lshw does not report all CPU cores

2016-06-02 Thread Lee Trager
*** This bug is a duplicate of bug 1039701 *** https://bugs.launchpad.net/bugs/1039701 ** This bug has been marked a duplicate of bug 1039701 Wrong RAM memory size -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1039701] Re: Wrong RAM memory size

2016-06-01 Thread Lee Trager
** Description changed: - 1) - Description: Ubuntu 12.04.1 LTS (Greek) - Release: 12.04 - 2) - landscape-client: - Εγκατεστημένα: 12.05-0ubuntu0.12.04 - Υποψήφιο: 12.05-0ubuntu0.12.04 - Πίνακας Έκδοσης: - *** 12.05-0ubuntu0.12.04 0 - 500 http://archive.ubuntu.com/ubuntu/

[Bug 1039701] Re: Wrong RAM memory size

2016-03-07 Thread Lee Trager
We're seeing this in MAAS as well. If you commission a machine with 2GB of RAM using Trusty lshw reports 2GB if you commission with Xenial you get 2000 Mb. This causes the MAAS UI to report 1GB of RAM because when we convert 2000 Mb to GB we get 1.9 which is shown as 1GB as we convert to an

[Bug 1039701] Re: Wrong RAM memory size

2016-05-24 Thread Lee Trager
I was mistaken that this is fixed in B.02.18. What is actually causing this is the smbios-noscan.patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039701 Title: Wrong RAM memory size To manage

[Bug 1039701] Re: Wrong RAM memory size

2016-05-11 Thread Lee Trager
** Branch unlinked: lp:~ltrager/maas/parse_proc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039701 Title: Wrong RAM memory size To manage notifications about this bug go to:

[Bug 1039701] Re: Wrong RAM memory size

2016-05-04 Thread Lee Trager
** Branch linked: lp:~ltrager/maas/parse_proc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039701 Title: Wrong RAM memory size To manage notifications about this bug go to:

[Bug 1039701] Re: Wrong RAM memory size

2016-05-09 Thread Lee Trager
B.02.18 was recently released which fixes this problem and displays the correct amount of physical RAM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039701 Title: Wrong RAM memory size To manage

[Bug 1579996] Re: lshw does not report all CPU cores

2016-05-09 Thread Lee Trager
** Attachment added: "Output of sudo lshw -xml from B.02.17" https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1579996/+attachment/4659592/+files/B.02.17.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1579996] Re: lshw does not report all CPU cores

2016-05-09 Thread Lee Trager
** Attachment added: "Output of sudo lshw -xml from B.02.18" https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1579996/+attachment/4659593/+files/B.02.18.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1579996] [NEW] lshw does not report all CPU cores

2016-05-09 Thread Lee Trager
Public bug reported: lshw B.02.17 is not reporting all available CPU cores. This is fixed with B.02.18. ** Affects: lshw (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1579996] Re: lshw does not report all CPU cores

2016-05-09 Thread Lee Trager
** Attachment added: "/proc/cpuinfo" https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1579996/+attachment/4659591/+files/cpuinfo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579996 Title:

[Bug 1588359] Re: No way to add setup files at build time

2016-08-05 Thread Lee Trager
Instead of copying the files out of the source path it would be nice if snapcraft allowed you to specify the path to the icon and license by part. For example if I have a part called foo which contains the icon and license in its source I should be able to do something like icon: $foo/icon.png

[Bug 1666413] Re: linux-image-hwe-16.04 depends on linux-generic-hwe-16.04-edge

2017-02-21 Thread Lee Trager
** Attachment added: "apt log from MAAS installation" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666413/+attachment/4823521/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1666413] Re: linux-image-hwe-16.04 depends on linux-generic-hwe-16.04-edge

2017-02-21 Thread Lee Trager
I can reproduce this when trying to deploy Xenial with HWE-16.04 or in an LXD container when using apt. In both cases linux-generic-hwe-16.04 is being installed into a environment which does not currently have a kernel installed. The MAAS simple stream was just updated to use the new

[Bug 1666413] [NEW] linux-image-hwe-16.04 depends on linux-generic-hwe-16.04-edge

2017-02-20 Thread Lee Trager
Public bug reported: Installing the linux-generic-hwe-16.04 package pulls in linux-generic- hwe-16.04-edge, thus the system has linux-image-4.8.0-34-generic and linux-image-4.8.0-36-generic installed. The system then boots to 4.8.0-36. Installing linux-generic-hwe-16.04 shouldn't pull in

[Bug 1603898] Re: DNS resolution fails when using VPN and routing all traffic over it

2016-08-31 Thread Lee Trager
I'm running into the same issue. My network doesn't have IPv6 although its configured to try, turning off IPv6 had no effect. If I direct all traffic through the VPN ('Use this connection only for resources on its network' in the routes window is left unchecked) I get a DNS server but its not

[Bug 1641832] [NEW] Bash ignores exit trap on success when part of a command string

2016-11-14 Thread Lee Trager
Public bug reported: The MAAS team uses a script, lp:maas-images, which generates the images available at images.maas.io. As part of this process we use the following to convert a SquashFS image to an ext4 image. sudo bash -ec 'src="$1"; img="$2"; trgmp="$3"; mounts="" cleanup() { for m

[Bug 1641832] Re: Bash ignores exit trap on success when part of a command string

2016-11-15 Thread Lee Trager
I'm having trouble coming up with a simpler test case myself. Here is how you can reproduce with lp:maas-images on Zesty with bash-4.4-1ubuntu1 mkdir maas-images cd maas-images bzr init bzr branch lp:maas-images cd export PATH=/home/ubuntu/maas-images/trunk/bin:$PATH wget

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

2017-08-29 Thread Lee Trager
** Changed in: maas Importance: Undecided => Critical ** Changed in: maas Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711760 Title: [2.3] resolv.conf is not

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

2017-08-25 Thread Lee Trager
This is easily reproducible by booting into any MAAS ephemeral environment(commissioning, testing, rescue mode). Apt works regardless of /etc/resolv.conf being set as apt is configured to proxy through the rack controller. MAAS is giving the DNS server over DHCP as running dhclient sets

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

2017-08-28 Thread Lee Trager
Attached is /run. One thing I forgot to mention. MAAS starts an ephemeral environment by passing a user_data script to cloud-init. This script downloads and runs all of the commissioning and testing scripts. My understand of cloud-init is that this means cloud-init still hasn't finished running as

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

2017-08-25 Thread Lee Trager
** Summary changed: - [2.3] resolv.conf is not set (during commissioning) + [2.3] resolv.conf is not set (during commissioning or testing) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711760

[Bug 1711203] Re: Deployments fail when Secure Boot enabled

2017-11-22 Thread Lee Trager
** Branch linked: lp:~ltrager/maas-images/maas_images_signed_kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711203 Title: Deployments fail when Secure Boot enabled To manage notifications

[Bug 1711203] Re: Deployments fail when Secure Boot enabled

2017-12-07 Thread Lee Trager
While reading through #1730493 and #1437024 I noticed both had various UEFI bootloader issues fixed by switching to the Artful version of grub and the shim. I've updated http://162.213.35.187/proposed/streams/v1/index.json to use boot loaders from Artful in case anyone wants to test. -- You

[Bug 1711203] Re: Deployments fail when Secure Boot enabled

2017-12-01 Thread Lee Trager
** Changed in: maas-images Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711203 Title: Deployments fail when Secure Boot enabled To manage

[Bug 1711203] Re: Deployments fail when Secure Boot enabled

2017-12-01 Thread Lee Trager
I've updated lp:maas-images to produce new images using the linux-signed kernel on AMD64. New images are produced when http://cloud- images.ubuntu.com/daily/ adds new images so it may take a few days for signed kernels to appear in the stream. Unsupported releases are no longer updated so we'll

[Bug 1777744] [NEW] 4.15.0-23-generic fails to PXE boot on PPC64

2018-06-19 Thread Lee Trager
Public bug reported: The MAAS CI has a PPC64 machine which is failing to boot into the ephemeral environment. Petite boot loads and kexecs 4.15.0-23-generic from 4.4.27-openpower1 but 4.15 panics before the initrd is loaded. ** Affects: linux (Ubuntu) Importance: Undecided Status:

[Bug 1777744] Re: 4.15.0-23-generic fails to PXE boot on PPC64

2018-06-19 Thread Lee Trager
Unable to run apport-collect as the error occurs while PXE booting the kernel. A panic happens while loading the initrd and a shell is not available. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu

[Bug 1742324] Re: Bionic kernel panics in the MAAS ephemeral environment

2018-01-09 Thread Lee Trager
The kernel panic happens before I can access the system. The long log I am able to pull is the console log which is attached. ** Tags removed: artful ** Tags added: bionic ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are

[Bug 1742324] [NEW] Bionic kernel panics in the MAAS ephemeral environment

2018-01-09 Thread Lee Trager
Public bug reported: Bionic kernel panics in the MAAS ephemeral environment. This does not always happen during commissioning or testing but does happen every time when trying to enter rescue mode. The test system is a KVM machine using all VirtIO drivers running on a Bionic host system. Both

[Bug 1613264] Re: Virt-manager Spice console not working

2018-01-08 Thread Lee Trager
I ran into this on Bionic but had to install the gir1.2-spiceclientgtk-3.0 package instead to fix it. For me apt locked trying to install virt-manager. While running dpkg --configure -a got virt-manager installed it seemed to of missed this dependency. -- You received this bug notification

[Bug 1742324] Re: Bionic kernel panics in the MAAS ephemeral environment

2018-01-11 Thread Lee Trager
4.15-rc7 works with MAAS. I've commissioned, tested, and entered rescue mode without hitting any kernel panics. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742324 Title: Bionic kernel panics in

[Bug 833312] Re: Can not connect to hidden wireless network

2018-01-06 Thread Lee Trager
The 18.04 installer is also missing the connect to hidden SSID option. There is also no option to connect to a hidden SSID from the system settings dropdown. I had to go into settings -> WiFi and then click on the menu icon to finally find the connect to hidden SSID option. For new users this is

[Bug 1742324] Re: Bionic kernel panics in the MAAS ephemeral environment

2018-01-12 Thread Lee Trager
** Changed in: maas Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742324 Title: Bionic kernel panics in the MAAS ephemeral environment To manage notifications

[Bug 1749246] Re: [2.3] Image download hardlinks the hwe-*-edge as the generic kernel instead of the ga-* kernel.

2018-02-13 Thread Lee Trager
** Changed in: maas Status: Confirmed => In Progress ** Changed in: maas/2.3 Status: Triaged => In Progress ** Changed in: maas/2.3 Assignee: (unassigned) => Lee Trager (ltrager) -- You received this bug notification because you are a member of Ubuntu Bu

[Bug 1785859] Re: [REGRESSION] ppc64el grub in bionic may be auto-generating MAC address instead of using the assigned to the VM.

2018-08-07 Thread Lee Trager
I have reverted the OpenFirmware PPC64EL bootloader in lp:maas-images to Xenial while this is debugged. ** Branch linked: lp:~ltrager/maas-images/xenial_ppc_bootloader -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1787630] [NEW] Include HTTP support in pre-build GRUB module

2018-08-17 Thread Lee Trager
Public bug reported: GRUB has builtin support for HTTP via http.mod. This module is not being included in the prebuild grubnetx64.efi. All that should be required is adding the http module. I also suggest building grubnetx64.efi using GRUB modules to include lvm and RAID support to allow

[Bug 1787630] Re: Include HTTP support in pre-build GRUB module

2018-08-17 Thread Lee Trager
** Description changed: GRUB has builtin support for HTTP via http.mod. This module is not being included in the prebuild grubnetx64.efi. All that should be required is adding the http module. I also suggest building grubnetx64.efi using - GRUB modules to include lvm and RAID support to

[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI

2018-08-28 Thread Lee Trager
Sorry forgot to include the failure screenshot. ** Attachment added: "libvirt UEFI iPXE failure with shimx64.efi" https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1789319/+attachment/5181784/+files/maas-test-5-failure.png -- You received this bug notification because you are a

[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI

2018-08-28 Thread Lee Trager
One thing to add, this happens *before* any GRUB configuration is loaded. The machine requests an address over DHCP, bootx64.efi(the shim) over TFTP, and then grubx64.efi over TFTP. Nothing else is requested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1789319] [NEW] Unable to load shimx64.efi using iPXE over UEFI

2018-08-27 Thread Lee Trager
Public bug reported: libvirt supports running in UEFI mode and uses iPXE to enable network booting. When MAAS gives shimx64.efi, as it does on all UEFI systems, to iPXE it chainloads grub but fails to the grub prompt. If I modify MAAS to give grubx64.efi instead of shimx64.efi UEFI booting works.

[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI

2018-08-27 Thread Lee Trager
** Description changed: libvirt supports running in UEFI mode and uses iPXE to enable network booting. When MAAS gives shimx64.efi, as it does on all UEFI systems, to iPXE it chainloads grub but fails to the grub prompt. If I modify MAAS to give grubx64.efi instead of shimx64.efi UEFI

[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI

2018-08-28 Thread Lee Trager
** Attachment added: "libvirt machine configuration" https://bugs.launchpad.net/maas/+bug/1789319/+attachment/5181602/+files/maas-test-5.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789319

[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI

2018-08-28 Thread Lee Trager
** Attachment added: "libvirt UEFI machine PXE booting using iPXE" https://bugs.launchpad.net/maas/+bug/1789319/+attachment/5181603/+files/maas-test-5-ipxe.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI

2018-08-28 Thread Lee Trager
** Attachment added: "libvirt UEFI boot configuration" https://bugs.launchpad.net/maas/+bug/1789319/+attachment/5181604/+files/maas-test-5-firmware.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI

2018-08-28 Thread Lee Trager
When I configure the machine to network boot iPXE is used to try to boot the machine via TFTP. If I go into the UEFI firmware on the virtual machine I can see there are two options to network boot. The first is PXEv4, the second is HTTPv4. It doesn't seem that booting HTTPv4 uses iPXE however that

[Bug 1790003] [NEW] grub-mkimage now requires -p

2018-08-30 Thread Lee Trager
Public bug reported: lp:maas-images downloads all the bootloaders MAAS needs and puts them in the MAAS stream at images.maas.io. It does this on an AMD64 host for all architectures. For ARM64 and PPC64 it must generate the bootloader using grub-mkimage. Since the release of 2.02-2ubuntu8.3

[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI

2018-09-10 Thread Lee Trager
Isn't iPXE what implements TFTP PXE boot? When I tried Julian's command kvm tries UEFI HTTP boot which isn't currently implemented in MAAS and is blocked by lack of grub support(LP:1787630). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1752440] Re: Lshw incorrectly detects amount of RAM in system

2018-02-28 Thread Lee Trager
Could you please post the lshw output in XML form to allow us to create a unit test? You can download this from the commissioning tab or using the CLI with maas node-script-result download current-commissioning filters=00-maas-01-lshw > lshw.log -- You received this bug notification because

[Bug 1752440] Re: Lshw incorrectly detects amount of RAM in system

2018-03-02 Thread Lee Trager
** Changed in: lshw (Ubuntu) Status: Incomplete => New ** Changed in: maas Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752440 Title: Lshw incorrectly

[Bug 1752440] Re: Lshw incorrectly detects amount of RAM in system

2018-03-02 Thread Lee Trager
lshw shows two banks of memory but MAAS is still correctly calculating the output from lshw. There are twelve occurrences of the line 34358689792 which is 384GB. I looked up the part number reported by lshw, 72ASS8G72LZ-2G3B2. According to [1] each DIM should be 64G, not 32G. There is a commit

[Bug 1752440] Re: Lshw incorrectly detects amount of RAM in system

2018-03-02 Thread Lee Trager
It look like these patches have already been accepted into the Bionic version of lshw. @dgrosvenor you don't have to compile lshw. You could also deploy Bionic, install lshw, and run sudo lshw -xml > lshw.log to comfirm. -- You received this bug notification because you are a member of Ubuntu

[Bug 1800153] Re: [2.5] Failed to deploy ppc64el when partition table is GPT

2018-10-30 Thread Lee Trager
Every time I commission the PPC host we have in our CI I always get a GPT partitioning table using MAAS 2.4.2+. Looking through the source code it appears GPT is always set when creating a new partitioning table[1] and when generating the preseed[2] due to the bios_boot_method being powernv. I'm

[Bug 1800153] Re: [2.5] Failed to deploy ppc64el when partition table is GPT

2018-11-01 Thread Lee Trager
My theory on different versions of GRUB causing the issue didn't pan out. After wiping the PReP partition I was able to go between 14.04, 16.04, and 18.04 with no problems. The only way I've been able to reproduce the issue after fixing it is by filling the PReP partition with garbage using $ dd

[Bug 1800153] Re: [2.5] Failed to deploy ppc64el when partition table is GPT

2018-11-01 Thread Lee Trager
** No longer affects: maas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800153 Title: [2.5] Failed to deploy ppc64el when partition table is GPT To manage notifications about this bug go to:

[Bug 1801899] Re: cannot install with python3.7 as default async is a reserved keyword

2018-11-06 Thread Lee Trager
** Changed in: maas Importance: Undecided => Critical ** Changed in: maas Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801899 Title: cannot install with

[Bug 1792575] Re: Boot failure with efi shims from 20180913.0

2018-10-04 Thread Lee Trager
I'm also unable to verify the fix using the MAAS CI. However I did confirm the new shim works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792575 Title: Boot failure with efi shims from

[Bug 1797235] [NEW] Xorg crashes when using nvidia-driver-390 with secure boot disabled

2018-10-10 Thread Lee Trager
Public bug reported: The latest nvidia update causes X.org to crash as soon as I try to login with gdm. I can login to Wayland for a few minutes but it then crashes as well. While going through dmesg I saw the following. It appears that the crash is happening because I disabled UEFI secure boot.

[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI

2018-09-17 Thread Lee Trager
I've verified that the updated ipxe package fixes virsh UEFI deployments wtih MAAS. I tested commissioning, and deploying both Ubuntu 18.04 and CentOS 7. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1813227] Re: lvm2-pvscan services fails to start on S390X DPM

2019-01-24 Thread Lee Trager
** Description changed: The lvm2-pvscan service fails to start in the MAAS ephemeral environment. The service takes ~3 minutes to fail, blocking boot until - failure. + failure. Curtin is expereincing a similar bug(LP:1813228) due to LVM. Release: 18.10(18.04 does not currently boot on

[Bug 1813227] [NEW] lvm2-pvscan services fails to start on S390X DPM

2019-01-24 Thread Lee Trager
Public bug reported: The lvm2-pvscan service fails to start in the MAAS ephemeral environment. The service takes ~3 minutes to fail, blocking boot until failure. Release: 18.10(18.04 does not currently boot on S390X DPM) Kernel: 4.18.0-13-generic LVM: 2.02.176-4.1ubuntu3 root@node3:~# lvm

[Bug 1813227] Re: lvm2-pvscan services fails to start on S390X DPM

2019-01-24 Thread Lee Trager
** Attachment added: "jourctl output of lvm2" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1813227/+attachment/5232337/+files/lvm.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813227

[Bug 1646805] Re: MAC address needs to be unique and unchanged during entire netboot process

2019-04-03 Thread Lee Trager
I tested this today using 5.0.0-8-generic and between reboots I am still getting different MAC addresses on Z13. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646805 Title: MAC address needs to be

[Bug 1813227] Re: lvm2-pvscan services fails to start on S390X DPM

2019-04-04 Thread Lee Trager
I tested a Disco image today with multipath-tools installed and I still get the same thing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813227 Title: lvm2-pvscan services fails to start on S390X

[Bug 1815788] Re: lshw exits with segmentation fault when commissioning a new node on maas

2019-02-14 Thread Lee Trager
Can you confirm storage is working correctly for you? Does the system you are experiencing this on have Intel SGX? Upstream recently committed a patch [1] to prevent a segmentation fault when using Intel SGX. Can you try building lshw from source[2] and see if you can reproduce the issue?

[Bug 1813227] Re: lvm2-pvscan services fails to start on S390X DPM

2019-01-28 Thread Lee Trager
** Attachment added: "lsblk output" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1813227/+attachment/5233345/+files/lsblk.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813227 Title:

[Bug 1813227] Re: lvm2-pvscan services fails to start on S390X DPM

2019-01-28 Thread Lee Trager
The MAAS ephemeral environment does not have the multipath kernel module nor multipath-tools. To get this log I had to install both. ** Attachment added: "multipath.log" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1813227/+attachment/5233346/+files/multipath.log -- You received this

[Bug 1829945] Re: SDL support missing from qemu-1:3.1+dfsg-2ubuntu3.1

2019-05-22 Thread Lee Trager
Thanks for the explanation. MAAS is starting to use Packer to create custom images so we may be packaging this soon. I will filed an upstream bug[1] and created a patch[2] to fix the issue. [1] https://github.com/hashicorp/packer/issues/7675 [2] https://github.com/hashicorp/packer/pull/7676 **

[Bug 1701434] Re: netplan apply always exits with status 0

2019-07-05 Thread Lee Trager
I'm seeing the same thing in LP:1835275 except netplan doesn't output any errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701434 Title: netplan apply always exits with status 0 To manage

[Bug 1844334] Re: SRU cloud-init (19.2.36): Xenial, Bionic, and Disco

2019-09-27 Thread Lee Trager
We're currently working on fixing the MAAS CI. In the meantime I was able to manually test Xenial, Bionic, and Disco with proposed. All were able to commission and deploy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1831134] Re: Pods Cannot allocate memory, even with memory_over_commit_ratio set 10.0

2019-09-20 Thread Lee Trager
It appears your system is over committed to much. qemu needs a minimal amount of resources to be able to start the VM. Leaving this open as our docs and the UI should explain this better. ** Tags added: docs ui ** Changed in: maas Status: New => Triaged ** Changed in: maas Importance:

[Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS

2019-10-04 Thread Lee Trager
I manually tested the new cloud-init using the MAAS CI as we don't have automated tests for bonds or bridges. Xenial, Bionic, and Disco can all commissioning and deploy fine using static IPs, bonds, and bridges. -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1862846] Re: Crash and failure installing focal

2020-02-11 Thread Lee Trager
Upstream util-linux has fixed this in 2.34.1+ https://github.com/karelzak/util-linux/issues/813 ** Bug watch added: github.com/karelzak/util-linux/issues #813 https://github.com/karelzak/util-linux/issues/813 -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1862846] Re: Crash and failure installing focal

2020-02-11 Thread Lee Trager
I agree a -b or -e should be used instead of -f. However pkname is a valid column in lsblk. From lsblk --help: KNAME internal kernel device name PKNAME internal parent kernel device name pkname not working is a regression which was introduced in util- linux-2.34[1]. Upstream has fixed this[2].

  1   2   >