[Bug 1765476] Re: [needs-packaging] candid
** Changed in: 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/1765476 Title: [needs-packaging] candid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1765476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823718] Re: Installation fails with Python3.7 SyntaxError on Ubuntu Disco
Marking as fix released, as this has been fixed in eoan. The fix and/or new upstream needs to be backported. ** Changed in: python-libmaas (Ubuntu) Status: Confirmed => 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/1823718 Title: Installation fails with Python3.7 SyntaxError on Ubuntu Disco To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1823718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823718] Re: Installation fails with Python3.7 SyntaxError on Ubuntu Disco
** Also affects: python-libmaas (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: python-libmaas (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: python-libmaas (Ubuntu Bionic) 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/1823718 Title: Installation fails with Python3.7 SyntaxError on Ubuntu Disco To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1823718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832295] Re: lighttpd broken by OpenSSL update
** Changed in: lighttpd (Ubuntu) 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/1832295 Title: lighttpd broken by OpenSSL update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lighttpd/+bug/1832295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655447] Re: IEEE indexes in netaddr package may not match data in ieee-data package
** Changed in: maas/2.3 Milestone: 2.3.6 => 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/1655447 Title: IEEE indexes in netaddr package may not match data in ieee-data package To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1655447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831134] Re: Pods Cannot allocate memory, even with memory_over_commit_ratio set 10.0
The error message below comes from QEMU 2019-05-30T17:08:05.186659Z qemu-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory AS such, what I see here is that MAAS is allowing you to create the VM, but qemu is not... so I think you should investigate why qemu doesn;t allow you to. ** Changed in: maas Status: New => Incomplete ** Also affects: qemu (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/1831134 Title: Pods Cannot allocate memory, even with memory_over_commit_ratio set 10.0 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1831134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815123] Re: Hardware test stress-ng-cpu-long bind failed
** 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/1815123 Title: Hardware test stress-ng-cpu-long bind failed To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1815123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827923] [NEW] Constant sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received
Public bug reported: I see this in bind logs constantly. The machine is a machine with 88 procs, and about 132 GB ram. https://kb.isc.org/docs/aa-00508 sheds some light on the issues, which require re-compilation of bind9. Apr 07 12:01:54 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:01:59 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:02:01 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:02:02 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:02:03 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:02:03 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:02:04 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:02:05 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:02:05 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:02:06 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:02:06 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:02:07 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:02:07 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:02:08 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:02:09 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:02:09 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:02:23 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:03:10 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:03:12 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:03:20 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:03:27 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:03:33 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:03:57 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:03:58 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:03:59 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received Apr 07 12:04:00 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received lines 1-27 ** Affects: bind9 (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/1827923 Title: Constant sockmgr 0x7fa0b8b0a010: maximum number of FD events (64) received To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1827923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826916] Re: MAAS uninstalls itself on unattended upgrade
** 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/1826916 Title: MAAS uninstalls itself on unattended upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826916] Re: MAAS uninstalls itself on unattended upgrade
After having a look at all the provided logs, I see the following: 1. On dpkg.log I see that packages where installed and removed: - on 2019-04-19, non-maas related packages were configured (likely upgraded) - on 2019-04-24, maas related packages were marked for removal, and removed, e.g: 2019-04-24 06:02:09 startup packages remove 2019-04-24 06:02:09 status installed maas-region-controller:all 2.3.0-6434-gd354690-0ubuntu1~16.04.1 2019-04-24 06:02:11 remove maas-region-controller:all 2.3.0-6434-gd354690-0ubuntu1~16.04.1 2. On term.log, I see the counterparts of the above, were: - on 2019-04-19 packages were upgraded and MAAS wasn't removed - on 2019-04-24 I see that MAAS packages were removed, but nothing was upgraded nor updated. 3. On history.log, I confirm what I see the above, which is that: - on 2019-04-19 packages were ntfs-3g:amd64 was upgraded, and nothing removed automatically. - on 2019-04-24 MAAS related packages were removed. >From looking at the above, nothing really tells me what could be wrong and why MAAS packages were removed. However, the one thing to notice here is that MAAS 2.3.0-6434-gd354690 was the one removed. The interesting part, is the following: 4. From looking at install.log things turn interesting. This is because what's installed is MAAS 2.3.5-6511-gf466fdb-0ubuntu1. So, from looking at all of the above I can conclude that: a. There's not enough information why MAAS got removed. b. The installed MAAS version on the system was *2.3.0-6434-gd354690* while the version available in -updates was *2.3.5-6511-gf466fdb-0ubuntu1*. This to me means that unattended upgrades never really upgraded the MAAS version with the latest in -updates (e.g. it seems this MAAS could've been installed when 2.3.0 was in -updates). c. More interestingly, is that: - In previous unattended upgrades, no MAAS packages were removed, so why in the latest? - When MAAS was removed, no other packages were installed, which if there were to have been a conflict that would have caused MAAS to be removed, I would have expected a dependency would have conflicted and installed instead, which would have caused the upgrade? Unless unattended upgrades simply managed to remove while not upgrade a given dep? - When MAAS was manually installed, the installation happened just fine without really any issues, so if there would've been dependency issues, I would have expected the install to complain. So from the above, it would seem that someone or something marked the MAAS package for removal, and doesn't seem related to a dependency because we can see no dep issues, or new deps installed which would've caused this. That said, I'm not certain how unattended upgrades works internally so not sure why it never did upgrade the MAAS version in previous upgrades, and why it removed it in the latest. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826916 Title: MAAS uninstalls itself on unattended upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826916] Re: MAAS uninstalls itself on unattended upgrade
Also, the big questions would be: 1. Why was MAAS never previously been upgraded if 2.3.5 (from 2.3.0) has been in the archive forever. Or why this issue was never seen before if the same applies. 2. There are no reported broken packages, or newly installed packages when MAAS was removed, nor removed packages when MAAS was manually installed later on. So would it be possible the package was marked for removal by something else? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826916 Title: MAAS uninstalls itself on unattended upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826916] Re: MAAS uninstalls itself on unattended upgrade
Hi Chris, Please provide more context on this. We specifically need logs on what apt commands were executed, how, and the full process log of the terminal (e.g. we wanna see what apt has done). That said, we've never seen anything like this before. TO recover, you should just be able to stop all maas server, apply your db backup, restart maas services and should be good to go. ** 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/1826916 Title: MAAS uninstalls itself on unattended upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825099] Re: Unable to deploy Xenial on a s390x KVM
oh i see what's happening here, just to confirm: 1. You have a Bionic host 2. You are trying to deploy Xenial. 3. Xenial will use the rom available in bionic from comment #6 to PXE. 4. chreipl fails to configure. So based on 4 and comment #4, then this would be like an issue on chreipl which is external to MAAS. Also just to be clear, MAAS cannot support Xenial as a KVM host, but provided the bug in question gets fixed, there should be no reason why Xenial cannot be deployed on a Bionic+ KVM host. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825099 Title: Unable to deploy Xenial on a s390x KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825099] Re: Unable to deploy Xenial on a s390x KVM
Then if this is a bug in chreipl, then there shouldn't really be any reason why MAAS couldn't deploy in Xenial. That said, what I'm surprised about is s390x VM off MAAS when [1] was never backported to Xenial. [1]: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1790901 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825099 Title: Unable to deploy Xenial on a s390x KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713094] Re: [2.x] Make maas-proxy more configurable
** Changed in: maas Status: New => Fix Released ** No longer affects: maas (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713094 Title: [2.x] Make maas-proxy more configurable To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1713094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431150] Re: Accesing node listing page shows 0 nodes, 0 devices until refresh
** Changed in: maas (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431150 Title: Accesing node listing page shows 0 nodes, 0 devices until refresh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1431150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788641] Re: [SRU] MAAS 2.4.2
** Changed in: maas (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788641 Title: [SRU] MAAS 2.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1788641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733615] Re: [SRU] MAAS 2.3.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/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 1669591] Re: [SRU] MAAS 1.9.5
** Changed in: maas (Ubuntu) Status: Confirmed => 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/1669591 Title: [SRU] MAAS 1.9.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1669591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824434] Re: [0-day SRU] MAAS 2.6.0beta1
** Description changed: - Ubuntu Disco currently has MAAS 2.5.0. This is a Standing Feature Freeze - Exception request for MAAS 2.6.0 beta 1 release. + [Impact] + MAAS 2.6 is the new upstream release of MAAS. This new release introduces several performance improvements, tracking and various other features that have made the product more robust. + + Providing 2.6 in Disco will allow for users and customers to start + testing this new upstream release, and provide access to our customers + to test the latest functionality with ESXi. Dependencies & Upgrade == MAAS 2.6 has introduced the following features: - HTTP boot for amd64/arm64 - ESXi storage support - ESXi vCenter registration - DB performance improvements - UI performance improvements - TFTP performance improvements - Performance profiling and tracking. - - OpenBMC power driver - - Better boot process output. + - OpenBMC power driver + - Better boot process output. Upcoming releases are targeted to only include bug fixes. - Testing - == - - Testing performed: + [Test Case] + MAAS follows a test process that involves both automated and manual testing. This involves: - CI testing - Manual UI testing - Fresh install testing - Upgrade testing - Releases - === - Current beta release contains all features targeted for 2.6. Currently sits in beta due to continues UI work. + As part of this process we ensure MAAS is backwards compatible and + doesn't break after an upgrade. That said, while this release has not + introduced breaking changes, we have ensured that there are no + regressions in our test environment. + + [Regression Potential] + Minimal - This is because 2.6 switches from a full TFTP boot process for amd64 EFI and arm64, to a combined TFTP and HTTP boot process. The regression potential is minimal because we have already made this change for amd64 Legacy boot on a previous release of MAAS and have not come across any real issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824434 Title: [0-day SRU] MAAS 2.6.0beta1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1824434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824434] Re: [0-day SRU] MAAS 2.6.0beta1
** Changed in: maas (Ubuntu) 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/1824434 Title: [0-day SRU] MAAS 2.6.0beta1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1824434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824434] Re: [0-day SRU] MAAS 2.6.0beta1
** Description changed: Ubuntu Disco currently has MAAS 2.5.0. This is a Standing Feature Freeze Exception request for MAAS 2.6.0 beta 1 release. Dependencies & Upgrade == MAAS 2.6 has introduced the following features: - HTTP boot for amd64/arm64 - ESXi storage support - ESXi vCenter registration - DB performance improvements - UI performance improvements - TFTP performance improvements - Performance profiling and tracking. + - OpenBMC power driver + - Better boot process output. Upcoming releases are targeted to only include bug fixes. Testing == Testing performed: - CI testing - Manual UI testing - Fresh install testing - Upgrade testing Releases === Current beta release contains all features targeted for 2.6. Currently sits in beta due to continues UI work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824434 Title: [0-day SRU] MAAS 2.6.0beta1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1824434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824434] Re: [0-day SRU] MAAS 2.6.0beta1
** Summary changed: - [FFe] MAAS 2.6.0 a 2 + [0-day SRU] MAAS 2.6.0beta1 ** Description changed: Ubuntu Disco currently has MAAS 2.5.0. This is a Standing Feature Freeze Exception request for MAAS 2.6 release. Dependencies & Upgrade == MAAS 2.6 has introduced the following features: - - HTTP boot for amd64/arm64 - - ESXi storage support - - ESXi vCenter registration - - DB performance improvements - - UI performance improvements - - TFTP performance improvements - - Performance profiling and tracking. + - HTTP boot for amd64/arm64 + - ESXi storage support + - ESXi vCenter registration + - DB performance improvements + - UI performance improvements + - TFTP performance improvements + - Performance profiling and tracking. Upcoming releases are targeted to only include bug fixes. Testing == Testing performed: - - CI testing - - Manual UI testing - - Fresh install testing - - Upgrade testing + - CI testing + - Manual UI testing + - Fresh install testing + - Upgrade testing Releases === - We are targeting a beta or RC as a 0-day SRU. + Current beta release contains all features targeted for 2.6. Currently sits in beta due to continues UI work. ** Description changed: Ubuntu Disco currently has MAAS 2.5.0. This is a Standing Feature Freeze - Exception request for MAAS 2.6 release. + Exception request for MAAS 2.6.0 beta 1 release. Dependencies & Upgrade == MAAS 2.6 has introduced the following features: - HTTP boot for amd64/arm64 - ESXi storage support - ESXi vCenter registration - DB performance improvements - UI performance improvements - TFTP performance improvements - Performance profiling and tracking. Upcoming releases are targeted to only include bug fixes. Testing == Testing performed: - CI testing - Manual UI testing - Fresh install testing - Upgrade testing Releases === Current beta release contains all features targeted for 2.6. Currently sits in beta due to continues UI work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824434 Title: [0-day SRU] MAAS 2.6.0beta1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1824434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825099] Re: Unable to deploy Xenial on a s390x KVM
We have never supported s390x on Xenial. s390x was enabled for bionic+. ** 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/1825099 Title: Unable to deploy Xenial on a s390x KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824434] [NEW] [FFe] MAAS 2.6.0 a 2
Public bug reported: Ubuntu Disco currently has MAAS 2.5.0. This is a Standing Feature Freeze Exception request for MAAS 2.6 release. Dependencies & Upgrade == MAAS 2.6 has introduced the following features: - HTTP boot for amd64/arm64 - ESXi storage support - ESXi vCenter registration - DB performance improvements - UI performance improvements - TFTP performance improvements - Performance profiling and tracking. Upcoming releases are targeted to only include bug fixes. Testing == Testing performed: - CI testing - Manual UI testing - Fresh install testing - Upgrade testing Releases === We are targeting a beta or RC as a 0-day SRU. ** Affects: maas (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/1824434 Title: [FFe] MAAS 2.6.0 a 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1824434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 564853] Re: Spurious conffile prompts for /etc/default/grub
** 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/564853 Title: Spurious conffile prompts for /etc/default/grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/564853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607345] Re: Collect all logs needed to debug curtin/cloud-init for each deployment
** Changed in: maas Milestone: 2.5.x => 2.6.0 ** No longer affects: maas/2.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607345 Title: Collect all logs needed to debug curtin/cloud-init for each deployment To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1607345/+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
** 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/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 1813168] [NEW] [SRU] Please SRU py-macaroon-bakery 1.2.1
Public bug reported: [Impact] py-macaroon-bakery 1.2.1 has several changes and fixes that allow third party software to integrate with Candid for macaroon based authentication. Without this version, users are unable to integrate their software with Candid. On the other hand, MAAS is impacted and wont be able to use remote authentication without this version. [Test Case] Without this version: 1. Install MAAS 2. Install Candid 3. Configure MAAS w/ Candid 4. Attempt authentication -> it will fail. With this version: 1. Install MAAS 2. Install Candid 3. Configure MAAS w/ Candid 4. Attempt authentication -> it will suceed. [Regression potential] ** Affects: py-macaroon-bakery (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/1813168 Title: [SRU] Please SRU py-macaroon-bakery 1.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/py-macaroon-bakery/+bug/1813168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
** Changed in: maas Importance: Critical => Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607345] Re: Collect all logs needed to debug curtin/cloud-init for each deployment
** Changed in: maas Milestone: 2.5.0 => 2.5.x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607345 Title: Collect all logs needed to debug curtin/cloud-init for each deployment To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1607345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
Setting this back to incomplete for MAAS because there is not enough information to determine this is a MAAS Bug. That said, given that this work with any VM other than one with 2048 of RAM, the issue may appear to be the kernel or libvirt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
** Changed in: maas Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805920] Re: iPXE ignores vlan 0 traffic
FWIW, Cisco documentation here states that priority tagging is enabled by default: https://www.cisco.com/c/en/us/td/docs/switches/connectedgrid/cg-switch- sw-master/software/configuration/guide/vlan0/b_vlan_0.html "Default Settings VLAN 0 priority tagging is enabled by default." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805920 Title: iPXE ignores vlan 0 traffic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1805920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807820] Re: Precise i386 deployment failed with root-tgz file not found error
So MAAS is correctly trying to download the root-tgz but the files avialable do not include a root-tgz. I also looked in the code and it seems that root-image.gz should be converted into root-tgz: #: Root Image (gets converted to root-image root-tgz, on the rack) ROOT_IMAGE = 'root-image.gz' But: root@maas-bionic:/var/lib/maas/boot-resources/current/ubuntu/i386/generic# ls -l /var/lib/maas/boot-resources/current/ubuntu/i386/generic/precise/daily/ total 278696 -rw-r--r-- 3 maas maas 18318877 Dec 12 23:44 boot-initrd -rw-r--r-- 3 maas maas 4910272 Dec 12 23:44 boot-kernel -rw-r--r-- 7 maas maas 262145114 Dec 12 23:44 root-image.gz ** Changed in: maas (Ubuntu) Status: New => Triaged ** Changed in: maas (Ubuntu) Importance: Undecided => High ** Also affects: maas Importance: Undecided Status: New ** No longer affects: maas (Ubuntu) ** Changed in: maas Milestone: None => 2.5.1 ** Also affects: maas/2.4 Importance: Undecided Status: New ** Changed in: maas Importance: Undecided => High ** Changed in: maas Status: New => Triaged ** Changed in: maas Importance: High => Medium ** Changed in: maas/2.4 Importance: Undecided => Medium ** Changed in: maas/2.4 Status: New => Triaged ** Changed in: maas Assignee: (unassigned) => Lee Trager (ltrager) ** Changed in: maas/2.4 Milestone: None => 2.4.x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807820 Title: Precise i386 deployment failed with root-tgz file not found error To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1807820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805920] Re: iPXE ignores vlan 0 traffic
Just to clarify the above statements as it has been source of confusion. MAAS 2.3+ (which is the latest available in Xenial), no longer uses nor supports iSCSI. While the option to fallback to old behavior does exist, it is not enabled by default, its obscured and, given that is not supported, it is to be used at users risk. That said, I'm not sure whether this change should be backported all the way to Xenial. It would seem to be that it should be backported to Bionic only. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805920 Title: iPXE ignores vlan 0 traffic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1805920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805920] Re: iPXE ignores vlan 0 traffic
FWIW, I patched ipxe with the CentOS patch as a test, which Vern was going to test: https://launchpadlibrarian.net/400355423/ipxe_1.0.0+git-20180124.fbe8c52d-0ubuntu2_1.0.0+git-20180124.fbe8c52d-0ubuntu2.2~18.04.1.diff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805920 Title: iPXE ignores vlan 0 traffic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1805920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805920] Re: iPXE ignores vlan 0 traffic
Seems other users in other distros experiencing the same, and a kernel update fixes the issues? https://serverfault.com/questions/497391/ ** Also affects: linux (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/1805920 Title: iPXE ignores vlan 0 traffic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1805920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805920] Re: iPXE ignores vlan 0 traffic
Hi Vern, Could you confirm something to us. WHen you say that the customer deployed centos 7 and were able to see the issue there, did you mean that they saw the issue in the packets themselves? In other words, CentOS7 deployed successfully but the packets still had the VLAN tag? The reason I ask is because centos7 ipxe includes a patch that strips the vlan tag. So I'm wondering if that allows VMs on a CentOS 7 host to PXE boot without failing? Anyhow, I've made a version of ipxe for Ubuntu with the centos patch in ppa:andreserl/maas. I've not tested it, but if you could take a look and test if that would fix the issue, then we could push that to Ubuntu. Anyhow, we need to talk to the kernel folks to figure this one out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805920 Title: iPXE ignores vlan 0 traffic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1805920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805920] Re: iPXE ignores vlan 0 traffic
I did some digging, and it seems that: 1. Upstream has not accepted a patch from redhat to strip the priority tags [1] 2. RHEL (and consequently centos) are patching ipxe directly [2], [3]. Based on this, I think this patch could potentially be ported into ipxe in Ubuntu, however, I think there should be some investigation into the network as to why packets are not stripped on egress. [1]: http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html [2]: https://git.centos.org/blob/rpms!ipxe.git/c7/SPECS!ipxe.spec [3]: https://git.centos.org/blob/rpms!ipxe.git/c7/SOURCES!0009-Strip-802.1Q-VLAN-0-priority-tags.patch ** Also affects: ipxe (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/1805920 Title: iPXE ignores vlan 0 traffic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1805920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801899] Re: cannot install with python3.7 as default async is a reserved keyword
** 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/1801899 Title: cannot install with python3.7 as default async is a reserved keyword To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1801899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800153] Re: [2.5] Failed to deploy ppc64el when partition table is GPT
@Ryan, with curtin verbose: https://pastebin.ubuntu.com/p/nzvHvStyKb/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800153 Title: [2.5] Failed to deploy ppc64el when partition table is GPT To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1800153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800153] Re: [2.5] Failed to deploy ppc64el when partition table is GPT
>From the MAAS perspective, I can confirm that MAAS is setting to GPT, and it is failing. When setting it to MBR, it succeeds. That said... the other question is whether curtin needs to support using GPT instead? ** Changed in: maas 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/1800153 Title: [2.5] Failed to deploy ppc64el when partition table is GPT To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1800153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800153] Re: [2.5] Failed to deploy ppc64el when partition table is GPT
The difference in behavior is between 2.5.0-beta3 and 418bd67af816b4a99747eb7a1ca8cb966b58ed84 The only storage related change is a UI change: https://git.launchpad.net/maas/commit/?id=32e3d12485456e07fbf5deb82ba6ab455eeefcb5 , which wouldn't seem related. ** Changed in: maas Assignee: (unassigned) => Lee Trager (ltrager) ** Changed in: maas Importance: Undecided => Critical ** Changed in: maas Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800153 Title: [2.5] Failed to deploy ppc64el when partition table is GPT To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1800153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800153] Re: [2.5] Failed to deploy ppc64el when partition table is GPT
After further investigation, it seems that commissioning is setting different partition tables: MAAS 2.5.0beta3 sets partition table to MBR MAAS 2.5.0beta4 sets partition table to GPT -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800153 Title: [2.5] Failed to deploy ppc64el when partition table is GPT To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1800153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800153] Re: [2.5] Failed to deploy ppc64el
I deployed using MAAS 2.5.0beta3, and the result is successful. This is the config from get-curtin-config: http://paste.ubuntu.com/p/bg4JZ4bVb7/ It seems that 2.5.0beta3 has: - id: sda model: IPR-0 6DC90500 name: sda ptable: msdos serial: IBM_IPR-0_6DC90580 type: disk MAAS from master automatically sets the partition table to: - id: sda model: IPR-0 6DC90500 name: sda ptable: gpt serial: IBM_IPR-0_6DC90580 type: disk wipe: superblock It seems to me that the fact that latest MAAS is changing that to gpt is what's breaking the deployments. ** Summary changed: - [2.5] Failed to deploy ppc64el + [2.5] Failed to deploy ppc64el when partition table is GPT -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800153 Title: [2.5] Failed to deploy ppc64el when partition table is GPT To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1800153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800153] Re: [2.5] Failed to deploy ppc64el
The failed installation log for the above config: https://pastebin.ubuntu.com/p/FSMCXRMzXt/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800153 Title: [2.5] Failed to deploy ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1800153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800153] Re: [2.5] Failed to deploy ppc64el
** Attachment added: "storage-ppc64.png" https://bugs.launchpad.net/maas/+bug/1800153/+attachment/5206915/+files/storage-ppc64.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800153 Title: [2.5] Failed to deploy ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1800153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800153] Re: [2.5] Failed to deploy ppc64el
The curtin configuration can be found here: http://paste.ubuntu.com/p/89DwnJGzc2/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800153 Title: [2.5] Failed to deploy ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1800153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790901] Re: How to use s390x pxelinux style network booting from qemu 3.0 in bionic
I've tested this with MAAS in a remote s390x system, and confirm it works out of the box. So I'm +1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790901 Title: How to use s390x pxelinux style network booting from qemu 3.0 in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI
** Changed in: maas Milestone: 2.5.x => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789319 Title: Unable to load shimx64.efi using iPXE over UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1789319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
** Changed in: maas Milestone: 2.5.0rc1 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664248] Re: Can't disable a backports pocket when deploying Ubuntu 14.04
** 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/1664248 Title: Can't disable a backports pocket when deploying Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1664248/+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 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/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 1787630] Re: [FFe] Include HTTP support in pre-build GRUB module
** Description changed:
+ {Description]
+ Grub supports booting files over the network via both FTP/HTTP. However, the
Ubuntu package is not built with the grub HTTP modules. Enabling this would
allow grub to obtain files over HTTP (such as initrd/kernel).
+
+ [Rationale]
+ Enabling HTTP support for Grub would allow MAAS to use such functionality to
boot files over the network with HTTP. This allows for improvement performance
(vs using ftp) and for better security.
+
+ [Original bug report]
+
GRUB has builtin support for HTTP via http.mod. This module is not being
included in the prebuild grubnetx64.efi. All that should be required is
adding the http module. I also suggest building grubnetx64.efi using
GRUB modules to include lvm and RAID support this will allow
grubnetx64.efi to local boot in all situations.
--- build-efi-images 2018-08-17 10:50:35.124311043 -0700
+++ build-efi-images.new 2018-08-17 10:50:59.270661126 -0700
@@ -148,8 +148,9 @@
raid5rec
raid6rec
"
-NET_MODULES="$CD_MODULES
+NET_MODULES="$GRUB_MODULES
tftp
+ http
"
"$grub_mkimage" -O "$platform" -o "$outdir/gcd$efi_name.efi" \
** Description changed:
{Description]
Grub supports booting files over the network via both FTP/HTTP. However, the
Ubuntu package is not built with the grub HTTP modules. Enabling this would
allow grub to obtain files over HTTP (such as initrd/kernel).
[Rationale]
Enabling HTTP support for Grub would allow MAAS to use such functionality to
boot files over the network with HTTP. This allows for improvement performance
(vs using ftp) and for better security.
+
+ MAAS would use this to download kernel and initrd over HTTP instead of
+ FTP at first for performance improvements.
[Original bug report]
GRUB has builtin support for HTTP via http.mod. This module is not being
included in the prebuild grubnetx64.efi. All that should be required is
adding the http module. I also suggest building grubnetx64.efi using
GRUB modules to include lvm and RAID support this will allow
grubnetx64.efi to local boot in all situations.
--- build-efi-images 2018-08-17 10:50:35.124311043 -0700
+++ build-efi-images.new 2018-08-17 10:50:59.270661126 -0700
@@ -148,8 +148,9 @@
raid5rec
raid6rec
"
-NET_MODULES="$CD_MODULES
+NET_MODULES="$GRUB_MODULES
tftp
+ http
"
"$grub_mkimage" -O "$platform" -o "$outdir/gcd$efi_name.efi" \
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787630
Title:
[FFe] Include HTTP support in pre-build GRUB module
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1787630/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787630] Re: [FFe] Include HTTP support in pre-build GRUB module
** Summary changed: - Include HTTP support in pre-build GRUB module + [FFe] Include HTTP support in pre-build GRUB module -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787630 Title: [FFe] Include HTTP support in pre-build GRUB module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1787630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796164] Re: After interface/IP changes, bind9 can fail to respond to queries on the new interface
** Changed in: maas Milestone: 2.5.0rc1 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796164 Title: After interface/IP changes, bind9 can fail to respond to queries on the new interface To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1796164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI
** Changed in: maas Milestone: 2.5.0rc1 => 2.5.x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789319 Title: Unable to load shimx64.efi using iPXE over UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1789319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796164] Re: After interface/IP changes, bind9 can fail to respond to queries on the new interface
Marking as won't fix for MAAS as this issue really sets outside of MAAS. ** Changed in: maas Status: Incomplete => 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/1796164 Title: After interface/IP changes, bind9 can fail to respond to queries on the new interface To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1796164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796937] [NEW] [FFe] MAAS 2.5.0beta2
Public bug reported: Ubuntu Cosmic currently has MAAS 2.5 beta 1. This is a Feature Freeze Exception request for MAAS 2.5 beta 2 release for Ubuntu Cosmic. Dependencies & Upgrade == MAAS 2.5 has introduced the following features: - CentOS/RHEL networking support - ESXi support - KVM Pod networking support - KVM Pod storage pool - ppc64el/arm64/s390x KVM pod support - Improved LDAP support & RBAC for resource pools - Rack Controller - proxy all communication - Performance/usability improvements - BMC enlistment - Partition tags The beta 2 release includes several internal bug fixes that stabilize the features above and introduces various UI updates that support the features above. Testing == Testing performed: - CI testing - Manual UI testing - Fresh install testing - Upgrade testing For more information on the QA process MAAS follows, please see https://wiki.ubuntu.com/MAASUpdates . We follow the same strict QA processes for new releases, as with SRU's. ** Affects: maas (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/1796937 Title: [FFe] MAAS 2.5.0beta2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1796937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796164] Re: After interface/IP changes, bind9 can fail to respond to queries on the new interface
** Changed in: maas 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/1796164 Title: After interface/IP changes, bind9 can fail to respond to queries on the new interface To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1796164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792905] Re: [2.5] iSCSI systemd services fails and blocks for 1 min 30 seconds
** 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/1792905 Title: [2.5] iSCSI systemd services fails and blocks for 1 min 30 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1792905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795726] Re: package maas-region-controller 2.4.2-7034-g2f5deb8b8-0ubuntu1 failed to install/upgrade: installed maas-region-controller package post-installation script subprocess returned error e
Looking at the logs it seems that postgresql is not running: django.db.utils.OperationalError: could not connect to server: Connection refused Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432? Postgresq needs to be running during the installation. ** 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/1795726 Title: package maas-region-controller 2.4.2-7034-g2f5deb8b8-0ubuntu1 failed to install/upgrade: installed maas-region-controller package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1795726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI
** Changed in: maas Milestone: 2.5.0beta2 => 2.5.0rc1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789319 Title: Unable to load shimx64.efi using iPXE over UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1789319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790901] Re: How to use s390x pxelinux style network booting from qemu 3.0 in bionic
>From the MAAS perspective, we have tested this and confirm that provides what we need. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790901 Title: How to use s390x pxelinux style network booting from qemu 3.0 in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1790901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772010] Re: [SRU] MAAS 2.3.5
** 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/1772010 Title: [SRU] MAAS 2.3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1772010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772010] Re: [SRU] MAAS 2.3.5
tested from -proposed this package both on CI and manually and +1. Marked 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/1772010 Title: [SRU] MAAS 2.3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1772010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772010] Re: [SRU] MAAS 2.3.5
maas-integration.TestMAASIntegration.test_create_admin ... ok maas-integration.TestMAASIntegration.test_restart_dbus_avahi ... SKIP: Avahi/DBUS are not used anymore maas-integration.TestMAASIntegration.test_update_maas_url ... ok maas-integration.TestMAASIntegration.test_update_maas_url_rack ... ok maas-integration.TestMAASIntegration.test_check_initial_services_systemctl ... ok maas-integration.TestMAASIntegration.test_check_rpc_info ... ok maas-integration.TestMAASIntegration.test_update_preseed_arm ... SKIP: Don't test ARM nodes maas-integration.TestMAASIntegration.test_login_api ... ok maas-integration.TestMAASIntegration.test_maas_logged_in ... ok maas-integration.TestMAASIntegration.test_set_main_archive ... ok maas-integration.TestMAASIntegration.test_main_archive_in_enlist_userdata_package_mirrors_config ... SKIP: Cloud-init "package_mirror" config is used in MAAS 2.0 and earlier maas-integration.TestMAASIntegration.test_main_archive_in_enlist_userdata_apt_config ... ok maas-integration.TestMAASIntegration.test_set_http_proxy ... ok maas-integration.TestMAASIntegration.test_add_ssh_key ... ok maas-integration.TestMAASIntegration.test_region_rack_connected ... ok maas-integration.TestMAASIntegration.test_stop_image_import ... ok maas-integration.TestMAASIntegration.test_set_custom_boot_source ... SKIP: Not testing custom images maas-integration.TestMAASIntegration.test_add_boot_source_selection_xenial ... SKIP: Not adding Xenial images as we are already running in Xenial maas-integration.TestMAASIntegration.test_add_boot_source_selection_ppc64el ... SKIP: Not testing PPC systems maas-integration.TestMAASIntegration.test_add_boot_source_selection_arm64 ... SKIP: Not testing arm64 systems maas-integration.TestMAASIntegration.test_add_boot_source_selection_centos ... ok maas-integration.TestMAASIntegration.test_start_image_import ... ok maas-integration.TestMAASIntegration.test_create_dynamic_range ... ok maas-integration.TestMAASIntegration.test_reserve_bmc_range ... ok maas-integration.TestMAASIntegration.test_create_slave_device_and_link_subnet ... ok maas-integration.TestMAASIntegration.test_slave_device_interface_linked ... ok maas-integration.TestMAASIntegration.test_set_up_dhcp_vlan ... ok maas-integration.TestMAASIntegration.test_check_dhcp_service_systemctl ... ok maas-integration.TestMAASIntegration.test_update_dns_config_systemctl ... ok maas-integration.TestMAASIntegration.test_add_new_zones ... ok maas-integration.TestMAASIntegration.test_list_zones ... ok maas-integration.TestMAASIntegration.test_delete_zone ... ok maas-integration.TestMAASIntegration.test_add_new_resource_pools ... SKIP: Resource pools feature only available after 2.5 maas-integration.TestMAASIntegration.test_list_resource_pools ... SKIP: Resource pools feature only available after 2.5 maas-integration.TestMAASIntegration.test_delete_resource_pools ... SKIP: Resource pools feature only available after 2.5 maas-integration.TestMAASIntegration.test_add_new_spaces ... ok maas-integration.TestMAASIntegration.test_create_subnet ... ok maas-integration.TestMAASIntegration.test_list_spaces ... ok maas-integration.TestMAASIntegration.test_list_subnets ... ok maas-integration.TestMAASIntegration.test_delete_subnet ... ok maas-integration.TestMAASIntegration.test_delete_space ... ok maas-integration.TestMAASIntegration.test_add_new_fabrics ... ok maas-integration.TestMAASIntegration.test_add_vlan_to_fabric ... ok maas-integration.TestMAASIntegration.test_list_fabrics ... ok maas-integration.TestMAASIntegration.test_list_vlans ... ok maas-integration.TestMAASIntegration.test_delete_vlan ... ok maas-integration.TestMAASIntegration.test_delete_fabric ... ok maas-integration.TestMAASIntegration.test_tag_uefi ... ok maas-integration.TestMAASIntegration.test_region_imported_images ... ok maas-integration.TestMAASIntegration.test_rack_imported_images ... ok maas-integration.TestMAASIntegration.test_add_windows_boot_resource ... SKIP: Not testing Windows maas-integration.TestMAASIntegration.test_add_rhel_boot_resource ... SKIP: Not testing RHEL maas-integration.TestMAASIntegration.test_set_xenial_as_default_distro_series ... SKIP: Not setting Xenial as default_distro_series as we only need it in 2.4 maas-integration.TestMAASIntegration.test_poweron_nodes_to_enlist ... ok maas-integration.TestMAASIntegration.test_check_machines_new ... ok maas-integration.TestMAASIntegration.test_check_enlisted_machines_commissioned ... SKIP: Commissioning during enlistment only supported in MAAS 2.5+ maas-integration.TestMAASIntegration.test_assign_machines_to_test_zone ... ok maas-integration.TestMAASIntegration.test_assign_machines_to_test_resource_pool ... SKIP: Resource pools feature only available after 2.5 maas-integration.TestMAASIntegration.test_set_machines_ipmi_config ... ok maas-integration.TestMAASIntegration.test_start_commissioning_machines ... ok maas-integration.TestMAASIntegration.test_check_nodes_ready ... ok maas-inte
[Bug 1772010] Re: [SRU] MAAS 2.3.5
After this operation, 228 MB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 authbind amd64 2.1.1+nmu1 [17.6 kB] Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libavahi-common-data amd64 0.6.32~rc+dfsg-1ubuntu2.2 [21.5 kB] Get:3 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libavahi-common3 amd64 0.6.32~rc+dfsg-1ubuntu2.2 [21.6 kB] Get:4 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libavahi-client3 amd64 0.6.32~rc+dfsg-1ubuntu2.2 [25.2 kB] Get:5 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libavahi-core7 amd64 0.6.32~rc+dfsg-1ubuntu2.2 [81.5 kB] Get:6 http://archive.ubuntu.com/ubuntu xenial/main amd64 libdaemon0 amd64 0.14-6 [16.6 kB] Get:7 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 avahi-daemon amd64 0.6.32~rc+dfsg-1ubuntu2.2 [59.5 kB] Get:8 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 avahi-utils amd64 0.6.32~rc+dfsg-1ubuntu2.2 [24.3 kB] Get:9 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 bind9utils amd64 1:9.10.3.dfsg.P4-8ubuntu1.11 [201 kB] Get:10 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 freeipmi-common amd64 1.4.11-1.1ubuntu4~0.16.04 [174 kB] Get:11 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libfreeipmi16 amd64 1.4.11-1.1ubuntu4~0.16.04 [827 kB] Get:12 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libipmiconsole2 amd64 1.4.11-1.1ubuntu4~0.16.04 [85.1 kB] Get:13 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libipmidetect0 amd64 1.4.11-1.1ubuntu4~0.16.04 [25.3 kB] Get:14 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 freeipmi-tools amd64 1.4.11-1.1ubuntu4~0.16.04 [623 kB] Get:15 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-httplib2 all 0.9.1+dfsg-1 [28.2 kB] Get:16 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-netifaces amd64 0.10.4-0.1build2 [12.9 kB] Get:17 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-oauth all 1.0.1-5 [8,238 B] Get:18 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-tempita all 0.5.2-1build1 [13.7 kB] Get:19 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 python3-maas-client all 2.3.5-6511-gf466fdb-0ubuntu1 [31.1 kB] Get:20 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 maas-cli all 2.3.5-6511-gf466fdb-0ubuntu1 [2,568 B] Get:21 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libdebian-installer4 amd64 0.102ubuntu1.1 [21.8 kB] Get:22 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 archdetect-deb amd64 1.117ubuntu2.3 [6,020 B] Get:23 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-attr all 15.2.0-1 [11.3 kB] Get:24 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-bson amd64 3.2-1build1 [24.2 kB] Get:25 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-zope.interface amd64 4.1.3-1build1 [81.2 kB] Get:26 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-openssl all 0.15.1-2build1 [84.1 kB] Get:27 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-pyasn1-modules all 0.0.7-0.1 [20.6 kB] Get:28 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-service-identity all 16.0.0-2 [9,388 B] Get:29 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 python3-twisted all 16.0.0-1ubuntu0.2 [1,104 kB] Get:30 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-crochet all 1.4.0-0ubuntu2 [20.9 kB] Get:31 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 curtin-common all 18.1-17-gae48e86f-0ubuntu1~16.04.1 [17.7 kB] Get:32 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 python3-curtin all 18.1-17-gae48e86f-0ubuntu1~16.04.1 [111 kB] Get:33 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-distro-info all 0.14build1 [8,134 B] Get:34 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-dnspython all 1.12.0-0ubuntu3 [84.4 kB] Get:35 http://archive.ubuntu.com/ubuntu xenial/main amd64 formencode-i18n all 1.3.0-0ubuntu5 [3,382 B] Get:36 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-formencode all 1.3.0-0ubuntu5 [69.2 kB] Get:37 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-jsonschema all 2.5.1-4 [30.3 kB] Get:38 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-lxml amd64 3.5.0-1build1 [811 kB] Get:39 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 python3-crypto amd64 2.6.1-6ubuntu0.16.04.3 [246 kB] Get:40 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-ecdsa all 0.13-2 [34.1 kB] Get:41 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 python3-paramiko all 1.16.0-1ubuntu0.1 [109 kB] Get:42 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-ptyprocess all 0.5-1 [13.0 kB] Get:43 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-pexpect all 4.0.1-1 [41.2 kB] Get:44 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 python3-pyparsing all 2.0.3+dfsg1-1ubuntu0.1 [35.5
[Bug 1772010] Re: [SRU] MAAS 2.3.4
1. check what use_peer_proxy ubuntu@autopkgtest:~$ maas admin maas get-config name=use_peer_proxy Success. Machine-readable output follows: false 2. set maas_proxy_port ubuntu@autopkgtest:~$ maas admin maas set-config name=maas_proxy_port value=8081 Success. Machine-readable output follows: OK 3. check it is set correctly ubuntu@autopkgtest:~$ maas admin maas get-config name=maas_proxy_port Success. Machine-readable output follows: 8081 4. Went to the UI to "Use peer proxy". 5. Check the new value ubuntu@autopkgtest:~$ maas admin maas get-config name=use_peer_proxy Success. Machine-readable output follows: true 6. Ensure maas_proxy_port is unchanged ubuntu@autopkgtest:~$ maas admin maas get-config name=maas_proxy_port Success. Machine-readable output follows: 8081 So I can confirm LP: #1787381 has now been resolved with what's in -proposed. ** Summary changed: - [SRU] MAAS 2.3.4 + [SRU] MAAS 2.3.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772010 Title: [SRU] MAAS 2.3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1772010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI
** 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/1789319 Title: Unable to load shimx64.efi using iPXE over UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1789319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772010] Re: [SRU] MAAS 2.3.4
** Description changed: [Impact] This is a new upstream release that addresses various issues present in 2.3.0. MAAS 2.3.4 fixes various issues that were present on MAAS 2.3.0. https://launchpad.net/maas/+milestone/2.3.1 https://launchpad.net/maas/+milestone/2.3.2 https://launchpad.net/maas/+milestone/2.3.3 https://launchpad.net/maas/+milestone/2.3.4 https://launchpad.net/maas/+milestone/2.3.5 This point release includes fixes/enhancements for hardware enablement and to address customer related issues that are worth noting: Enhancements/Hardware Enablement * Bug 1750622 "[feature] Add ability to select the BIOS boot method for IPMI - To address issues with newer firmware" This adds a new option to power manage machines, that are oriented at addressing changes in upstream hardware firmware's (that have broken compatibility with older versions). Causes no behavior changes for MAAS as it continues to do the same. Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, and this change only takes effect by a user driven action. Bug 1758760 "[enhancement] Support Lenovo’s new password policy (Lenovo SR550)" Fixes the password generation process for IPMI discovery to consider new password policies that are being added to newer hardware or firmware versions. Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by testing the old password policy. If it doesn't work it will use the new password policy. LP: #1779712 [enhancement] maas-proxy port should be configurable Adds the ability to change the proxy port for the proxy that MAAS uses. If users upgrade, the configuration rendered will continue to use the default port. This will only take effect for users who change the port. Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by using the default port. This change only takes effect by a user driven action. LP: #1778710 [2.3] Allow telling MAAS image import to not use proxy. Allow's users to tell MAAS to import images without using the configured proxy, in cases that MAAS is directly connected to the internet but machines are not. Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, this would only take effect by a user driven action. Bug fixes that change existing behaviour Bug 1739761 [adds support to deploy Precise on MAAS 2.3] Re-adds the ability to deploy precise, which was dropped on MAAS 2.3 initially. Bug 1730751 "LACP rate fast by default" Changes the default LACP rate to fast, which addresses issues in that our IS department was facing. Note that this only changes how often the control packets are set and it is recommended/preferred to be set to fast, and the use of slow is discouraged. Bug 1767137 "Default install is now importing bionic by default instead of xenial" This is an issue that MAAS automatically started selection Bionic for commissioning instead of Xenial as it was intended. This ensure that Xenial is selected by default. Note that in case of upgrades, if Bionic is already selected, MAAS won't change this to Xenial. It will *only* affect to new installs. + Other + + LP: #1787381 - WebUI overrides proxy values that have not changed + + The WebUI was overriding values that had not been changed in the WebUI. + This bugs addresses this issue to ensure it only does it if something + changes. + + [Test Case] MAAS Testing 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. + LP: #1787381 Testing + + This fix requires manual testing. To test: + + 1. Install MAAS + 2. Update maas_proxy_port over the API (e.g. maas maas set-config name=maas_proxy_port value=8080 + 3. Go to the Web UI and change the proxy method from internal to 'Peer Proxy' + 4. Ensure that maas_proxy_port has not changed: (w.g. maas maas get-config name=maas_proxy_port. + Solutions QA
[Bug 1792575] Re: Boot failure with efi shims from 20180913.0
Marking this as invalid for MAAS> Once this issue is fixed and SRU'd to Xenial, it will be rolled out automatically. In the meantime, the bootloaders have been reverted from the archive, and from the MAAS image repositories. ** Changed in: maas Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792575 Title: Boot failure with efi shims from 20180913.0 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1792575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792575] Re: Boot failure with efi shims from 20180913.0
Just to provide some more context 1. Machines were deployed with Xenial and bootloders from image streams version 20180906, which was using an older shim (versions as per "a" below) 2. The shim has been updated in the ubuntu archive for cosmic and bionic, but for xenial they still in -proposed (new version as per "b" below). 3. MAAS automatically updated to newer bootloaders in 20180913 streams, using the latest from bionic-proposed (see "b" below for details) 4. The machine was rebooted, upon reboot, the new boot fails were unable to chain into the installed systems files. The installed system (in Xenial) had older version of the shim, where as MAAS, had a newer version of the shim (from Bionic). Looking at the MAAS streams that provides the bootloaders [1] I can see that: a) 20180906.0 is using bionic's grub2-signed (1.93.5+2.02-2ubuntu8.4) and shim-signed (1.34.9.2+13-0ubuntu2) b) 20180913.0 is using bionic's grub2-signed (1.93.5+2.02-2ubuntu8.4) but it is using a different shim-signed (1.37~18.04.1+15+1533136590.3beb971-0ubuntu1) [1]: https://images.maas.io/ephemeral-v3/daily/streams/v1/com.ubuntu.maas:daily:1:bootloader-download.json That said, I would have thought that: 1. using a newer shim/grub2-signed, it should be able to chainload into an older shim/grub2-signed? I'm adding a task for the 'shim' package to get this question answered and find out whether a shim update should be able to chain into an older shim version (or viceversa). ** Also affects: shim (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/1792575 Title: Boot failure with efi shims from 20180913.0 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1792575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792389] [NEW] [FFe] Standing Feature Freeze Exception for MAAS 2.5
Public bug reported: Ubuntu Cosmic currently has MAAS 2.5 alpha 2. This is a Standing Feature Freeze Exception request for MAAS 2.5 upcoming beta/rc/final releases for Ubuntu Cosmic. Dependencies & Upgrade == MAAS 2.5 has introduced the following features: - CentOS/RHEL networking support - ESXi support - KVM Pod networking support - KVM Pod storage pool - ppc64el/arm64/s390x KVM pod support - Improved LDAP support & RBAC for resource pools - Rack Controller - proxy all communication - Performance/usability improvements - BMC enlistment - Partition tags Upcoming releases are targeted to bugfix, improve and complete the features above. Testing == Testing performed: - CI testing - Manual UI testing - Fresh install testing - Upgrade testing For more information on the QA process MAAS follows, please see https://wiki.ubuntu.com/MAASUpdates . We follow the same strict QA processes for new releases, as with SRU's. Releases === Upcoming MAAS releases are targetted on a 2 week cadence: - MAAS 2.5.0~b1 - MAAS 2.5.0~b2 - MAAS 2.5.0~rc1 - MAAS 2.5.0~rc2 - MAAS 2.5.0 ** Affects: maas (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/1792389 Title: [FFe] Standing Feature Freeze Exception for MAAS 2.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1792389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319644] Re: maas with no arguments gives bad advice
** This is an automated message ** We believe this is no longer an issue on the latest MAAS releases. As such, we are marking this bug report as invalid. If you believe this is still an issue, please re-open the bug report and provide any relevant information. Thanks. ** Changed in: maas Status: Triaged => Invalid ** Changed in: maas (Ubuntu) Status: Confirmed => Invalid ** Changed in: maas (Ubuntu Trusty) Status: Confirmed => 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/1319644 Title: maas with no arguments gives bad advice To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1319644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336816] Re: [doc] MAAS needs Moonshot Documentation
** Summary changed: - MAAS needs Moonshot Documentation + [doc] MAAS needs Moonshot Documentation ** No longer affects: maas (Ubuntu) ** Changed in: maas Importance: High => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336816 Title: [doc] MAAS needs Moonshot Documentation To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1336816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772010] Re: [SRU] MAAS 2.3.4
** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772010 Title: [SRU] MAAS 2.3.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1772010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791110] Re: package maas-region-controller 2.3.0-6434-gd354690-0ubuntu1~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hi There, Seems that your DB is not running: File "/usr/lib/python3/dist-packages/django/db/backends/postgresql_psycopg2/base.py", line 176, in get_new_connection connection = Database.connect(**conn_params) File "/usr/lib/python3/dist-packages/psycopg2/__init__.py", line 164, in connect conn = _connect(dsn, connection_factory=connection_factory, async=async) django.db.utils.OperationalError: could not connect to server: Connection refused Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432? I would ensure that postgresql is running and then sudo apt-get -f install. THat shoudl esolve your issue. ** 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/1791110 Title: package maas-region-controller 2.3.0-6434-gd354690-0ubuntu1~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1791110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1790901] Re: Backporting s390x pxelinux style network booting from qemu 3.0 to bionic
What about getting qemu 3.0 into cosmic? On Thu, Sep 6, 2018 at 2:41 AM Christian Ehrhardt < 1790...@bugs.launchpad.net> wrote: > Hi, > this would not only require a backport that seems hard (plenty of other > cleanups/fixes to pc-bios/s390-ccw) but doable eventually with some extra > work. > That part of it would be SRUable if we want to spend all the effort as it > only fixes/improves the s390x netboot capabilities. > > The initial netboot capabilities were only added in the 2.12 version > (Cosmic) so we'd also need all the packaging changes. > That includes bringing back SLOF headers of the right version. > > And with SLOF we have the biggest issue, for this to actually work we'd > have to also bump SLOF quite a lot. Now that is a problem for many > potential issues between the binary SLOF and ppc-qemu working against it > vs the in-qemu-source SLOF that s390x needs to build the pxelinux. > > Together the effort is high and the regression risk even higher, if I'd > be SRU team I'd nack it so we might waste all the effort. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1790901 > > Title: > Backporting s390x pxelinux style network booting from qemu 3.0 to > bionic > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1790901/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=qemu; component=main; > status=New; importance=Undecided; assignee=None; > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: andreserl paelzer > Launchpad-Bug-Reporter: Andres Rodriguez (andreserl) > Launchpad-Bug-Modifier: Christian Ehrhardt (paelzer) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: andreserl > -- 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/1790901 Title: Backporting s390x pxelinux style network booting from qemu 3.0 to bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1790901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791006] Re: deploying Ubuntu 18.04 with MAAS 1.9.5 fails during the final boot
I think the issue is quite simple actually. Bionic uses net plan, everything before that uses e/n/i. In trusty, curtin wrote the network configuration. In latest versions, Curtin now doesn’t do the network configuration, and actually tells cloud-unit to do it by passing the configuration. So what I think is happening is that curtin writes e/n/i and cloud-unit actually never writes net plan. So I would say that bionic deployment is not supported on 1.9 due to curtin. ** Changed in: maas Status: New => Incomplete ** Also affects: curtin (Ubuntu) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu) Status: New => Incomplete ** Changed in: curtin (Ubuntu) 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/1791006 Title: deploying Ubuntu 18.04 with MAAS 1.9.5 fails during the final boot To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1791006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1402042] Re: console= parameters need to be added before -- on kernel cmdline
** Changed in: maas Milestone: next => None ** Changed in: maas/trunk Milestone: next => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1402042 Title: console= parameters need to be added before -- on kernel cmdline To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1402042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599223] Re: [2.0] confusing reverse DNS lookups because MAAS creates multiple PTR records
** Changed in: maas Milestone: next => None ** Changed in: maas/2.0 Milestone: 2.0.0 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599223 Title: [2.0] confusing reverse DNS lookups because MAAS creates multiple PTR records To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1599223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433697] Re: maas depends on syslinux-dev, removed upstream
** Changed in: maas Milestone: next => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433697 Title: maas depends on syslinux-dev, removed upstream To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1433697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655447] Re: IEEE indexes in netaddr package may not match data in ieee-data package
** Changed in: maas Milestone: 2.4.x => 2.5.x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655447 Title: IEEE indexes in netaddr package may not match data in ieee-data package To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1655447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607345] Re: Collect all logs needed to debug curtin/cloud-init for each deployment
** Changed in: maas Milestone: 2.5.0beta2 => 2.5.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607345 Title: Collect all logs needed to debug curtin/cloud-init for each deployment To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1607345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752737] Re: [2.3.0-6434] mDNS observer problems
In MAAS we have provided a work around in LP: #1773698 ** Changed in: maas Milestone: 2.5.0beta1 => 2.5.0beta2 ** No longer affects: maas ** No longer affects: maas/2.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752737 Title: [2.3.0-6434] mDNS observer problems To manage notifications about this bug go to: https://bugs.launchpad.net/avahi/+bug/1752737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607345] Re: Collect all logs needed to debug curtin/cloud-init for each deployment
** Changed in: maas Milestone: 2.5.0beta1 => 2.5.0beta2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607345 Title: Collect all logs needed to debug curtin/cloud-init for each deployment To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1607345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752737] Re: [2.3.0-6434] mDNS observer problems
** Changed in: maas Milestone: 2.5.0 => 2.5.0beta1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752737 Title: [2.3.0-6434] mDNS observer problems To manage notifications about this bug go to: https://bugs.launchpad.net/avahi/+bug/1752737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI
** Changed in: maas Milestone: 2.5.0beta1 => 2.5.0beta2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789319 Title: Unable to load shimx64.efi using iPXE over UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1789319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790901] Re: Backporting s390x pxelinux style network booting from qemu 3.0 to bionic
** Description changed: QEMU 3.0 has recently released with support for pxelinux style network booting from s390x. As part of the MAAS roadmap, we have an item to enable s390x as a supported architecture for deployment of KVM image. Since QEMU now includes that support upstream, we would like an evaluation of whether it would be possible to backport this feature back to Bionic's QEMU to avoid having to create a work around in MAAS that are not supported upstream. Note that the MAAS team has not tested this feature. + + https://wiki.qemu.org/ChangeLog/3.0#s390_firmware -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790901 Title: Backporting s390x pxelinux style network booting from qemu 3.0 to bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1790901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790901] [NEW] Backporting s390x pxelinux style network booting from qemu 3.0 to bionic
Public bug reported: QEMU 3.0 has recently released with support for pxelinux style network booting from s390x. As part of the MAAS roadmap, we have an item to enable s390x as a supported architecture for deployment of KVM image. Since QEMU now includes that support upstream, we would like an evaluation of whether it would be possible to backport this feature back to Bionic's QEMU to avoid having to create a work around in MAAS that are not supported upstream. Note that the MAAS team has not tested this feature. ** Affects: qemu (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/1790901 Title: Backporting s390x pxelinux style network booting from qemu 3.0 to bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1790901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790663] Re: httpbakery: discharge does not work when hostname does not contain a dot
** Also affects: py-macaroon-bakery (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: py-macaroon-bakery (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: py-macaroon-bakery (Ubuntu Cosmic) 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/1790663 Title: httpbakery: discharge does not work when hostname does not contain a dot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/py-macaroon-bakery/+bug/1790663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790161] [NEW] simplestreams do not raise errors for failures behind a proxy
Public bug reported:
Simplestreams do not catch errors created for being behind a proxy.
In MAAS, we were expecting / validating for json to be returned from
simplestreams, but we kept seeing this failure:
[...]
line 325, in load_content
return json.loads(content)
File "/usr/lib/python3.6/json/__init__.py", line 354, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.6/json/decoder.py", line 339, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.6/json/decoder.py", line 357, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
To debug, I had to do this:
--- simplestreams/util.py 2016-11-28 14:54:35 +
+++ simplestreams/util.py 2018-08-31 14:32:54 +
@@ -320,6 +320,7 @@
def load_content(content):
+print(content)
if isinstance(content, bytes):
content = content.decode('utf-8')
return json.loads(content)
And this resulted in:
2018-08-31 14:13:36 stdout: [info] body
2018-08-31 14:13:36 stdout: [info] :lang(fa) { direction: rtl; font-size: 100%;
font-family: Tahoma, Roya, sans-serif; float: right; }
2018-08-31 14:13:36 stdout: [info] :lang(he) { direction: rtl; }
2018-08-31 14:13:36 stdout: [info] -->
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info] ERROR
2018-08-31 14:13:36 stdout: [info] The requested URL could not be
retrieved
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info] The following error was encountered while
trying to retrieve the URL: http://[2001:67c:1562:800a::6]:5240/MAAS/images-stream/streams/v1/index.json";>http://[2001:67c:1562:800a::6]:5240/MAAS/images-stream/streams
/v1/index.json
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info] Connection to 2001:67c:1562:800a::6
failed.
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info] The system returned: (110)
Connection timed out
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info] The remote host or network may be down.
Please try the request again.
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info] Your cache administrator is mailto:webmaster?subject=CacheErrorInfo%20-%20ERR_CONNECT_FAIL&body=CacheHost%3A%20localhost%0D%0AErrPage%3A%20ERR_CONNECT_FAIL%0D%0AErr%3A%20(110)%20Connection%20timed%20out%0D%
0ATimeStamp%3A%20Fri,%2031%20Aug%202018%2014%3A13%3A36%20GMT%0D%0A%0D%0AClientIP%3A%2010.246.88.6%0D%0AServerIP%3A%202001%3A67c%3A1562%3A800a%3A%3A6%0D%0A%0D%0AHTTP%20Request%3A%0D%0AGET%20%2FMAAS%2Fimages-stream%2Fstreams%2Fv1%2Findex.json%20HTTP%2F1.1%0AU
ser-Agent%3A%20python-simplestreams%2F0.1%0D%0AAccept-Encoding%3A%20gzip,%20deflate%0D%0AAccept%3A%20*%2F*%0D%0AConnection%3A%20keep-alive%0D%0AHost%3A%20%5B2001%3A67c%3A1562%3A800a%3A%3A6%5D%3A5240%0D%0A%0D%0A%0D%0A">webmaster.
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info] Generated Fri, 31 Aug 2018 14:13:36 GMT
by localhost (squid/3.1.19)
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info]
2018-08-31 14:13:36 stdout: [info]
Which shows that simplestreams was failing to access the mirror because of a
proxy issue, but it is not catching such issues.
** Affects: simplestreams
Importance: Undecided
Status: New
** Affects: simplestreams (Ubuntu)
Importance: Undecided
Status: New
** Also affects: simplestreams
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/1790161
Title:
simplestreams do not raise errors for failures behind a proxy
To manage notifications about this bug go to:
https://bugs.launchpad.net/simplestreams/+bug/1790161/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743595] Re: modprobing mlx5_core doesn't bring the interface up
** Tags added: track -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743595 Title: modprobing mlx5_core doesn't bring the interface up To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1743595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI
** Changed in: maas Milestone: None => 2.5.0beta1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789319 Title: Unable to load shimx64.efi using iPXE over UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1789319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI
isn't this the same issue as https://bugs.launchpad.net/maas/+bug/1711203 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789319 Title: Unable to load shimx64.efi using iPXE over UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1789319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787630] Re: Include HTTP support in pre-build GRUB module
** Attachment added: "debdiff" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1787630/+attachment/5181406/+files/debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787630 Title: Include HTTP support in pre-build GRUB module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1787630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772010] Re: [SRU] MAAS 2.3.5
For MAAS 2.3.4 I've marked this as verification failed. I'm uploading MAAS 2.3.5 which fixes a regression that was encountered by some users during testing and we were able to reproduce. I'm using this same bug report for MAAS 2.3.5. ** Description changed: [Impact] This is a new upstream release that addresses various issues present in 2.3.0. MAAS 2.3.4 fixes various issues that were present on MAAS 2.3.0. https://launchpad.net/maas/+milestone/2.3.1 https://launchpad.net/maas/+milestone/2.3.2 https://launchpad.net/maas/+milestone/2.3.3 https://launchpad.net/maas/+milestone/2.3.4 + https://launchpad.net/maas/+milestone/2.3.5 This point release includes fixes/enhancements for hardware enablement and to address customer related issues that are worth noting: Enhancements/Hardware Enablement * Bug 1750622 "[feature] Add ability to select the BIOS boot method for IPMI - To address issues with newer firmware" This adds a new option to power manage machines, that are oriented at addressing changes in upstream hardware firmware's (that have broken compatibility with older versions). Causes no behavior changes for MAAS as it continues to do the same. Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, and this change only takes effect by a user driven action. Bug 1758760 "[enhancement] Support Lenovo’s new password policy (Lenovo SR550)" Fixes the password generation process for IPMI discovery to consider new password policies that are being added to newer hardware or firmware versions. Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by testing the old password policy. If it doesn't work it will use the new password policy. LP: #1779712 [enhancement] maas-proxy port should be configurable Adds the ability to change the proxy port for the proxy that MAAS uses. If users upgrade, the configuration rendered will continue to use the default port. This will only take effect for users who change the port. Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by using the default port. This change only takes effect by a user driven action. LP: #1778710 [2.3] Allow telling MAAS image import to not use proxy. Allow's users to tell MAAS to import images without using the configured proxy, in cases that MAAS is directly connected to the internet but machines are not. Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, this would only take effect by a user driven action. Bug fixes that change existing behaviour Bug 1739761 [adds support to deploy Precise on MAAS 2.3] Re-adds the ability to deploy precise, which was dropped on MAAS 2.3 initially. Bug 1730751 "LACP rate fast by default" Changes the default LACP rate to fast, which addresses issues in that our IS department was facing. Note that this only changes how often the control packets are set and it is recommended/preferred to be set to fast, and the use of slow is discouraged. Bug 1767137 "Default install is now importing bionic by default instead of xenial" This is an issue that MAAS automatically started selection Bionic for commissioning instead of Xenial as it was intended. This ensure that Xenial is selected by default. Note that in case of upgrades, if Bionic is already selected, MAAS won't change this to Xenial. It will *only* affect to new installs. [Test Case] MAAS Testing 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. Solutions QA MAAS releases are also now vetted by the Solutions QA team. The test they run ensure there are no regression for their use cases. This release has been accepted / vetted by them. [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 continu
[Bug 1788641] Re: [SRU] MAAS 2.4.1
** Description changed: [Impact] This is a new upstream release that addresses various issues present in 2.4.2. MAAS 2.4.2 fixes various issues that were present on MAAS 2.4.2. https://launchpad.net/maas/+milestone/2.4.1 https://launchpad.net/maas/+milestone/2.4.2 This point release includes fixes/enhancements for hardware enablement and to address customer related issues that are worth noting: - Enhancements/Hardware Enablement - - - * Bug 1750622 "[feature] Add ability to select the BIOS boot method for - IPMI - To address issues with newer firmware" - - This adds a new option to power manage machines, that are oriented at - addressing changes in upstream hardware firmware's (that have broken - compatibility with older versions). Causes no behavior changes for MAAS - as it continues to do the same. - - Regression potential: None. MAAS will continue to behave the same way it - did before in new installs and upgrades, and this change only takes - effect by a user driven action. - - Bug 1758760 "[enhancement] Support Lenovo’s new password policy (Lenovo - SR550)" - - Fixes the password generation process for IPMI discovery to consider new - password policies that are being added to newer hardware or firmware - versions. - - Regression potential: None. MAAS will continue to behave the same way it - did before in new installs and upgrades, by testing the old password - policy. If it doesn't work it will use the new password policy. + Enhancements + LP: #1779712 [enhancement] maas-proxy port should be configurable Adds the ability to change the proxy port for the proxy that MAAS uses. If users upgrade, the configuration rendered will continue to use the default port. This will only take effect for users who change the port. Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by using the default port. This change only takes effect by a user driven action. LP: #1778710 [2.3] Allow telling MAAS image import to not use proxy. Allow's users to tell MAAS to import images without using the configured proxy, in cases that MAAS is directly connected to the internet but machines are not. Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, this would only take effect by a user driven action. - Bug fixes that change existing behaviour - + Resource Pools UI - MAAS 2.4.1 adds API & UI for resource pools. Al - Bug 1739761 [adds support to deploy Precise on MAAS 2.3] - Re-adds the ability to deploy precise, which was dropped on MAAS 2.3 initially. + Regression potential: Minimal. This is minimal because it doesn't affect + the current operation provided that everything already released in 2.4.0 + already included the resource pools feature. This only adds the missing + API endpoints and UI that's already been released in 2.5. - Bug 1730751 "LACP rate fast by default" - Changes the default LACP rate to fast, which addresses issues in that our IS department was facing. Note that this only changes how often the control packets are set and it is recommended/preferred to be set to fast, and the use of slow is discouraged. - - Bug 1767137 "Default install is now importing bionic by default instead of xenial" - This is an issue that MAAS automatically started selection Bionic for commissioning instead of Xenial as it was intended. This ensure that Xenial is selected by default. Note that in case of upgrades, if Bionic is already selected, MAAS won't change this to Xenial. It will *only* affect to new installs. [Test Case] MAAS Testing 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. Solutions QA MAAS releases are also now vetted by the Solutions QA team. The test they run ensure there are no regression for their use cases. This release has been accepted / vetted by them. [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 w
