Finally got around to test this. ANd this are my findings:
1. Installed 4.15-rc1 above, rebooted the machine, and did not see the
issue.
ubuntu@just-pika:~$ uname -a
Linux just-pika 4.15.0-041500rc1-generic #201711262030 SMP Mon Nov 27 01:32
So I've tested all the way from rc2 -> rc7, and confirm that rc7 is the
issue. In two different machines:
machine1: running kernel was rc3
machine2: running kernel was rc4
In both cases, after install of rc7, and reboot, I see the issue. Logs
for the latest:
https://pastebin.ubuntu.com/p/yVTWBRq
** Changed in: maas
Milestone: 2.4.0beta4 => 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/1655447
Title:
IEEE indexes in netaddr package may not match data in ieee-data
package
To mana
** Changed in: maas
Milestone: 2.4.0beta4 => 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/1752737
Title:
[2.3.0-6434] mDNS observer problems
To manage notifications about this bug go to:
Public bug reported:
[Impact]
This is a new upstream release that addresses various issues present in 2.3.0.
MAAS 2.3.3 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/+milest
@Joseph:
Issue still exists:
ubuntu@superb-whale:~$ uname -a
Linux superb-whale 4.15.0-041500rc6-generic #201805171959 SMP Thu May 17
20:02:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@superb-whale:~$ sudo reboot
===
Stopping LVM2 metadata daemon...
** Changed in: maas
Status: New => Incomplete
** Changed in: maas
Status: Incomplete => Invalid
** Also affects: curtin
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- deployment timed o
** Changed in: maas
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772490
Title:
bcache: register_bcache() error
To manage notifications about this bug go to:
h
Hi Ashley,
Marking this incomplete for MAAS (although I think it is invalid).
Opening a task for curtin and for the kernel team. The error in curtin
implies is the same issue as [1]. Judging from [2], it seems that it
should already be fixed:
May 21 10:57:03 geodude cloud-init[1643]: Processing t
** Attachment added: "rsyslog-bcache-failure"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772490/+attachment/5142552/+files/rsyslog-bcache-failure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Attached the rsyslog showing the error. It indeed doesn't seem like
there were any curtin failures, but I wonder that, while curtin
successfully process, the machine actually doesn't actually boot onto
the filesystem due to the kernel issue?
--
You received this bug notification because you are a
@Ashley,
Could you please start gathering the logs from HAProxy running for the
MAAS servers?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772490
Title:
bcache: register_bcache() error
To manage
@Ryan,
I'm marking this as incomplete for curtin provided that after further
debugging, I can see that the late command that's supposed to send the
"netboot_off" operation is not being sent.
This could be because curtin failed but we are lacking logs to determine
this.
** Changed in: curtin
@Ryan,
Marking this as invalid for curtin again. I looked closely to the log
and saw this:
May 21 11:00:35 geodude cloud-init[1643]: --2018-05-21 11:00:35--
http://10.244.40.33/MAAS/metadata/latest/by-id/gnbttp/
May 21 11:00:35 geodude cloud-init[1643]: Connecting to 10.244.40.33:80...
connect
** Description changed:
Ubuntu Bionic currently has MAAS 2.4 alpha 1. This is a Standing Feature
Freeze Exception request for MAAS 2.4 upcoming alpha/beta/rc/final
releases for Ubuntu Bionic.
Dependencies & Upgrade
==
MAAS 2.4 has introduced the following feat
** 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/1749246
Title:
[2.3] Image download hardlinks the hwe-*-edge as the generic kernel
i
** 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/1743966
Title:
Trusty deployments fail when custom archive keys are configured
To mana
** 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/1754012
Title:
[FFe] openwsman, wsmancli
To manage notifications about this bug go to:
** Changed in: maas
Milestone: 2.4.0alpha2 => 2.4.0beta1
--
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
T
I hit the same issue and had to force the v4 address as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756032
Title:
No VPN connectivity when accessing tunnel endpoint over IPv6
To manage not
** Changed in: maas
Milestone: 2.4.x => 2.4.0beta1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743249
Title:
High IO on the system prevents MAAS to provide PXE config in a timely
manner (le
Hi There,
The MAAS images use the kernels that are available in the archive. Since
this is a kernel issue, I'm retargetting to the linux package in Ubuntu.
If this is already fixed, MAAS will automatically update new images once
the packages are available in the archive, otherwise, please feel fr
** Changed in: maas
Status: Incomplete => 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/1361241
Title:
maas automatic u
Dear user,
This is an automated message.
We believe this bug report is no longer an issue in the latest version
of MAAS. For such reason, we are making this issue as Won't Fix. If you
believe this issue is still present in the latest version of MAAS,
please re-open this bug report.
** Changed in
Dear user,
This is an automated message.
We believe this bug report is no longer an issue in the latest version
of MAAS. For such reason, we are making this issue as Won't Fix. If you
believe this issue is still present in the latest version of MAAS,
please re-open this bug report.
--
You recei
** Changed in: maas
Importance: Critical => High
** Changed in: maas/2.3
Importance: Critical => High
--
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 pack
Dear user,
This is an automated message.
We believe this bug report is no longer an issue in the latest version
of MAAS. For such reason, we are making this issue as Won't Fix. If you
believe this issue is still present in the latest version of MAAS,
please re-open this bug report.
** Changed in
Dear user,
This is an automated message.
We believe this bug report is no longer an issue in the latest version
of MAAS. For such reason, we are making this issue as Won't Fix. If you
believe this issue is still present in the latest version of MAAS,
please re-open this bug report.
** Changed in
** Changed in: maas
Status: In Progress => Fix Committed
** 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/1713795
Title:
[1
** Changed in: maas
Milestone: None => 2.4.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:
** Summary changed:
- [2.4, regression] Cannot compose a machine inside
+ libvirt drops connection when attaching a disk
** Description changed:
+ libvirt is dropping the connection when attaching a disk. This used to
+ work as of last week. There;s been a new libvirt published in the
+ archive
segfaults in dmesg:
[ 3371.756438] libvirtd[30973]: segfault at 0 ip 7fedded4dfc0 sp
7fedd151b968 error 4 in libvirt.so.0.4000.0[7feddec3c000+3be000]
[ 4805.107412] libvirtd[31525]: segfault at 0 ip 7f91d9cd0fc0 sp
7f91cdca1968 error 4 in libvirt.so.0.4000.0[7f91d9bbf000+3be000]
** Changed in: maas
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757210
Title:
libvirt drops connection when attaching a disk (breaks MAAS pods)
To manage not
** Changed in: maas
Milestone: 2.4.0beta1 => 2.4.0beta2
--
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 g
** Changed in: maas
Milestone: 2.4.0beta1 => 2.4.0beta2
--
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
** Changed in: maas (Ubuntu)
Status: New => Triaged
** Changed in: maas (Ubuntu)
Importance: Undecided => High
** Also affects: maas
Importance: Undecided
Status: New
** No longer affects: juju
** No longer affects: maas (Ubuntu)
** Summary changed:
- static routes get los
Hi!
We believe this is no longer an issue in 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 this bug report.
Thanks
** Changed in: maas
Status: Triaged => Invalid
** Changed in: maas (Ubuntu)
Stat
Hi!
We believe this is no longer an issue in 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 this back report.
Thanks
** Changed in: maas
Status: Triaged => Invalid
--
You received this bug notification
Hi!
We believe this is no longer an issue in 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 this bug report.
Thanks
** Changed in: maas
Status: Incomplete => Invalid
** Changed in: maas (Ubuntu)
S
Hi!
We believe this is no longer an issue in 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 this back report.
Thanks
** Changed in: maas
Status: Triaged => Invalid
--
You received this bug notification
Hi!
We believe this is no longer an issue in 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 this bug report.
Thanks
** Changed in: maas
Status: Triaged => Invalid
** Changed in: maas (Ubuntu)
Stat
Hi!
**This is an automated message**
We believe this is may no longer be an issue in the latest MAAS release.
Due to the date of this bug report, we are marking this bug report as
invalid. If you believe this is still an issue, please re-open this bug
report.
Thanks
** Changed in: maas
S
Hi!
We believe this is no longer an issue in 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 this bug report.
Thanks
** Changed in: maas
Status: Triaged => Invalid
** Changed in: maas (Ubuntu)
Stat
Hi!
**This is an automated message**
We believe this is no longer an issue in 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 this bug report.
Thanks
** Changed in: maas
Status: Triaged => Invalid
--
Yo
Hi!
**This is an automated message**
We believe this is may no longer be an issue in the latest MAAS release.
Due to the report date of this, we are currently marking it as Invalid.
If you believe this bug report still valid against the latest release of
MAAS, or if you are still interested in th
** Changed in: maas/2.2
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
ad
** Changed in: maas/2.2
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 a
Hi Eric,
I experience the same issue in non-MAAS deployed machines after
upgrading to the latest kernel. AS such, I'm marking this as invalid for
MAAS and opening a task for the kernel.
** Changed in: maas
Status: New => Invalid
** Also affects: linux (Ubuntu)
Importance: Undecided
** 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/1749246
Title:
[2.3] Image download hardlinks the hwe-*-edge as the generic kernel
instead of the ga-* kernel.
T
** Changed in: maas (Ubuntu)
Status: New => Triaged
** Tags added: ui ux
** Summary changed:
- MAAS web ui should help configure DHCP on first start
+ [UX] MAAS web ui should help configure DHCP on first start
** Also affects: maas
Importance: Undecided
Status: New
** No longe
** Changed in: maas
Milestone: 2.4.0beta3 => 2.4.0beta4
--
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 g
** Changed in: maas
Milestone: 2.4.0beta3 => 2.4.0beta4
--
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
- Custom configuration to ensure proper operation.
Changes:
https://launchpad.net/maas/2.4/2.4.0beta3
** Affects: maas (Ubuntu)
Importance: Undecided
Assignee: Andres Rodriguez (andreserl)
Status: New
** Changed in: maas (Ubuntu)
Assignee: (unassigned) => And
** Changed in: maas (Ubuntu)
Assignee: Andres Rodriguez (andreserl) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768800
Title:
[SRU] MAAS 2.4.0beta3 to bionic
To man
** Description changed:
We would like to request a SRU for MAAS 2.4. This follows the draft SRU
exception process described at https://wiki.ubuntu.com/MAASUpdates
[Impact]
This is a new version of MAAS only provides bugfixes that improve the
stability of 2.4.
[Regression Potential
Hi Roger,
Could you please ensure your postgres is running and then:
sudo apt-get -f install
It may seem like postgres could be the culprit.
** Changed in: maas (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Milestone: None => 2.4.0rc1
** No longer affects: maas (Ubuntu)
** Summary changed:
- 2.4 beta3 traceback while enlisting
+ [2.4b3] traceback while enlisting
--
You received this bug notification because
Hi!
**This is an automated message**
We believe this is may no longer be an issue in the latest MAAS release.
Due to the original date of the bug report, we are currently marking it
as Invalid. If you believe this bug report still valid against the
latest release of MAAS, or if you are still inte
Hi Scott,
To clarify,
1. your machine was "allocated", not "deployed" right?
2. Only machines that are "deployed" should go back into booting from the disk.
** No longer affects: maas (Ubuntu)
** Changed in: maas
Status: New => Incomplete
** Changed in: maas
Milestone: None => 2.4.0
Hi!
**This is an automated message**
We believe this is may no longer be an issue in the latest MAAS release.
Due to the original date of the bug report, we are currently marking it
as Invalid. If you believe this bug report still valid against the
latest release of MAAS, or if you are still inte
Hi!
**This is an automated message**
We believe this is may no longer be an issue in the latest MAAS release.
Due to the original date of the bug report, we are currently marking it
as Invalid. If you believe this bug report still valid against the
latest release of MAAS, or if you are still inte
** 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
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 y
** 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 manag
** 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 notif
** 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
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
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 r
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:
201
** 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
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 o
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:
Una
** 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
** 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
- ESX
** 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.
+ [Impact]
+ MAAS 2.6 is the new upstream release of MAAS. This new release introduces
several performance improvements, tracking and various other
** 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:
** 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://b
** 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:
htt
** 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 n
** 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 m
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
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 e
** 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
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 Ubunt
** 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 th
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
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.g
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
** 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 pani
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
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
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 an
I can no longer deploy Xenial on the same hardware. I see the same
issues as with Bionic (Note that the system PXE boots just fine, loads
the ephemeral env, but gets stuck in the same place).
hostname big-koi hostname big-koi hostname big-koi hostname big-koi hostname
big-koi hostname big-koi IP-
Public bug reported:
The Candid server provides a macaroon-based authentication service.
URL: https://github.com/CanonicalLtd/candid
License: AGPL-2+
** Affects: ubuntu
Importance: Undecided
Assignee: Andres Rodriguez (andreserl)
Status: In Progress
** Changed in: ubuntu
** Changed in: maas
Milestone: 2.5.0alpha2 => 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/1607345
Title:
Collect all logs needed to debug curtin/cloud-init for each deployment
To m
Public bug reported:
[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
** No longer affects: maas (Ubuntu)
** No longer affects: maas (Ubuntu Xenial)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767137
Title:
[2.3] Default install is now importing bionic by default
** 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 r
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 rel
301 - 400 of 2956 matches
Mail list logo
