[Bug 1711203] Re: Deployments fail when Secure Boot enabled
We have a test streams that uses the signed linux kernel instead of the non-signed for x86. Can you please test it from this stream: http://162.213.35.187/proposed/streams/v1/index.json -- 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 about this bug go to: https://bugs.launchpad.net/curtin/+bug/1711203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711203] Re: Deployments fail when Secure Boot enabled
** Changed in: maas-images Assignee: (unassigned) => Lee Trager (ltrager) -- 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 about this bug go to: https://bugs.launchpad.net/curtin/+bug/1711203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732522] Re: [2.3] Ephemeral boot environment does not renew DHCP leases
** Changed in: maas Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732522 Title: [2.3] Ephemeral boot environment does not renew DHCP leases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1732522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733615] [NEW] [SRU] MAAS 2.3.0
Public bug reported: [Impact] This is a new upstream release that addresses various issues present in 2.2 and introduces various features that improve the robustness, and feature set of MAAS. MAAS 2.3.0 introduces the following features: - Add support for CentOS & Windows networking. - Add support for Upstream Proxy. - Add the ability to deploy rack controllers. - Add the ability to report controller versions. - Add HTTP boot for ephemeral images, instead of 'tgt'. - Add django 1.11 support. - Introduce beaconing for better network discovery. - Improve hardware testing for better usage and feedback. - Improves performance by improving DNS reloading performance. - Machine, devices & controller page re-design. [Test Case] MAAS testing has been done in various cases, partially documented https://wiki.ubuntu.com/MAASUpdates. This include: 1. Manual Fresh installation of MAAS 2. Manual upgrade from the previous Ubuntu Release. 3. Automated (CI) testing of MAAS install and operation as per the MAAS' CI. 4. Automated (CI) testing of MAAS install and operation against other Canonical's product (juju, Canonical OpenStack & Kubernetes) provided by the Canonical Solutions QA Team. 5. Manual split region/rack test are performed. This is to ensure that if we upgrade a MAAS Region to a newer version, the MAAS rack of the older version remains connected and operational. All of this includes verifying normal operation, issues fixed, and ensuring that Canonical Cloud solutions can inter-operate. MAAS releases are also now vetted by the Solutions QA team. [Regression Potential] Minimal (For MAAS itself). MAAS is fully backwards compatible and handles upgrades from previous releases which result in the continuous operation of MAAS. Users will continue to use this new version of MAAS as they used it before. Medium (For not tested set of hardware) - A new version of Curtin has been SRU'd, and as such, this could impact the deployment of untested hardware Paths. MAAS, in itself, has not changed the way it deploys machines, but curtin (the one in charge of network, disk & boot-order) has. ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Affects: maas (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: maas (Ubuntu Zesty) Importance: Undecided Status: New ** Affects: maas (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: maas (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: maas (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: maas (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733615 Title: [SRU] MAAS 2.3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1733615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707999] Re: [SRU] iPXE doesn't handle NAK requests when multiple DHCP server's offer
** Changed in: ipxe (Ubuntu Zesty) Importance: Undecided => Critical ** Changed in: ipxe (Ubuntu Xenial) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707999 Title: [SRU] iPXE doesn't handle NAK requests when multiple DHCP server's offer To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1707999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707999] Re: [SRU] iPXE doesn't handle NAK requests when multiple DHCP server's offer
** Summary changed: - pod VM fails to PXE boot after receiving multiple DHCP offers, for different IPs, from the dhcp server + [SRU] iPXE doesn't handle NAK requests when multiple DHCP server's offer ** Description changed: + [Impact] + When there are multiple DHCP servers on the network, iPXE doesn't handle NAK's for the DHCP servers. This causes iPXE to get blocked without attempting to re-discover, hence, never obtaining an IP address. + + For example, in a MAAS HA environment with a DHCP master/slave + configuration, the machine fails to PXE boot because at a certain point, + the DHCP server is not fully in sync, which causes iPXE to get a NAK + request. This prevents the machine from PXE booting. + + [Test case] + The easiest way: + 1. Install MAAS with two rack controllers + 2. Configure HA + 3. PXE boot KVM's. + + [Regression Potential] + Minimal. This only ensures that iPXE attempts to re-discover the network when it receives a NACK. + + [Original bug report] A VM failed to PXE boot after receiving multiple DHCP offers. You can see this here on a log from the secondary controller: http://paste.ubuntu.com/25221939/ The node is offered both 10.245.208.201 and 10.245.208.120, tries to get 10.245.208.120, and is refused. One strange thing is that it seems like the DHCP server on both the primary controller and the secondary controller are responding. The primary controller's log doesn't have the offer for 10.245.208.120 - only the offer for 10.245.208.201: http://paste.ubuntu.com/25221952/ This is in an HA setup: region API's are at 10.245.208.30, 10.245.208.31 and 10.245.208.32. We're using hacluster to load balance, and a VIP in front at 10.245.208.33. There are rack controllers on 10.245.208.30 and 10.245.208.31. For the untagged vlan this VM is trying to boot from, 10.245.208.30 is set as the primary controller, and 10.245.208.31 is set as the secondary. Primary postgres is on 10.245.208.30, it's being replicated to backup postgres on 10.245.208.31. It has a VIP at 10.245.208.34. We don't hit this everytime - on this deployment only one machine out of about 30 hit this. We've also seen this on single node MAAS setups - non HA. So, it's not an HA specific issue. I've attached logs from the maas servers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707999 Title: [SRU] iPXE doesn't handle NAK requests when multiple DHCP server's offer To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1707999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711203] Re: Deployments fail when Secure Boot enabled
** Changed in: maas-images Status: Confirmed => In Progress -- 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 about this bug go to: https://bugs.launchpad.net/curtin/+bug/1711203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711203] Re: Deployments fail when Secure Boot enabled
** Branch linked: lp:~andreserl/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 about this bug go to: https://bugs.launchpad.net/curtin/+bug/1711203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711203] Re: Deployments fail when Secure Boot enabled
** Also affects: maas-images Importance: Undecided Status: New -- 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 about this bug go to: https://bugs.launchpad.net/curtin/+bug/1711203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711203] Re: Deployments fail when Secure Boot enabled
** Changed in: maas-images Status: New => Confirmed ** Changed in: maas-images Importance: Undecided => High ** Changed in: maas-images Importance: High => Critical ** Changed in: maas Importance: Undecided => Critical ** Changed in: maas Milestone: None => 2.3.0 -- 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 about this bug go to: https://bugs.launchpad.net/curtin/+bug/1711203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319600] Re: maas-cli stack trace if .maascli.db unreadable
** Changed in: maas Milestone: 2.3.0 => 2.3.x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319600 Title: maas-cli stack trace if .maascli.db unreadable To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1319600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680266] Re: [2.x, API] interface update will return successful with invalid params
** Changed in: maas Milestone: 2.3.0 => 2.3.x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680266 Title: [2.x, API] interface update will return successful with invalid params To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1680266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
** Changed in: maas Status: Fix Committed => Fix Released -- 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 set (during commissioning or testing) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial
@Chris, Can you attach the output of: maas machine get-curtin-config And attach the follow curtin log (you can grab that from the UI under the Installation tab). Also, this seems an issue widely with Ubuntu. Curtin is the one that writes this configuration, so marking this as Incomplete for MAAS and opening it in curtin. ** Changed in: maas Status: New => Incomplete ** Also affects: curtin Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573982 Title: LVM boot problem - volumes not activated after upgrade to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1573982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1444992] Re: fastpath install duplicates iSCSI initiator names, blocking iSCSI HW
We believe this is no longer an issue in the latest releases of MAAS. Please upgrade to the latest version of MAAS, and If you believe this issue is still present, please re-open this bug report or file a new one. ** 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/1444992 Title: fastpath install duplicates iSCSI initiator names, blocking iSCSI HW To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1444992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508087] Re: Unhandled UDP error during manual enlistment of xgene-2
I believe that in the latest versions of MAAS, this has now been fixed. If you believe this issue still exists, please re-open this bug report or file a new one. ** No longer affects: python-tx-tftp ** Changed in: python-tx-tftp (Ubuntu) Status: New => Invalid ** 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/1508087 Title: Unhandled UDP error during manual enlistment of xgene-2 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1508087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319600] Re: maas-cli stack trace if .maascli.db unreadable
** Changed in: maas Milestone: None => 2.3.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319600 Title: maas-cli stack trace if .maascli.db unreadable To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1319600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442112] Re: booting ppc64el with hwe-u kernel hangs in initrd
** 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/1442112 Title: booting ppc64el with hwe-u kernel hangs in initrd To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1442112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307614] Re: MAAS sometimes attempts to install to USB flash drive
** Changed in: maas Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307614 Title: MAAS sometimes attempts to install to USB flash drive To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1307614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580279] Re: [2.0] maas-cli 2.0 doesn't find 1.0 api
** Changed in: maas Milestone: 2.0.0 => next ** Changed in: maas Status: Triaged => Won't Fix ** Changed in: maas (Ubuntu) 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/1580279 Title: [2.0] maas-cli 2.0 doesn't find 1.0 api To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1580279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637246] Re: MaaS should use configured names for VLAN interfaces
** Changed in: maas (Ubuntu) Status: New => Fix Released ** Changed in: maas/2.0 Status: Triaged => Won't Fix ** Changed in: maas/2.0 Milestone: 2.0.1 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637246 Title: MaaS should use configured names for VLAN interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1637246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729127] Re: storage: No available machine matches constraints
Hi James, Can you please provide the following: 1. MAAS version and logs (/var/log/maas/regiond.log,maas.log)' 2. The dump of machine that would satisfy constraints: e.g. maas admin machines read hostname= 3. Can you provide the Juju debug lab where it is making a request to MAAS sending the constraints? I wanna see the difference between the juju command (in the bug report) and the actual request that juju made to MAAS. Thanks! ** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** Changed in: maas (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729127 Title: storage: No available machine matches constraints To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1729127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729127] Re: storage: No available machine matches constraints
debug log* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729127 Title: storage: No available machine matches constraints To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1729127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
I've verified these two manually! Thanks for all the work! ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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 set (during commissioning or testing) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565467] Re: twistd3 crashed with PermissionError in touch(): [Errno 13] Permission denied: '/etc/maas/rackd.conf'
while there's a traceback, the reality of it is that MAAS itself recovers, so it is not immediately a blocking issue. ** Changed in: maas Milestone: None => 2.3.x ** Changed in: maas Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565467 Title: twistd3 crashed with PermissionError in touch(): [Errno 13] Permission denied: '/etc/maas/rackd.conf' To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1565467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
Bumping this to critical provided that at this point, this completely breaks MAAS. ** Changed in: resolvconf (Ubuntu Xenial) Importance: Medium => Critical -- 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 set (during commissioning or testing) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
Also, I've tested this in GMAAS and confirm the fix works! -- 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 set (during commissioning or testing) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707999] Re: pod VM fails to PXE boot after receiving multiple DHCP offers, for different IPs, from the dhcp server
** Changed in: ipxe (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707999 Title: pod VM fails to PXE boot after receiving multiple DHCP offers, for different IPs, from the dhcp server To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1707999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726909] Re: Nodes fail deploying with 17.10 due to hang on "waiting for network" at boot
*** This bug is a duplicate of bug 1721808 *** https://bugs.launchpad.net/bugs/1721808 You need a newer version of curtin, which is currently available on xenial-proposed. ** Changed in: maas Status: Confirmed => Invalid ** Changed in: maas (Ubuntu Xenial) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726909 Title: Nodes fail deploying with 17.10 due to hang on "waiting for network" at boot To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1726909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
@Mark, I do have access (just tested). I'll give it a try tomorrow! Thanks! -- 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 set (during commissioning or testing) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724181] Re: maas-cli missing dependencies: netifaces, tempita
** Also affects: maas Importance: Undecided Status: New ** No longer affects: maas (Ubuntu) ** Changed in: maas Milestone: None => 2.3.0beta3 ** Also affects: maas/2.2 Importance: Undecided Status: New ** Changed in: maas/2.2 Milestone: None => 2.2.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724181 Title: maas-cli missing dependencies: netifaces, tempita To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1724181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707999] Re: pod VM fails to PXE boot after receiving multiple DHCP offers, for different IPs, from the dhcp server
As David said, and to clarify, I was planning on uploading this patch to the archive, but I wanted to double check with you guys to ensure that the implementation is sane from your perspective, as this will affect ipxe clients that receive DHCPNACKs. Also, it would be good to get a different perspective from the RFC standpoint. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707999 Title: pod VM fails to PXE boot after receiving multiple DHCP offers, for different IPs, from the dhcp server To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1707999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1389811] Re: tgtadm: out of memory crash
@Christian, We cannot test the zesty package nor grab the package and install it in xenial because it needs to be built against the xenial archive for the library linking. As such, I would recommend this patch is pushed to -proposed where we can test it against the libraries of the archive. That would allow us to test it just once and be pushed into -xenial, and not have to test it in the PPA and then again test it in -proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1389811 Title: tgtadm: out of memory crash To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1389811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1389811] Re: tgtadm: out of memory crash
** Changed in: maas Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1389811 Title: tgtadm: out of memory crash To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1389811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707999] Re: pod VM fails to PXE boot after receiving multiple DHCP offers, for different IPs, from the dhcp server
** Patch added: "handle-dhcp-nack.patch" https://bugs.launchpad.net/maas/+bug/1707999/+attachment/4969236/+files/handle-dhcp-nack.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707999 Title: pod VM fails to PXE boot after receiving multiple DHCP offers, for different IPs, from the dhcp server To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1707999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707999] Re: pod VM fails to PXE boot after receiving multiple DHCP offers, for different IPs, from the dhcp server
** Changed in: maas Status: Incomplete => Invalid ** Changed in: maas/2.2 Status: Incomplete => Invalid ** Changed in: ipxe (Ubuntu) Assignee: (unassigned) => Andres Rodriguez (andreserl) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707999 Title: pod VM fails to PXE boot after receiving multiple DHCP offers, for different IPs, from the dhcp server To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1707999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707999] Re: pod VM fails to PXE boot after receiving multiple DHCP offers, for different IPs, from the dhcp server
** Changed in: maas Assignee: (unassigned) => Blake Rouse (blake-rouse) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707999 Title: pod VM fails to PXE boot after receiving multiple DHCP offers, for different IPs, from the dhcp server To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1707999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
** Changed in: maas Status: Fix Committed => Fix Released -- 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 set (during commissioning or testing) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707999] Re: pod VM fails to PXE boot after receiving multiple DHCP offers, for different IPs, from the dhcp server
** Also affects: ipxe (Ubuntu) Importance: Undecided Status: New ** Changed in: ipxe (Ubuntu) Importance: Undecided => Critical ** Changed in: maas Status: Triaged => Incomplete ** Changed in: maas/2.2 Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707999 Title: pod VM fails to PXE boot after receiving multiple DHCP offers, for different IPs, from the dhcp server To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1707999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
** Changed in: maas Assignee: (unassigned) => Andres Rodriguez (andreserl) ** Changed in: maas Status: Confirmed => In Progress -- 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 set (during commissioning or testing) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
** Changed in: maas Milestone: 2.3.0 => 2.3.0beta2 -- 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 set (during commissioning or testing) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382774] Re: Postgresql installation for MAAS fails on locales missing language packs
** Tags added: internal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382774 Title: Postgresql installation for MAAS fails on locales missing language packs To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570633] Re: [2.0 beta 2] Nodes fail to remain powered after Trusty commission with "Allow SSH" selected
** Tags added: internal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570633 Title: [2.0 beta 2] Nodes fail to remain powered after Trusty commission with "Allow SSH" selected To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1570633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394306] Re: maas 1.7 upgrade: document potential need for maas-proxy.conf manual setup migration
** Changed in: maas Status: Triaged => Won't Fix ** Changed in: maas (Ubuntu) Status: New => 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/1394306 Title: maas 1.7 upgrade: document potential need for maas-proxy.conf manual setup migration To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1394306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1389811] Re: tgtadm: out of memory crash
** 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/1389811 Title: tgtadm: out of memory crash To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1389811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717287] Re: maas-enlist doesn't work when provided with serverurl with IPv6 address
** Changed in: maas Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717287 Title: maas-enlist doesn't work when provided with serverurl with IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1717287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713795] Re: [1.9] Unable to install 14.04, shim.efi.signed renamed
** 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. https://bugs.launchpad.net/bugs/1713795 Title: [1.9] Unable to install 14.04, shim.efi.signed renamed To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1713795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590689] Re: MAAS 1.9.3 + Juju 1.25.5 - on the Juju controller node eth0 and juju-br0 interfaces have the same IP address at the same time
** Changed in: maas Status: Confirmed => Won't Fix ** Changed in: maas Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590689 Title: MAAS 1.9.3 + Juju 1.25.5 - on the Juju controller node eth0 and juju- br0 interfaces have the same IP address at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1590689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717287] Re: maas-enlist doesn't work when provided with serverurl with IPv6 address
** Changed in: maas Milestone: 2.3.0 => 2.3.0beta1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717287 Title: maas-enlist doesn't work when provided with serverurl with IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1717287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713795] Re: [1.9] Unable to install 14.04, shim.efi.signed renamed
@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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713795 Title: [1.9] Unable to install 14.04, shim.efi.signed renamed To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1713795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717287] Re: maas-enlist doesn't work when provided with serverurl with IPv6 address
** Changed in: maas/2.2 Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717287 Title: maas-enlist doesn't work when provided with serverurl with IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1717287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717287] Re: maas-enlist doesn't work when provided with serverurl with IPv6 address
** Changed in: maas/2.2 Assignee: (unassigned) => Andres Rodriguez (andreserl) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717287 Title: maas-enlist doesn't work when provided with serverurl with IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1717287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717287] Re: maas-enlist doesn't work when provided with serverurl with IPv6 address
** Also affects: maas/2.2 Importance: Undecided Status: New ** Changed in: maas/2.2 Milestone: None => 2.2.3 ** Changed in: maas/2.2 Importance: Undecided => High ** Changed in: maas/2.2 Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717287 Title: maas-enlist doesn't work when provided with serverurl with IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1717287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717287] Re: maas-enlist doesn't work when provided with serverurl with IPv6 address
** Changed in: maas Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717287 Title: maas-enlist doesn't work when provided with serverurl with IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1717287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
Hi All, So what's the latest status on this and/or what is the proposed fix? -- 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 set (during commissioning or testing) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642298] Re: Grub package upgrades overwrites NVRAM, causing MAAS boot order to be overwritten.
** Changed in: maas Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642298 Title: Grub package upgrades overwrites NVRAM, causing MAAS boot order to be overwritten. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1642298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642298] Re: Grub package upgrades overwrites NVRAM, causing MAAS boot order to be overwritten.
** Changed in: maas Milestone: 2.3.0 => 2.3.0alpha3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642298 Title: Grub package upgrades overwrites NVRAM, causing MAAS boot order to be overwritten. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1642298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717287] Re: maas-enlist doesn't work when provided with serverurl with IPv6 address
** Tags added: internal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717287 Title: maas-enlist doesn't work when provided with serverurl with IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1717287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717287] Re: maas-enlist doesn't work when provided with serverurl with IPv6 address
** Also affects: maas Importance: Undecided Status: New ** Changed in: maas Milestone: None => 2.3.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717287 Title: maas-enlist doesn't work when provided with serverurl with IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1717287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713795] Re: [1.9] Unable to install 14.04, shim.efi.signed renamed
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. ** Changed in: maas (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713795 Title: [1.9] Unable to install 14.04, shim.efi.signed renamed To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1713795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642298] Re: Grub package upgrades overwrites NVRAM, causing MAAS boot order to be overwritten.
** Changed in: maas Status: Confirmed => In Progress ** Also affects: maas/2.2 Importance: Undecided Status: New ** Changed in: maas/2.2 Milestone: None => 2.2.3 ** Changed in: maas/2.2 Importance: Undecided => High ** Changed in: maas/2.2 Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642298 Title: Grub package upgrades overwrites NVRAM, causing MAAS boot order to be overwritten. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1642298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716784] Re: Ephemeral boot error: alloc magic is broken at 0x94eceac0: 94e05880
>From our irc discussion: 18:27 < dpb> but it's booted just fine as recently as 2 days ago A new grub version was published on 2017-07-28 in 2.02~beta2-36ubuntu3.12. This seems like it could be a regression in grub that 2.02~beta2-36ubuntu3.13 (currently in proposed) could probably fix. ** Changed in: maas Status: New => Incomplete ** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716784 Title: Ephemeral boot error: alloc magic is broken at 0x94eceac0: 94e05880 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1716784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716498] Re: maas reloads bind9 every 2 seconds, bind keeps becoming unresponsive
*** This bug is a duplicate of bug 1711700 *** https://bugs.launchpad.net/bugs/1711700 Hi Jeff, If MAAS is reloading DNS constantly, it is because you have machines from the dynamic range obtaining new IP addresses. That said, the issue is not MAAS reloading, but rather, it is bind failing to reload. That said, we've taking steps in MAAS to improve the reloading to avoid such issues. Marking this bug as duplicate. ** This bug has been marked a duplicate of bug 1711700 [2.x] MAAS should avoid updating DNS if nothing changed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716498 Title: maas reloads bind9 every 2 seconds, bind keeps becoming unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1716498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713795] Re: [1.9] Unable to install 14.04, shim.efi.signed renamed
** Description changed: - After a recent update, it's no longer possible to install Ubuntu 14.04 - with MaaS 1.9.5 . This is on a new installation of MaaS on 14.04. + [Impact] + After a recent update, it's no longer possible to install Ubuntu 14.04 with MaaS 1.9.5 . This is on a new installation of MaaS on 14.04. The change appears to be related to this change: https://launchpad.net/ubuntu/+source/shim-signed/1.32~14.04.2 - This was reported on the mailing list and via maas@freenode IRC. + [Test Case] + 1. Install maas 1.9 + 2. Attempt to import images + 2.1 without the fix, MAAS wont be able to import images. + 2.2. with the fix, MAAS will be able to import images. - https://lists.ubuntu.com/archives/maas-devel/2017-August/002689.html - - The suggested workaround (copying the shimx64.efi.signed to - shim.efi.signed in /usr/lib/shim) doesn't seem to work - possibly the - file is looked for in a temp directory created, as the error is: - `exceptions.IOError: [Errno 2] No such file or directory: u'/tmp/maas- - lokTRb/usr/lib/shim/shim.efi.signed'` + [Regression Potential] + Minimal. Since only the name of a binary has changed, this has minimal impact provided the binary doesn't get renamed again. --- # 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.9.5+bzr4599-0ubuntu1~14.04.1 all MAAS server all-in-one metapackage ii maas-cli 1.9.5+bzr4599-0ubuntu1~14.04.1 all MAAS command line API tool ii maas-cluster-controller 1.9.5+bzr4599-0ubuntu1~14.04.1 all MAAS server cluster controller ii maas-common 1.9.5+bzr4599-0ubuntu1~14.04.1 all MAAS server common files ii maas-dhcp1.9.5+bzr4599-0ubuntu1~14.04.1 all MAAS DHCP server ii maas-dns 1.9.5+bzr4599-0ubuntu1~14.04.1 all MAAS DNS server ii maas-proxy 1.9.5+bzr4599-0ubuntu1~14.04.1 all MAAS Caching Proxy ii maas-region-controller 1.9.5+bzr4599-0ubuntu1~14.04.1 all MAAS server complete region controller ii maas-region-controller-min 1.9.5+bzr4599-0ubuntu1~14.04.1 all MAAS Server minimum region controller ii python-django-maas 1.9.5+bzr4599-0ubuntu1~14.04.1 all MAAS server Django web framework ii python-maas-client 1.9.5+bzr4599-0ubuntu1~14.04.1 all MAAS python API client ii python-maas-provisioningserver 1.9.5+bzr4599-0ubuntu1~14.04.1 all MAAS server provisioning libraries ** Description changed: [Impact] After a recent update, it's no longer possible to install Ubuntu 14.04 with MaaS 1.9.5 . This is on a new installation of MaaS on 14.04. The change appears to be related to this change: https://launchpad.net/ubuntu/+source/shim-signed/1.32~14.04.2 [Test Case] 1. Install maas 1.9 2. Attempt to import images 2.1 without the fix, MAAS wont be able to import images. 2.2. with the fix, MAAS will be able to import images. [Regression Potential] Minimal. Since only the name of a binary has changed, this has minimal impact provided the binary doesn't get renamed again. - - --- - # 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.9.5+bzr4599-0ubuntu1~14.04.1 all MAAS server all-in-one metapackage - ii maa
[Bug 1713795] Re: [1.9] Unable to install 14.04, shim.efi.signed renamed
** Changed in: maas (Ubuntu) Status: In Progress => New ** Changed in: maas (Ubuntu) Assignee: Andres Rodriguez (andreserl) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713795 Title: [1.9] Unable to install 14.04, shim.efi.signed renamed To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1713795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713795] Re: [1.9] Unable to install 14.04, shim.efi.signed renamed
Hi John, There's a patch attached which you can apply to resolve this issue. We are working to get this SRU'd. Thanks! ** Changed in: maas Status: Triaged => In Progress ** Changed in: maas (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713795 Title: [1.9] Unable to install 14.04, shim.efi.signed renamed To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1713795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642298] Re: Grub upgrades overwrites NVRAM cuasing MAAS/curtin boot order to be overwriten
The work around is to pass a debconf configuration option to grub2 package to not update the NVRAM on package upgrade. ** Changed in: maas Assignee: (unassigned) => Andres Rodriguez (andreserl) ** Changed in: maas Status: New => Confirmed ** Changed in: maas Importance: Undecided => High ** Summary changed: - Grub upgrades overwrites NVRAM cuasing MAAS/curtin boot order to be overwriten + Grub package upgrades overwrites NVRAM, causing MAAS boot order to be overwritten. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642298 Title: Grub package upgrades overwrites NVRAM, causing MAAS boot order to be overwritten. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1642298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642298] Re: Grub upgrades overwrites NVRAM cuasing MAAS/curtin boot order to be overwriten
** Summary changed: - UEFI Xenial install sets computer to boot from hard disk + Grub upgrades overwrites NVRAM cuasing MAAS/curtin boot order to be overwriten -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642298 Title: Grub package upgrades overwrites NVRAM, causing MAAS boot order to be overwritten. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1642298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642298] Re: UEFI Xenial install sets computer to boot from hard disk
In ipmitool 1.18.17+ $ ipmitool -I lanplus -U xxx -P xxx -H X.X.X.X chassis bootdev pxe options=persistent,efiboot Set Boot Device to pxe $ ipmitool -I lanplus -U xxx -P xxx -H X.X.X.X chassis bootparam get 5 Boot parameter version: 1 Boot parameter 5 is valid/unlocked Boot parameter data: a00402 Boot Flags : - Boot Flag Valid - Options apply to only next boot - BIOS EFI boot - Boot Device Selector : Force PXE - Console Redirection control : System Default - Lock Out Sleep Button - BIOS verbosity : Request console redirection be enabled - BIOS Mux Control Override : BIOS uses recommended setting of the mux at the end of POST -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642298 Title: UEFI Xenial install sets computer to boot from hard disk To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1642298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714090] Re: Upgrading grub2 shouldn't overwrite EFI boot order
So the concern we are primarily interested on is the upgrade scenario. Effectively, if 'ubuntu' is already in the boot order (and it is not the first one), on grub2 upgrade, it shouldn't be overwriting the current BootOrder (e.g. because we specifically configured it to Boot from the Network first). So on package upgrades, it should be preserving the current boot order. ** Summary changed: - Upgrading grub2 shouldn't overwrite EFI boot order + grub2 upgrade doesn't preserve current boot order. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714090 Title: grub2 upgrade doesn't preserve current boot order. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1714090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714090] [NEW] grub2 upgrade doesn't preserve current boot order.
Public bug reported: This is a follow up discussion from #1642298 and filing this bug to keep a record. On a fresh Ubuntu install, grub2 overwrites the NVRAM and updates to boot order to have Ubuntu as the first boot device. This affects situations in which PXE had been set the first boot device in the boot order as it would overwrite it. However, every single time grub2 package upgrades, it will overwrite the NVRAM and completely override the boot order again. For example, consider that ubuntu is first in the boot order. efibootmgr -v BootCurrent: Timeout: 2 seconds BootOrder: ,0001 Boot* ubuntu Boot0001 PCI LAN But the administrator changed Network to be the first in the boot order. efibootmgr -v BootCurrent: 0001 Timeout: 2 seconds BootOrder: 0001, Boot0001* PCI LAN Boot ubuntu After a package upgrade, grub will overwrite the NVRAM and change this back to: efibootmgr -v BootCurrent: Timeout: 2 seconds BootOrder: ,0001 Boot* ubuntu Boot0001 PCI LAN ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714090 Title: grub2 upgrade doesn't preserve current boot order. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1714090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642298] Re: UEFI Xenial install sets computer to boot from hard disk
Hi Rod, Judging by your message in #2, unless I'm missing something, you would have not been able to re-deploy the machine because efibootmgr had set the boot order to the disk first. When you re-deployed the machine, MAAS told that machine that "on the next boot, PXE boot". " - The node was already deployed and running when I started. It had the "ubuntu" entry set as the default in "efibootmgr" output, suggesting that when it was last deployed (about a month ago?), the bug existed. - I redeployed, and it worked as expected. " As far as IPMI, you do have a way to ensure that the next boot, boots from PXE. Example EFI boot config for freeipmi-tools: Section Chassis_Boot_Flags Boot_Flags_Persistent Yes BIOS_Boot_TypeEFI Boot_Device PXE EndSection And exactly, we as Canonical can control how and when we use efibootmgr to adjust the boot order. The fact that we are, by default, completely eliminating the boot order that has been set on the BIOS by the administrator, is IMHO, the wrong approach. If the administrator has, by default, set PXE as the first in the boot order, then grub should not be overriding such configuration. There is a reason why the administrator has set the boot order to PXE first and Ubuntu shouldn't be changing that. While I understand you guys have been discussing the solution, and whatever the solution may be, that doesn't change the fact that both Blake and I agree in the fact that grub shouldn't be changing the boot order by default. The fact that it is currently doing it overriding BIOS settings and we want to work around it, is a completely different matter. Also, it doesn't mean that curtin shouldn;t be setting this by default. IMHO, as I already expressed, curtin should ensure setting the grub to not update the nvram to ensure that curtin maintains what it does today. Today, after installation, curtin uses efibootmgr *AND* ensures that PXE is first on the boot order, and the disk is second as a fallback. As such, curtin needs to ensure, by default that grub does not overwrite the efibootmgr configuration that curtin already made. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642298 Title: UEFI Xenial install sets computer to boot from hard disk To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1642298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642298] Re: UEFI Xenial install sets computer to boot from hard disk
Hey guys. Sorry for joining the party late. But let me see if I understand the full extent of the problem here. 0. A machine PXE boots off MAAS, installs Ubuntu in it, grub gets installed and configured without updating the NVRAM. 1. The machine reboots, PXE's, boots from local disk, and finishes installation (an unnecessary step). 2. An upgrade of overwrites NVRAM to boot from disk. 3. A reboot boots from disk directly and not from network. 4. If we re-deploy, the machine is told to PXE boot via the BMC. 5. If we re-deploy the machine, the machine PXE boots off MAAS again and installs. The machine reboots and boots off the disk. Now, the above only becomes a real problem when. The machine does not support changing the boot order remotely via IPMI or other power management mechanism. - That, however, is a certification problem. MAAS expects to be able to control the boot order of the machine. If this is not possible, it is a certification challenge. That said, regardless of being able to set the boot order or not, I see a completely different problem: 1. The administrator configured their BIOS with a specific boot order. 2. The administrator installs ubuntu, expecting their BIOS boot order configuration to remain (somewhat) unchanged (specially when it is set to boot from network first). 3. The software (grub2) overrides the BIOS' boot order to boot from disk. This overrides the fact that the administrator set the BIOS boot order to PXE first. So, based on this, the REAL bug that needs to be fixed is that grub needs to somewhat respect the boot order set in the BIOS. For example: 1. If BIOS Boot order before Ubuntu install is: 1. PXE, 2. HDD1, 3. HDD2 2. And we install Ubuntu on HDD2, then grub needs to /somewhat/ preserve the boot order and make it so: 1. PXE, 2. HDD2, 3. HDD1. To conclude: 1. The real bug is in grub, and this needs to be addressed to properly preserve the boot order in a sane way if PXE/Network boot is set as the first boot type on the BIOS boot order. 2. If we want to make work arounds in the meantime, I think it is acceptable to say that curtin should tell grub to disable nvram updating by default, and only enabled it if the users wishes so, so we can respect what was set on the firmware. Either way, IMHO, the real solution is to fix grub. ** Changed in: maas Status: Triaged => Incomplete ** Changed in: maas Importance: High => Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642298 Title: UEFI Xenial install sets computer to boot from hard disk To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1642298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713795] Re: [1.9] Unable to install 14.04, shim.efi.signed renamed
** Changed in: maas Assignee: (unassigned) => Andres Rodriguez (andreserl) ** Changed in: maas Milestone: None => 1.9.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713795 Title: [1.9] Unable to install 14.04, shim.efi.signed renamed To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1713795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713795] Re: [1.9] Unable to install 14.04, shim.efi.signed renamed
** Changed in: maas Importance: Undecided => Critical ** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** Changed in: maas (Ubuntu) Importance: Undecided => Critical ** Changed in: maas (Ubuntu) Assignee: (unassigned) => Andres Rodriguez (andreserl) ** Changed in: maas (Ubuntu) Status: New => Triaged ** Changed in: maas Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713795 Title: [1.9] Unable to install 14.04, shim.efi.signed renamed To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1713795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680266] Re: [2.x, API] interface update will return successful with invalid params
** Summary changed: - interface update will return successful with invalid params + [2.x, API] interface update will return successful with invalid params -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680266 Title: [2.x, API] interface update will return successful with invalid params To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1680266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken
** Changed in: maas Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705504] Re: [2.3] on install MAAS has system warnings
** Changed in: maas Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705504 Title: [2.3] on install MAAS has system warnings To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1705504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning)
Scott, What information are you looking with the time stamps so I can reproduce this and get you that exact info? On Mon, Aug 21, 2017 at 4:31 PM Scott Moser wrote: > There are no timestamps shown in your log, but guessing by the time > stamp of your paste, you ran the pastebinit command ~ 13 minutes after > cloud-init had finished. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1711760 > > Title: > [2.3] resolv.conf is not set (during commissioning) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions > -- Andres Rodriguez (RoAkSoAx) Ubuntu Server Developer MSc. Telecom & Networking Systems Engineer -- 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 set (during commissioning) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning)
ubuntu@withkvm:~$ cat /proc/cmdline
BOOT_IMAGE=ubuntu/amd64/generic/xenial/daily/boot-kernel nomodeset
root=squash:http://192.168.122.2:5248/images/ubuntu/amd64/generic/xenial/daily/squashfs
ro ip=withkvm:BOOTIF ip6=off overlayroot=tmpfs
overlayroot_cfgdisk=disabled cc:{'datasource_list': ['MAAS']}end_cc
cloud-config-url=http://192.168.122.2:5240/MAAS/metadata/latest/by-id/xh33gw/?op=get_preseed
apparmor=0 log_host=192.168.122.2 log_port=514
initrd=ubuntu/amd64/generic/xenial/daily/boot-initrd BOOTIF=01-52-54-00-03-02-6e
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => New
--
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 set (during commissioning)
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705504] Re: [2.3] on install MAAS has system warnings
** Changed in: maas Milestone: 2.3.0 => 2.3.0alpha2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705504 Title: [2.3] on install MAAS has system warnings To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1705504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken
** Changed in: maas Milestone: 2.3.0 => 2.3.0alpha2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711760] [NEW] [2.3] resolv.conf is not set (during commissioning)
Public bug reported:
Using MAAS 2.3, during commissioning (and likely in the rest of the
ephemeral environment) we have noticed that resolv.conf is not set with
the DNS server.
That said, during the commissioning process, MAAS does not send any
metadata to cloud-init to configure the network, rather, we expect the
image to boot from the network via DHCP. So, cloud-init writes:
ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback
# control-manual ens3
iface ens3 inet dhcp
broadcast 192.168.122.255
dns-nameservers 192.168.122.2
gateway 192.168.122.1
netmask 255.255.255.0
Which correctly includes the DNS server. However:
ubuntu@manual:~$ ping google.com
ping: unknown host google.com
If restart the interfacE:
ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
ifdown: interface ens3 not configured
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/ens3/52:54:00:ea:57:31
Sending on LPF/ens3/52:54:00:ea:57:31
Sending on Socket/fallback
DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67
(xid=0x5403eb14)
DHCPOFFER of 192.168.122.195 from 192.168.122.2
DHCPACK of 192.168.122.195 from 192.168.122.2
Restarting ntp (via systemctl): ntp.service.
bound to 192.168.122.195 -- renewal in 290 seconds.
ubuntu@manual:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.122.2
search maas
ubuntu@manual:~$ ping google.com
PING google.com (216.58.192.46) 56(84) bytes of data.
64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): icmp_seq=1 ttl=52
time=7.47 ms
^C
--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 7.472/7.472/7.472/0.000 ms
As such, this either seems like a bug in Ubuntu, or caused by cloud-init
when writing e/n/i.d/50-cloud-init.cfg
ubuntu@manual:~$ dpkg -l | grep cloud-init
ii cloud-init 0.7.9-153-g16a7302f-0ubuntu1~16.04.2
all Init scripts for cloud instances
ii cloud-initramfs-copymods 0.27ubuntu1.4
all copy initramfs modules into root filesystem for later use
ii cloud-initramfs-dyn-netconf 0.27ubuntu1.4
all write a network interface file in /run for BOOTIF
ubuntu@manual:~$ uname -a
Linux manual 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@manual:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename: xenial
ubuntu@manual:~$ pastebinit /var/log/cloud-init.log
http://paste.ubuntu.com/25342738/
ubuntu@manual:~$ pastebinit /var/log/cloud-init-output.log
http://paste.ubuntu.com/25342740/
** Affects: maas
Importance: Undecided
Status: New
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Using MAAS 2.3, during commissioning (and likely in the rest of the
ephemeral environment) we have noticed that resolv.conf is not set with
the DNS server.
That said, during the commissioning process, MAAS does not send any
metadata to cloud-init to configure the network, rather, we expect the
image to boot from the network via DHCP. So, cloud-init writes:
- ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
+ ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback
# control-manual ens3
iface ens3 inet dhcp
- broadcast 192.168.122.255
- dns-nameservers 192.168.122.2
- gateway 192.168.122.1
- netmask 255.255.255.0
+ broadcast 192.168.122.255
+ dns-nameservers 192.168.122.2
+ gateway 192.168.122.1
+ netmask 255.255.255.0
Which correctly includes the DNS server. However:
ubuntu@manual:~$ ping goo
[Bug 1711203] Re: Deployments fail when Secure Boot enabled
Since 2.02-beta2-36ubuntu3.11 works but .12 (which is the latest in Xenial updates doesn't) this seems to confirm the regression in grub. marking invalid for NAAS and curtin! Maas will automatically pick up a fixed grub once on the archive. ** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Changed in: curtin Status: Incomplete => Invalid ** Changed in: maas Status: Incomplete => Invalid -- 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 about this bug go to: https://bugs.launchpad.net/curtin/+bug/1711203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711197] Re: distro-info returns an object instead of a dictionary which breaks applications relying on it
FWIW, while this change may things nicer moving forward, this makes it very difficult to maintain code that needs to work on both, Xenial and Artful+. Having the old API still available would allow applications to continue to rely on the module without having to do any hackery, specially, since the module doesn't seem to expose any versioning information. While I acknowledge that the change is for the better, to address these cases it should at least expose version information so applications can adapt the work on the different behavior of the module in a different release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711197 Title: distro-info returns an object instead of a dictionary which breaks applications relying on it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/1711197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711197] Re: distro-info returns an object instead of a dictionary which breaks applications relying on it
Other areas this doesn't work anymore: ubuntu = UbuntuDistroInfo() ubuntu._rows ... AttributeError: 'UbuntuDistroInfo' object has no attribute '_rows' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711197 Title: distro-info returns an object instead of a dictionary which breaks applications relying on it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/1711197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711197] [NEW] distro-info returns an object instead of a dictionary which breaks applications relying on it
Public bug reported: A new version of distro-info has just broken all applications that rely on the python module. One of this applications is MAAS. Example: # In Xenial, you would do something like: from distro_info import UbuntuDistroInfo info = UbuntuDistroInfo() for row in info._avail(info._date): print(row['series']) # In Artful, this no longer works. It would have to be done like: from distro_info import UbuntuDistroInfo info = UbuntuDistroInfo() for row in info._avail(info._date): print(row.series) ** Affects: distro-info (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711197 Title: distro-info returns an object instead of a dictionary which breaks applications relying on it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/1711197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708651] Re: [SRU] MAAS 2.2.2
I've tested this both in Xenial and Zesty as per the bug report testing from proposed section, and can verify that everything works as expected! ** Tags removed: verification-needed verification-needed-xenial verification-needed-zesty ** Tags added: verification-done verification-done-xenial verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708651 Title: [SRU] MAAS 2.2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1708651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708651] Re: [SRU] MAAS 2.2.2
Hi Steve, python3-googleapi is present in the Archive. https://packages.ubuntu.com /xenial-updates/python/python3-googleapi The reason why we need a conflicts is because both MAAS and python3-googleapi installs in /usr/lib/python3/dist-packages/apiclient, which obviously we need a conflicts. ** Changed in: maas (Ubuntu Xenial) Status: Incomplete => New ** Changed in: maas (Ubuntu Zesty) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708651 Title: [SRU] MAAS 2.2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1708651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708651] Re: [SRU] MAAS 2.2.2
** Description changed: [Impact] This is a new upstream release that addresses various upstream bugs. MAAS 2.2.2 does NOT introduce any new features. Please see CHANGELOG for further details. [Test Case] MAAS testing has been done in various cases, partially documented https://wiki.ubuntu.com/MAASUpdates. This include: + All MAAS Upstream releases follow the following testing: + 1. Manual Fresh installation of MAAS 2. Manual upgrade from the previous Ubuntu Release. 3. Automated (CI) testing of MAAS install and operation as per the MAAS' CI. 4. Automated (CI) testing of MAAS install and operation against other Canonical's product (juju, Canonical OpenStack & Kubernetes) provided by the Canonical Solutions QA Team. 5. Manual split region/rack test are performed. This is to ensure that if we upgrade a MAAS Region to a newer version, the MAAS rack of the older version remains connected and operational. + + Packages from proposed have the following testing to guard against + misbuilds: + + 1. Manual Fresh installation of MAAS + 2. Manual upgrade from the previous Ubuntu Release. + 3. Manual split region/rack tests. All of this includes verifying normal operation, issues fixed, and ensuring that Canonical Cloud solutions can inter-operate. MAAS releases are also now vetted by the Solutions QA team. [Regression Potential] Minimal (For MAAS itself). MAAS 2.2.2 is just a point release that addresses bugs and does not change any behavior. It has minimum risk for backward compatibility issues. It does NOT include any database migrations as such, upgrade risks are very minimal as well. ** Description changed: [Impact] This is a new upstream release that addresses various upstream bugs. MAAS 2.2.2 does NOT introduce any new features. Please see CHANGELOG for further details. [Test Case] MAAS testing has been done in various cases, partially documented https://wiki.ubuntu.com/MAASUpdates. This include: All MAAS Upstream releases follow the following testing: 1. Manual Fresh installation of MAAS 2. Manual upgrade from the previous Ubuntu Release. 3. Automated (CI) testing of MAAS install and operation as per the MAAS' CI. 4. Automated (CI) testing of MAAS install and operation against other Canonical's product (juju, Canonical OpenStack & Kubernetes) provided by the Canonical Solutions QA Team. 5. Manual split region/rack test are performed. This is to ensure that if we upgrade a MAAS Region to a newer version, the MAAS rack of the older version remains connected and operational. Packages from proposed have the following testing to guard against misbuilds: - 1. Manual Fresh installation of MAAS - 2. Manual upgrade from the previous Ubuntu Release. - 3. Manual split region/rack tests. + 1. Manual Fresh installation, configuration and deployment of machines. + 2. Manual upgrade from the previous Ubuntu Release (and ensure continued operation) + 3. Includes split region/rack tests. All of this includes verifying normal operation, issues fixed, and ensuring that Canonical Cloud solutions can inter-operate. MAAS releases are also now vetted by the Solutions QA team. [Regression Potential] Minimal (For MAAS itself). MAAS 2.2.2 is just a point release that addresses bugs and does not change any behavior. It has minimum risk for backward compatibility issues. It does NOT include any database migrations as such, upgrade risks are very minimal as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708651 Title: [SRU] MAAS 2.2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1708651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708651] Re: [SRU] MAAS 2.2.2
** Changed in: maas (Ubuntu) Status: New => 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/1708651 Title: [SRU] MAAS 2.2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1708651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1696752] Re: [SRU] MAAS 2.2.0
** Changed in: maas (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696752 Title: [SRU] MAAS 2.2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1696752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708651] [NEW] [SRU] MAAS 2.2.2
Public bug reported: [Impact] This is a new upstream release that addresses various upstream bugs. MAAS 2.2.2 does NOT introduce any new features. Please see CHANGELOG for further details. [Test Case] MAAS testing has been done in various cases, partially documented https://wiki.ubuntu.com/MAASUpdates. This include: 1. Manual Fresh installation of MAAS 2. Manual upgrade from the previous Ubuntu Release. 3. Automated (CI) testing of MAAS install and operation as per the MAAS' CI. 4. Automated (CI) testing of MAAS install and operation against other Canonical's product (juju, Canonical OpenStack & Kubernetes) provided by the Canonical Solutions QA Team. 5. Manual split region/rack test are performed. This is to ensure that if we upgrade a MAAS Region to a newer version, the MAAS rack of the older version remains connected and operational. All of this includes verifying normal operation, issues fixed, and ensuring that Canonical Cloud solutions can inter-operate. MAAS releases are also now vetted by the Solutions QA team. [Regression Potential] Minimal (For MAAS itself). MAAS 2.2.2 is just a point release that addresses bugs and does not change any behavior. It has minimum risk for backward compatibility issues. It does NOT include any database migrations as such, upgrade risks are very minimal as well. ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Affects: maas (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: maas (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: maas (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: maas (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708651 Title: [SRU] MAAS 2.2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1708651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705504] Re: on install MAAS has system warnings
** Also affects: maas Importance: Undecided Status: New ** Changed in: maas Milestone: None => 2.3.0 ** Changed in: maas Importance: Undecided => High ** Changed in: maas Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705504 Title: on install MAAS has system warnings To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1705504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1696752] Re: [SRU] MAAS 2.2.0
The versions in -proposed for all releases have been tested as per the description of the bug. 2.2.0+bzr6054-0ubuntu2~17.04.1 2.2.0+bzr6054-0ubuntu2~16.10.1 2.2.0+bzr6054-0ubuntu2~16.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696752 Title: [SRU] MAAS 2.2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1696752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1696752] Re: [SRU] MAAS 2.2.0
I've verified -proposed on all releases and marked this as verification- done. ** Tags removed: verification-needed verification-needed-xenial verification-needed-yakkety verification-needed-zesty ** Tags added: verification-done verification-done-xenial verification-done-yakkety verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696752 Title: [SRU] MAAS 2.2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1696752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1704538] Re: package maas-region-controller 2.2.0+bzr6054-0ubuntu2~17.04.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
MAAS 2.2 does not support Django 1.11, which is in Artful. This is causing the failure you are seeing. MAAS 2.3 will fix this and the first alpha wi be released next week, and will replace this package. As such, im marking this as won't fix. ** Changed in: maas (Ubuntu) Status: New => 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/1704538 Title: package maas-region-controller 2.2.0+bzr6054-0ubuntu2~17.04.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1704538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664822] Re: [2.2] MAAS IPMI autodiscover should enable IPMI-over-LAN if disabled
This fix will be made available in 2.2.2 which will be backported to Xenial! ** Also affects: maas/2.2 Importance: Undecided Status: New ** Changed in: maas/2.2 Milestone: None => 2.2.2 ** No longer affects: maas (Ubuntu) ** Changed in: maas/2.2 Importance: Undecided => High ** Changed in: maas/2.2 Status: New => Triaged ** Changed in: maas/2.2 Assignee: (unassigned) => Andres Rodriguez (andreserl) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664822 Title: [2.2] MAAS IPMI autodiscover should enable IPMI-over-LAN if disabled To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1664822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543204] Re: cloud images should have /lib/modules inside
** Changed in: maas-images Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543204 Title: cloud images should have /lib/modules inside To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/1543204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568918] Re: Add support for lts-xenial kernel flavours in trusty
** Changed in: maas-images Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1568918 Title: Add support for lts-xenial kernel flavours in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/1568918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
