We have a test streams that uses the signed linux kernel instead of the
non-signed for x86. Can you please test it from this stream:
http://162.213.35.187/proposed/streams/v1/index.json
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: maas-images
Assignee: (unassigned) => Lee Trager (ltrager)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711203
Title:
Deployments fail when Secure Boot enabled
To manage
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732522
Title:
[2.3] Ephemeral boot environment does not renew DHCP leases
To manage
Public bug reported:
[Impact]
This is a new upstream release that addresses various issues present in 2.2 and
introduces various features that improve the robustness, and feature set of
MAAS.
MAAS 2.3.0 introduces the following features:
- Add support for CentOS & Windows networking.
** Changed in: ipxe (Ubuntu Zesty)
Importance: Undecided => Critical
** Changed in: ipxe (Ubuntu Xenial)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707999
** Summary changed:
- pod VM fails to PXE boot after receiving multiple DHCP offers, for different
IPs, from the dhcp server
+ [SRU] iPXE doesn't handle NAK requests when multiple DHCP server's offer
** Description changed:
+ [Impact]
+ When there are multiple DHCP servers on the network, iPXE
** Changed in: maas-images
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711203
Title:
Deployments fail when Secure Boot enabled
To manage notifications
** Branch linked: lp:~andreserl/maas-images/maas_images_signed_kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711203
Title:
Deployments fail when Secure Boot enabled
To manage notifications
** Also affects: maas-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711203
Title:
Deployments fail when Secure Boot enabled
To manage
** Changed in: maas-images
Status: New => Confirmed
** Changed in: maas-images
Importance: Undecided => High
** Changed in: maas-images
Importance: High => Critical
** Changed in: maas
Importance: Undecided => Critical
** Changed in: maas
Milestone: None => 2.3.0
--
You
** Changed in: maas
Milestone: 2.3.0 => 2.3.x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319600
Title:
maas-cli stack trace if .maascli.db unreadable
To manage notifications about this bug
** Changed in: maas
Milestone: 2.3.0 => 2.3.x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680266
Title:
[2.x, API] interface update will return successful with invalid params
To manage
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during commissioning or testing)
To
@Chris,
Can you attach the output of:
maas machine get-curtin-config
And attach the follow curtin log (you can grab that from the UI under
the Installation tab).
Also, this seems an issue widely with Ubuntu.
Curtin is the one that writes this configuration, so marking this as
Incomplete for
We believe this is no longer an issue in the latest releases of MAAS.
Please upgrade to the latest version of MAAS, and If you believe this
issue is still present, please re-open this bug report or file a new
one.
** Changed in: maas
Status: Triaged => Won't Fix
--
You received this bug
I believe that in the latest versions of MAAS, this has now been fixed.
If you believe this issue still exists, please re-open this bug report
or file a new one.
** No longer affects: python-tx-tftp
** Changed in: python-tx-tftp (Ubuntu)
Status: New => Invalid
** Changed in: maas
** Changed in: maas
Milestone: None => 2.3.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319600
Title:
maas-cli stack trace if .maascli.db unreadable
To manage notifications about this bug
** Changed in: maas
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442112
Title:
booting ppc64el with hwe-u kernel hangs in initrd
To manage notifications about
** Changed in: maas
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307614
Title:
MAAS sometimes attempts to install to USB flash drive
To manage
** Changed in: maas
Milestone: 2.0.0 => next
** Changed in: maas
Status: Triaged => Won't Fix
** Changed in: maas (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: maas (Ubuntu)
Status: New => Fix Released
** Changed in: maas/2.0
Status: Triaged => Won't Fix
** Changed in: maas/2.0
Milestone: 2.0.1 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi James,
Can you please provide the following:
1. MAAS version and logs (/var/log/maas/regiond.log,maas.log)'
2. The dump of machine that would satisfy constraints: e.g. maas admin machines
read hostname=
3. Can you provide the Juju debug lab where it is making a request to MAAS
sending the
debug log*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729127
Title:
storage: No available machine matches constraints
To manage notifications about this bug go to:
I've verified these two manually! Thanks for all the work!
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
while there's a traceback, the reality of it is that MAAS itself
recovers, so it is not immediately a blocking issue.
** Changed in: maas
Milestone: None => 2.3.x
** Changed in: maas
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bumping this to critical provided that at this point, this completely
breaks MAAS.
** Changed in: resolvconf (Ubuntu Xenial)
Importance: Medium => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also, I've tested this in GMAAS and confirm the fix works!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during commissioning or testing)
To manage
** Changed in: ipxe (Ubuntu Bionic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707999
Title:
pod VM fails to PXE boot after receiving multiple DHCP offers,
*** This bug is a duplicate of bug 1721808 ***
https://bugs.launchpad.net/bugs/1721808
You need a newer version of curtin, which is currently available on
xenial-proposed.
** Changed in: maas
Status: Confirmed => Invalid
** Changed in: maas (Ubuntu Xenial)
Status: Confirmed =>
@Mark,
I do have access (just tested). I'll give it a try tomorrow! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during commissioning or
** Also affects: maas
Importance: Undecided
Status: New
** No longer affects: maas (Ubuntu)
** Changed in: maas
Milestone: None => 2.3.0beta3
** Also affects: maas/2.2
Importance: Undecided
Status: New
** Changed in: maas/2.2
Milestone: None => 2.2.3
--
You
As David said, and to clarify, I was planning on uploading this patch to
the archive, but I wanted to double check with you guys to ensure that
the implementation is sane from your perspective, as this will affect
ipxe clients that receive DHCPNACKs.
Also, it would be good to get a different
@Christian,
We cannot test the zesty package nor grab the package and install it in
xenial because it needs to be built against the xenial archive for the
library linking. As such, I would recommend this patch is pushed to
-proposed where we can test it against the libraries of the archive.
That
** Changed in: maas
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389811
Title:
tgtadm: out of memory crash
To manage notifications about this bug go to:
** Patch added: "handle-dhcp-nack.patch"
https://bugs.launchpad.net/maas/+bug/1707999/+attachment/4969236/+files/handle-dhcp-nack.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707999
** Changed in: maas
Status: Incomplete => Invalid
** Changed in: maas/2.2
Status: Incomplete => Invalid
** Changed in: ipxe (Ubuntu)
Assignee: (unassigned) => Andres Rodriguez (andreserl)
--
You received this bug notification because you are a member of Ubuntu
Bu
** Changed in: maas
Assignee: (unassigned) => Blake Rouse (blake-rouse)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707999
Title:
pod VM fails to PXE boot after receiving multiple DHCP
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during commissioning or testing)
To
** Also affects: ipxe (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ipxe (Ubuntu)
Importance: Undecided => Critical
** Changed in: maas
Status: Triaged => Incomplete
** Changed in: maas/2.2
Status: Triaged => Incomplete
--
You received this bug
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Changed in: maas
Milestone: 2.3.0 => 2.3.0beta2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during commissioning or testing)
To manage
** Tags added: internal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382774
Title:
Postgresql installation for MAAS fails on locales missing language
packs
To manage notifications about this
** Tags added: internal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570633
Title:
[2.0 beta 2] Nodes fail to remain powered after Trusty commission with
"Allow SSH" selected
To manage
** Changed in: maas
Status: Triaged => Won't Fix
** Changed in: maas (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394306
Title:
maas 1.7 upgrade:
** Changed in: maas
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389811
Title:
tgtadm: out of memory crash
To manage notifications about this bug go to:
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717287
Title:
maas-enlist doesn't work when provided with serverurl with IPv6
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713795
Title:
[1.9] Unable to install 14.04, shim.efi.signed renamed
To manage
** Changed in: maas
Status: Confirmed => Won't Fix
** Changed in: maas
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590689
Title:
MAAS 1.9.3 + Juju
** Changed in: maas
Milestone: 2.3.0 => 2.3.0beta1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717287
Title:
maas-enlist doesn't work when provided with serverurl with IPv6
address
To
@Brian,
I've uploaded a new version of the package including this change, but I
think you may have to reject the previous upload as it shares the same
version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: maas/2.2
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717287
Title:
maas-enlist doesn't work when provided with serverurl with IPv6
address
** Changed in: maas/2.2
Assignee: (unassigned) => Andres Rodriguez (andreserl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717287
Title:
maas-enlist doesn't work when provi
** Also affects: maas/2.2
Importance: Undecided
Status: New
** Changed in: maas/2.2
Milestone: None => 2.2.3
** Changed in: maas/2.2
Importance: Undecided => High
** Changed in: maas/2.2
Status: New => Triaged
--
You received this bug notification because you are a
** Changed in: maas
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717287
Title:
maas-enlist doesn't work when provided with serverurl with IPv6
address
To
Hi All,
So what's the latest status on this and/or what is the proposed fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during commissioning or
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
Grub package upgrades overwrites NVRAM, causing MAAS boot order to be
** Changed in: maas
Milestone: 2.3.0 => 2.3.0alpha3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
Grub package upgrades overwrites NVRAM, causing MAAS boot order to be
** Tags added: internal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717287
Title:
maas-enlist doesn't work when provided with serverurl with IPv6
address
To manage notifications about this
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Milestone: None => 2.3.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717287
Title:
maas-enlist doesn't
Yes, this will work only with the version in trusty-updates, provided
that all of our known customers/users are already using trusty-updates,
and as such, we do not need to be compatible with trusty-security.
** Changed in: maas (Ubuntu)
Status: Incomplete => New
--
You received this bug
** Changed in: maas
Status: Confirmed => In Progress
** Also affects: maas/2.2
Importance: Undecided
Status: New
** Changed in: maas/2.2
Milestone: None => 2.2.3
** Changed in: maas/2.2
Importance: Undecided => High
** Changed in: maas/2.2
Status: New => Triaged
>From our irc discussion:
18:27 < dpb> but it's booted just fine as recently as 2 days ago
A new grub version was published on 2017-07-28 in
2.02~beta2-36ubuntu3.12. This seems like it could be a regression in
grub that 2.02~beta2-36ubuntu3.13 (currently in proposed) could
probably fix.
**
*** This bug is a duplicate of bug 1711700 ***
https://bugs.launchpad.net/bugs/1711700
Hi Jeff,
If MAAS is reloading DNS constantly, it is because you have machines
from the dynamic range obtaining new IP addresses. That said, the issue
is not MAAS reloading, but rather, it is bind failing
** Description changed:
- After a recent update, it's no longer possible to install Ubuntu 14.04
- with MaaS 1.9.5 . This is on a new installation of MaaS on 14.04.
+ [Impact]
+ After a recent update, it's no longer possible to install Ubuntu 14.04 with
MaaS 1.9.5 . This is on a new installation
** Changed in: maas (Ubuntu)
Status: In Progress => New
** Changed in: maas (Ubuntu)
Assignee: Andres Rodriguez (andreserl) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Hi John,
There's a patch attached which you can apply to resolve this issue. We
are working to get this SRU'd.
Thanks!
** Changed in: maas
Status: Triaged => In Progress
** Changed in: maas (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because
The work around is to pass a debconf configuration option to grub2
package to not update the NVRAM on package upgrade.
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas
Status: New => Confirmed
** Changed in: maas
Importance: Und
** Summary changed:
- UEFI Xenial install sets computer to boot from hard disk
+ Grub upgrades overwrites NVRAM cuasing MAAS/curtin boot order to be overwriten
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In ipmitool 1.18.17+
$ ipmitool -I lanplus -U xxx -P xxx -H X.X.X.X chassis bootdev pxe
options=persistent,efiboot
Set Boot Device to pxe
$ ipmitool -I lanplus -U xxx -P xxx -H X.X.X.X chassis bootparam get 5
Boot parameter version: 1
Boot parameter 5 is valid/unlocked
Boot parameter data:
So the concern we are primarily interested on is the upgrade scenario.
Effectively, if 'ubuntu' is already in the boot order (and it is not the
first one), on grub2 upgrade, it shouldn't be overwriting the current
BootOrder (e.g. because we specifically configured it to Boot from the
Network
Public bug reported:
This is a follow up discussion from #1642298 and filing this bug to keep
a record.
On a fresh Ubuntu install, grub2 overwrites the NVRAM and updates to
boot order to have Ubuntu as the first boot device. This affects
situations in which PXE had been set the first boot device
Hi Rod,
Judging by your message in #2, unless I'm missing something, you would have not
been able to re-deploy the machine because efibootmgr had set the boot order to
the disk first. When you re-deployed the machine, MAAS told that machine that
"on the next boot, PXE boot".
"
- The node was
Hey guys.
Sorry for joining the party late. But let me see if I understand the
full extent of the problem here.
0. A machine PXE boots off MAAS, installs Ubuntu in it, grub gets
installed and configured without updating the NVRAM.
1. The machine reboots, PXE's, boots from local disk, and
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas
Milestone: None => 1.9.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713795
Title:
** Changed in: maas
Importance: Undecided => Critical
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Importance: Undecided => Critical
** Changed in: maas (Ubuntu)
Assignee: (unassigned) => Andres Rodriguez (
** Summary changed:
- interface update will return successful with invalid params
+ [2.x, API] interface update will return successful with invalid params
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710278
Title:
[2.3a1] named stuck on reload, DNS broken
To manage notifications
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705504
Title:
[2.3] on install MAAS has system warnings
To manage notifications
ning)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions
>
--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer
--
You received this bug notification because you are a memb
ubuntu@withkvm:~$ cat /proc/cmdline
BOOT_IMAGE=ubuntu/amd64/generic/xenial/daily/boot-kernel nomodeset
root=squash:http://192.168.122.2:5248/images/ubuntu/amd64/generic/xenial/daily/squashfs
ro ip=withkvm:BOOTIF ip6=off overlayroot=tmpfs
overlayroot_cfgdisk=disabled cc:{'datasource_list':
** Changed in: maas
Milestone: 2.3.0 => 2.3.0alpha2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705504
Title:
[2.3] on install MAAS has system warnings
To manage notifications about this
** Changed in: maas
Milestone: 2.3.0 => 2.3.0alpha2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710278
Title:
[2.3a1] named stuck on reload, DNS broken
To manage notifications about this
Public bug reported:
Using MAAS 2.3, during commissioning (and likely in the rest of the
ephemeral environment) we have noticed that resolv.conf is not set with
the DNS server.
That said, during the commissioning process, MAAS does not send any
metadata to cloud-init to configure the network,
Since 2.02-beta2-36ubuntu3.11 works but .12 (which is the latest in
Xenial updates doesn't) this seems to confirm the regression in grub.
marking invalid for NAAS and curtin!
Maas will automatically pick up a fixed grub once on the archive.
** Also affects: grub2 (Ubuntu)
Importance:
FWIW, while this change may things nicer moving forward, this makes it
very difficult to maintain code that needs to work on both, Xenial and
Artful+. Having the old API still available would allow applications to
continue to rely on the module without having to do any hackery,
specially, since
Other areas this doesn't work anymore:
ubuntu = UbuntuDistroInfo()
ubuntu._rows
...
AttributeError: 'UbuntuDistroInfo' object has no attribute '_rows'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
A new version of distro-info has just broken all applications that rely
on the python module. One of this applications is MAAS.
Example:
# In Xenial, you would do something like:
from distro_info import UbuntuDistroInfo
info = UbuntuDistroInfo()
for row in
I've tested this both in Xenial and Zesty as per the bug report testing
from proposed section, and can verify that everything works as expected!
** Tags removed: verification-needed verification-needed-xenial
verification-needed-zesty
** Tags added: verification-done verification-done-xenial
Hi Steve,
python3-googleapi is present in the Archive. https://packages.ubuntu.com
/xenial-updates/python/python3-googleapi
The reason why we need a conflicts is because both MAAS and
python3-googleapi installs in /usr/lib/python3/dist-packages/apiclient,
which obviously we need a conflicts.
** Description changed:
[Impact]
This is a new upstream release that addresses various upstream bugs. MAAS
2.2.2 does NOT introduce any new features.
Please see CHANGELOG for further details.
[Test Case]
MAAS testing has been done in various cases, partially documented
** Changed in: maas (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708651
Title:
[SRU] MAAS 2.2.2
To manage notifications about this bug go to:
** Changed in: maas (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696752
Title:
[SRU] MAAS 2.2.0
To manage notifications about this bug go to:
Public bug reported:
[Impact]
This is a new upstream release that addresses various upstream bugs. MAAS 2.2.2
does NOT introduce any new features.
Please see CHANGELOG for further details.
[Test Case]
MAAS testing has been done in various cases, partially documented
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Milestone: None => 2.3.0
** Changed in: maas
Importance: Undecided => High
** Changed in: maas
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
The versions in -proposed for all releases have been tested as per the
description of the bug.
2.2.0+bzr6054-0ubuntu2~17.04.1
2.2.0+bzr6054-0ubuntu2~16.10.1
2.2.0+bzr6054-0ubuntu2~16.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've verified -proposed on all releases and marked this as verification-
done.
** Tags removed: verification-needed verification-needed-xenial
verification-needed-yakkety verification-needed-zesty
** Tags added: verification-done verification-done-xenial
verification-done-yakkety
MAAS 2.2 does not support Django 1.11, which is in Artful. This is
causing the failure you are seeing. MAAS 2.3 will fix this and the first
alpha wi be released next week, and will replace this package. As such,
im marking this as won't fix.
** Changed in: maas (Ubuntu)
Status: New =>
; High
** Changed in: maas/2.2
Status: New => Triaged
** Changed in: maas/2.2
Assignee: (unassigned) => Andres Rodriguez (andreserl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16
** Changed in: maas-images
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543204
Title:
cloud images should have /lib/modules inside
To manage
** Changed in: maas-images
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568918
Title:
Add support for lts-xenial kernel flavours in trusty
To manage
401 - 500 of 4346 matches
Mail list logo
