Activity log for bug #1437353

Date Who What changed Old value New value Message
2015-03-27 14:10:36 Matt Dirba bug added bug
2015-03-27 14:10:36 Matt Dirba attachment added varlogmaas.tar.gz https://bugs.launchpad.net/bugs/1437353/+attachment/4357841/+files/varlogmaas.tar.gz
2015-03-27 14:30:36 Blake Rouse maas: status New Triaged
2015-03-27 14:30:38 Blake Rouse maas: importance Undecided High
2015-03-27 14:30:40 Blake Rouse maas: milestone next
2015-03-27 14:30:46 Blake Rouse tags hwe
2015-03-27 14:30:55 Blake Rouse tags hwe grubnet hwe uefi
2015-03-27 14:31:39 Blake Rouse bug task added grub2 (Ubuntu)
2015-03-27 14:56:50 Blake Rouse bug task deleted grub2 (Ubuntu)
2015-03-27 14:56:59 Blake Rouse tags grubnet hwe uefi hwe ipv6 uefi
2015-03-27 15:05:08 Andres Rodriguez bug task added python-tx-tftp
2015-03-30 17:17:47 Blake Rouse bug task added grub2 (Ubuntu)
2015-04-01 19:14:23 Matt Dirba maas: status Triaged Invalid
2015-04-01 19:14:36 Matt Dirba grub2 (Ubuntu): status New Invalid
2015-04-01 19:17:07 Matt Dirba python-tx-tftp: status New Invalid
2015-07-24 06:04:04 meilei007 bug added subscriber meilei007
2016-09-01 06:26:13 Surajit bug added subscriber Surajit
2017-03-01 13:43:41 Ante Karamatić bug added subscriber Ante Karamatić
2017-05-04 19:32:17 Ante Karamatić grub2 (Ubuntu): status Invalid Confirmed
2017-05-04 19:32:20 Ante Karamatić grub2 (Ubuntu): importance Undecided High
2017-05-04 21:11:19 Andres Rodriguez grub2 (Ubuntu): status Confirmed Triaged
2017-05-04 21:11:24 Andres Rodriguez grub2 (Ubuntu): status Triaged Confirmed
2017-05-04 21:11:29 Andres Rodriguez bug task added maas-images
2017-05-04 21:11:37 Andres Rodriguez maas-images: status New Triaged
2017-05-04 21:11:44 Andres Rodriguez maas-images: importance Undecided High
2017-05-04 21:53:40 Mathieu Trudel-Lapierre grub2 (Ubuntu): assignee Mathieu Trudel-Lapierre (cyphermox)
2017-05-04 21:53:43 Mathieu Trudel-Lapierre grub2 (Ubuntu): status Confirmed In Progress
2017-05-04 21:53:53 Mathieu Trudel-Lapierre grub2 (Ubuntu): status In Progress Fix Released
2017-05-04 21:54:22 Mathieu Trudel-Lapierre nominated for series Ubuntu Yakkety
2017-05-04 21:54:22 Mathieu Trudel-Lapierre bug task added grub2 (Ubuntu Yakkety)
2017-05-04 21:54:22 Mathieu Trudel-Lapierre nominated for series Ubuntu Xenial
2017-05-04 21:54:22 Mathieu Trudel-Lapierre bug task added grub2 (Ubuntu Xenial)
2017-05-04 21:54:22 Mathieu Trudel-Lapierre nominated for series Ubuntu Trusty
2017-05-04 21:54:22 Mathieu Trudel-Lapierre bug task added grub2 (Ubuntu Trusty)
2017-05-04 21:54:34 Mathieu Trudel-Lapierre grub2 (Ubuntu Xenial): status New In Progress
2017-05-04 21:54:36 Mathieu Trudel-Lapierre grub2 (Ubuntu Xenial): importance Undecided High
2017-05-04 21:54:38 Mathieu Trudel-Lapierre grub2 (Ubuntu Trusty): importance Undecided High
2017-05-04 21:54:39 Mathieu Trudel-Lapierre grub2 (Ubuntu Yakkety): importance Undecided High
2017-05-04 21:54:41 Mathieu Trudel-Lapierre grub2 (Ubuntu Trusty): assignee Mathieu Trudel-Lapierre (cyphermox)
2017-05-04 21:54:43 Mathieu Trudel-Lapierre grub2 (Ubuntu Xenial): assignee Mathieu Trudel-Lapierre (cyphermox)
2017-05-04 21:54:45 Mathieu Trudel-Lapierre grub2 (Ubuntu Yakkety): assignee Mathieu Trudel-Lapierre (cyphermox)
2017-05-04 21:54:52 Mathieu Trudel-Lapierre grub2 (Ubuntu): milestone ubuntu-17.05
2017-05-05 14:41:46 Mathieu Trudel-Lapierre bug task added grub2-signed (Ubuntu)
2017-05-05 14:42:10 Mathieu Trudel-Lapierre grub2-signed (Ubuntu Xenial): importance Undecided Medium
2017-05-05 14:42:10 Mathieu Trudel-Lapierre grub2-signed (Ubuntu Xenial): status New In Progress
2017-05-05 14:42:10 Mathieu Trudel-Lapierre grub2-signed (Ubuntu Xenial): assignee Mathieu Trudel-Lapierre (cyphermox)
2017-05-05 15:51:01 Mathieu Trudel-Lapierre description I am using MAAS to commission and install machines. When I attempt to commission a machine with a "82599ES 10-Gigabit SFI/SFP+" network adapter the following happens: 1) TFTP Request — bootx64.efi 2) TFTP Request — /grubx64.efi 3) Console hangs at grub prompt If I go into bios and force the adapter above into legacy mode then the machine is able to network boot and run through the commission process. 1) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-initrd 2) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-kernel 3) TFTP Request — ifcpu64.c32 4) PXE Request — power off 5) TFTP Request — pxelinux.cfg/01-90-e2-ba-52-23-78 6) TFTP Request — pxelinux.cfg/71e3f102-bd8b-11e4-b634-3c18a001c80a 7) TFTP Request — pxelinux.0 Also, if I disconnect the cable to the adapter above and connect a cable to the integrated "I210 Gigabit" adapter which is configured for UEFI mode. The machine is able to network boot grubx64.efi and run through the commission process. ~$ dpkg -l '*maas*'|cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=====================================-==================================-============-=============================================================================== ii maas 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server all-in-one metapackage ii maas-cli 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS command line API tool ii maas-cluster-controller 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server cluster controller ii maas-common 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server common files ii maas-dhcp 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS DHCP server ii maas-dns 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS DNS server ii maas-proxy 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS Caching Proxy ii maas-region-controller 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server complete region controller ii maas-region-controller-min 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS Server minimum region controller ii python-django-maas 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server Django web framework ii python-maas-client 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS python API client ii python-maas-provisioningserver 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server provisioning libraries ~$ [Impact] MAAS commissioning may fail when deploying Xenial images or using grubx64.efi from Xenial due to hardware particularities of some Intel 82599-based network cards. Other network manufacturers may be affected as well. The main failure mode appears to be an infinite re-send of some packets because of an unexpected response from the network hardware. [Test case] [Regression potential] As this affects network in EFI mode; any failure to netboot using EFI should be considered a possible regression. Systems may fail to receive data from the network boot server and terminate the process with a timeout. Another possible failure scenario is to fail to receive complete data over the network, or data corruption. ---- I am using MAAS to commission and install machines. When I attempt to commission a machine with a "82599ES 10-Gigabit SFI/SFP+" network adapter the following happens: 1) TFTP Request — bootx64.efi 2) TFTP Request — /grubx64.efi 3) Console hangs at grub prompt If I go into bios and force the adapter above into legacy mode then the machine is able to network boot and run through the commission process. 1) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-initrd 2) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-kernel 3) TFTP Request — ifcpu64.c32 4) PXE Request — power off 5) TFTP Request — pxelinux.cfg/01-90-e2-ba-52-23-78 6) TFTP Request — pxelinux.cfg/71e3f102-bd8b-11e4-b634-3c18a001c80a 7) TFTP Request — pxelinux.0 Also, if I disconnect the cable to the adapter above and connect a cable to the integrated "I210 Gigabit" adapter which is configured for UEFI mode. The machine is able to network boot grubx64.efi and run through the commission process. ~$ dpkg -l '*maas*'|cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=====================================-==================================-============-=============================================================================== ii maas 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server all-in-one metapackage ii maas-cli 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS command line API tool ii maas-cluster-controller 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server cluster controller ii maas-common 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server common files ii maas-dhcp 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS DHCP server ii maas-dns 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS DNS server ii maas-proxy 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS Caching Proxy ii maas-region-controller 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server complete region controller ii maas-region-controller-min 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS Server minimum region controller ii python-django-maas 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server Django web framework ii python-maas-client 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS python API client ii python-maas-provisioningserver 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server provisioning libraries ~$
2017-05-07 23:38:29 Taihsiang Ho bug added subscriber Taihsiang Ho
2018-01-17 12:35:28 Nobuto Murata tags hwe ipv6 uefi cpe-onsite hwe ipv6 uefi
2018-01-17 12:35:37 Nobuto Murata bug added subscriber Nobuto Murata
2018-03-14 02:08:00 Ante Karamatić bug added subscriber Canonical Field High
2018-03-21 16:45:53 Mathieu Trudel-Lapierre description [Impact] MAAS commissioning may fail when deploying Xenial images or using grubx64.efi from Xenial due to hardware particularities of some Intel 82599-based network cards. Other network manufacturers may be affected as well. The main failure mode appears to be an infinite re-send of some packets because of an unexpected response from the network hardware. [Test case] [Regression potential] As this affects network in EFI mode; any failure to netboot using EFI should be considered a possible regression. Systems may fail to receive data from the network boot server and terminate the process with a timeout. Another possible failure scenario is to fail to receive complete data over the network, or data corruption. ---- I am using MAAS to commission and install machines. When I attempt to commission a machine with a "82599ES 10-Gigabit SFI/SFP+" network adapter the following happens: 1) TFTP Request — bootx64.efi 2) TFTP Request — /grubx64.efi 3) Console hangs at grub prompt If I go into bios and force the adapter above into legacy mode then the machine is able to network boot and run through the commission process. 1) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-initrd 2) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-kernel 3) TFTP Request — ifcpu64.c32 4) PXE Request — power off 5) TFTP Request — pxelinux.cfg/01-90-e2-ba-52-23-78 6) TFTP Request — pxelinux.cfg/71e3f102-bd8b-11e4-b634-3c18a001c80a 7) TFTP Request — pxelinux.0 Also, if I disconnect the cable to the adapter above and connect a cable to the integrated "I210 Gigabit" adapter which is configured for UEFI mode. The machine is able to network boot grubx64.efi and run through the commission process. ~$ dpkg -l '*maas*'|cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=====================================-==================================-============-=============================================================================== ii maas 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server all-in-one metapackage ii maas-cli 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS command line API tool ii maas-cluster-controller 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server cluster controller ii maas-common 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server common files ii maas-dhcp 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS DHCP server ii maas-dns 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS DNS server ii maas-proxy 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS Caching Proxy ii maas-region-controller 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server complete region controller ii maas-region-controller-min 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS Server minimum region controller ii python-django-maas 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server Django web framework ii python-maas-client 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS python API client ii python-maas-provisioningserver 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server provisioning libraries ~$ [Impact] MAAS commissioning may fail when deploying Xenial images or using grubx64.efi from Xenial due to hardware particularities of some Intel 82599-based network cards. Other network manufacturers may be affected as well. The main failure mode appears to be an infinite re-send of some packets because of an unexpected response from the network hardware. [Test case] Attempt to netboot on a system with a "82599ES 10-Gigabit SFI/SFP+" network adapter. [Regression potential] As this affects network in EFI mode; any failure to netboot using EFI should be considered a possible regression. Systems may fail to receive data from the network boot server and terminate the process with a timeout. Another possible failure scenario is to fail to receive complete data over the network, or data corruption. ---- I am using MAAS to commission and install machines. When I attempt to commission a machine with a "82599ES 10-Gigabit SFI/SFP+" network adapter the following happens: 1) TFTP Request — bootx64.efi 2) TFTP Request — /grubx64.efi 3) Console hangs at grub prompt If I go into bios and force the adapter above into legacy mode then the machine is able to network boot and run through the commission process. 1) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-initrd 2) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-kernel 3) TFTP Request — ifcpu64.c32 4) PXE Request — power off 5) TFTP Request — pxelinux.cfg/01-90-e2-ba-52-23-78 6) TFTP Request — pxelinux.cfg/71e3f102-bd8b-11e4-b634-3c18a001c80a 7) TFTP Request — pxelinux.0 Also, if I disconnect the cable to the adapter above and connect a cable to the integrated "I210 Gigabit" adapter which is configured for UEFI mode. The machine is able to network boot grubx64.efi and run through the commission process. ~$ dpkg -l '*maas*'|cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=====================================-==================================-============-=============================================================================== ii maas 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server all-in-one metapackage ii maas-cli 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS command line API tool ii maas-cluster-controller 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server cluster controller ii maas-common 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server common files ii maas-dhcp 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS DHCP server ii maas-dns 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS DNS server ii maas-proxy 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS Caching Proxy ii maas-region-controller 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server complete region controller ii maas-region-controller-min 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS Server minimum region controller ii python-django-maas 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server Django web framework ii python-maas-client 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS python API client ii python-maas-provisioningserver 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server provisioning libraries ~$
2018-03-21 16:51:35 Steve Langasek grub2 (Ubuntu Yakkety): status New Won't Fix
2018-03-21 16:51:47 Steve Langasek grub2-signed (Ubuntu Yakkety): status New Won't Fix
2018-03-21 17:34:14 Mathieu Trudel-Lapierre description [Impact] MAAS commissioning may fail when deploying Xenial images or using grubx64.efi from Xenial due to hardware particularities of some Intel 82599-based network cards. Other network manufacturers may be affected as well. The main failure mode appears to be an infinite re-send of some packets because of an unexpected response from the network hardware. [Test case] Attempt to netboot on a system with a "82599ES 10-Gigabit SFI/SFP+" network adapter. [Regression potential] As this affects network in EFI mode; any failure to netboot using EFI should be considered a possible regression. Systems may fail to receive data from the network boot server and terminate the process with a timeout. Another possible failure scenario is to fail to receive complete data over the network, or data corruption. ---- I am using MAAS to commission and install machines. When I attempt to commission a machine with a "82599ES 10-Gigabit SFI/SFP+" network adapter the following happens: 1) TFTP Request — bootx64.efi 2) TFTP Request — /grubx64.efi 3) Console hangs at grub prompt If I go into bios and force the adapter above into legacy mode then the machine is able to network boot and run through the commission process. 1) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-initrd 2) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-kernel 3) TFTP Request — ifcpu64.c32 4) PXE Request — power off 5) TFTP Request — pxelinux.cfg/01-90-e2-ba-52-23-78 6) TFTP Request — pxelinux.cfg/71e3f102-bd8b-11e4-b634-3c18a001c80a 7) TFTP Request — pxelinux.0 Also, if I disconnect the cable to the adapter above and connect a cable to the integrated "I210 Gigabit" adapter which is configured for UEFI mode. The machine is able to network boot grubx64.efi and run through the commission process. ~$ dpkg -l '*maas*'|cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=====================================-==================================-============-=============================================================================== ii maas 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server all-in-one metapackage ii maas-cli 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS command line API tool ii maas-cluster-controller 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server cluster controller ii maas-common 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server common files ii maas-dhcp 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS DHCP server ii maas-dns 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS DNS server ii maas-proxy 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS Caching Proxy ii maas-region-controller 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server complete region controller ii maas-region-controller-min 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS Server minimum region controller ii python-django-maas 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server Django web framework ii python-maas-client 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS python API client ii python-maas-provisioningserver 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server provisioning libraries ~$ [Impact] MAAS commissioning may fail when deploying Xenial images or using grubx64.efi from Xenial due to hardware particularities of some Intel 82599-based network cards. Other network manufacturers may be affected as well. The main failure mode appears to be an infinite re-send of some packets because of an unexpected response from the network hardware. [Test case] 1) Attempt to netboot on a system with a "82599ES 10-Gigabit SFI/SFP+" network adapter; in UEFI mode. 2) Validate that netbooting happens correctly, passing control over to the kernel as configured in grub.cfg. 3) Validate that netbooting another system, not using an Intel 82599 adapter, behaves normally when booting in UEFI mode. 4) Validate that netbooting another system, not using an Intel 82599 adapter, behaves normally when booting in LEGACY mode. [Regression potential] As this affects network in EFI mode; any failure to netboot using EFI should be considered a possible regression. Systems may fail to receive data from the network boot server and terminate the process with a timeout. Another possible failure scenario is to fail to receive complete data over the network, or data corruption. ---- I am using MAAS to commission and install machines. When I attempt to commission a machine with a "82599ES 10-Gigabit SFI/SFP+" network adapter the following happens: 1) TFTP Request — bootx64.efi 2) TFTP Request — /grubx64.efi 3) Console hangs at grub prompt If I go into bios and force the adapter above into legacy mode then the machine is able to network boot and run through the commission process. 1) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-initrd 2) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-kernel 3) TFTP Request — ifcpu64.c32 4) PXE Request — power off 5) TFTP Request — pxelinux.cfg/01-90-e2-ba-52-23-78 6) TFTP Request — pxelinux.cfg/71e3f102-bd8b-11e4-b634-3c18a001c80a 7) TFTP Request — pxelinux.0 Also, if I disconnect the cable to the adapter above and connect a cable to the integrated "I210 Gigabit" adapter which is configured for UEFI mode. The machine is able to network boot grubx64.efi and run through the commission process. ~$ dpkg -l '*maas*'|cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=====================================-==================================-============-=============================================================================== ii maas 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server all-in-one metapackage ii maas-cli 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS command line API tool ii maas-cluster-controller 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server cluster controller ii maas-common 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server common files ii maas-dhcp 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS DHCP server ii maas-dns 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS DNS server ii maas-proxy 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS Caching Proxy ii maas-region-controller 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server complete region controller ii maas-region-controller-min 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS Server minimum region controller ii python-django-maas 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server Django web framework ii python-maas-client 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS python API client ii python-maas-provisioningserver 1.7.2+bzr3355-0ubuntu1~trusty1 all MAAS server provisioning libraries ~$
2018-03-21 17:37:52 Steve Langasek grub2 (Ubuntu Xenial): status In Progress Fix Committed
2018-03-21 17:37:55 Steve Langasek bug added subscriber Ubuntu Stable Release Updates Team
2018-03-21 17:37:57 Steve Langasek bug added subscriber SRU Verification
2018-03-21 17:38:03 Steve Langasek tags cpe-onsite hwe ipv6 uefi cpe-onsite hwe ipv6 uefi verification-needed verification-needed-xenial
2018-03-21 17:40:59 Patricia Gaughen bug added subscriber Patricia Gaughen
2018-03-22 03:53:41 Steve Langasek grub2-signed (Ubuntu Xenial): status In Progress Fix Committed
2018-03-22 12:33:59 Francis Ginther tags cpe-onsite hwe ipv6 uefi verification-needed verification-needed-xenial cpe-onsite hwe id-5ab2aac1fcfcb094be6eb2e1 ipv6 uefi verification-needed verification-needed-xenial
2018-03-29 19:32:35 Ubuntu Foundations Team Bug Bot bug added subscriber Brian Murray
2018-03-29 19:32:38 Ubuntu Foundations Team Bug Bot tags cpe-onsite hwe id-5ab2aac1fcfcb094be6eb2e1 ipv6 uefi verification-needed verification-needed-xenial cpe-onsite hwe id-5ab2aac1fcfcb094be6eb2e1 ipv6 uefi verification-failed-xenial verification-needed verification-needed-xenial
2018-04-09 13:23:34 Mathieu Trudel-Lapierre tags cpe-onsite hwe id-5ab2aac1fcfcb094be6eb2e1 ipv6 uefi verification-failed-xenial verification-needed verification-needed-xenial cpe-onsite hwe id-5ab2aac1fcfcb094be6eb2e1 ipv6 uefi verification-needed verification-needed-xenial
2018-04-25 14:22:35 Andres Rodriguez tags cpe-onsite hwe id-5ab2aac1fcfcb094be6eb2e1 ipv6 uefi verification-needed verification-needed-xenial cpe-onsite hwe id-5ab2aac1fcfcb094be6eb2e1 ipv6 uefi verification-done-xenial verification-needed
2018-04-25 14:22:42 Andres Rodriguez tags cpe-onsite hwe id-5ab2aac1fcfcb094be6eb2e1 ipv6 uefi verification-done-xenial verification-needed cpe-onsite hwe id-5ab2aac1fcfcb094be6eb2e1 ipv6 uefi verification-done verification-done-xenial
2018-05-16 14:04:34 Mathieu Trudel-Lapierre tags cpe-onsite hwe id-5ab2aac1fcfcb094be6eb2e1 ipv6 uefi verification-done verification-done-xenial cpe-onsite hwe id-5ab2aac1fcfcb094be6eb2e1 ipv6 uefi verification-failed-xenial
2018-05-16 22:27:49 Mathieu Trudel-Lapierre tags cpe-onsite hwe id-5ab2aac1fcfcb094be6eb2e1 ipv6 uefi verification-failed-xenial cpe-onsite hwe id-5ab2aac1fcfcb094be6eb2e1 ipv6 uefi verification-needed-xenial
2018-05-17 13:49:24 Mathieu Trudel-Lapierre tags cpe-onsite hwe id-5ab2aac1fcfcb094be6eb2e1 ipv6 uefi verification-needed-xenial cpe-onsite hwe id-5ab2aac1fcfcb094be6eb2e1 ipv6 uefi verification-done-xenial
2018-05-21 07:00:26 Łukasz Zemczak removed subscriber Ubuntu Stable Release Updates Team
2018-05-21 07:00:24 Launchpad Janitor grub2 (Ubuntu Xenial): status Fix Committed Fix Released
2018-05-21 07:00:39 Launchpad Janitor grub2-signed (Ubuntu Xenial): status Fix Committed Fix Released
2018-05-31 14:20:26 Launchpad Janitor grub2-signed (Ubuntu): status New Confirmed
2018-05-31 14:20:26 Launchpad Janitor grub2 (Ubuntu Trusty): status New Confirmed
2018-05-31 14:20:26 Launchpad Janitor grub2-signed (Ubuntu Trusty): status New Confirmed
2018-06-13 12:49:13 Andres Rodriguez maas-images: status Triaged Fix Released
2021-08-24 09:31:00 Björn Tillenius maas: milestone next