** 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 notificati
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
** 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
** 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
** 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
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
** 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
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
** 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
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:
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
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
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
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
** 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
** 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
** 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:
** 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:
** 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:
** 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
** 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:
** 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
-
** 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
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:
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
** 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:
** 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
** 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
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
** 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
** 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
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
** 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
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
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 =
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
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
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,
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
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
** 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
@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
>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
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:
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.
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:
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
** 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:
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
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
** 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
** 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
** 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
** 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
** 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
** 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
** 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
** 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
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:
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
** 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
** 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
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
** 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
>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
** 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:
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
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
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 ...
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
** 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
** 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
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
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
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
** 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
** 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.
** 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:
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
ns
>
> 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
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
** 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
** 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
** 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
** 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
** 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
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.
** 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
** 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
** 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
** 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
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
** 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
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)
** 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:
** 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
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
** 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:
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
** 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
1 - 100 of 4346 matches
Mail list logo
