** 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/1762555
Title:
ipmi-config connection timeout
To manage notifications about this bug go
Curtin for Artful from -proposed has been verified:
Full log on: http:///job/proposed-maas-curtin-
manual/13/console
package-test-stdout);'], kind test, sout raw, serr raw, env []
maas-integration.TestMAASIntegration.test_create_admin ... ok
Curtin for Xenial from -proposed has been verified:
Full log on: http:///job/proposed-maas-curtin-
manual/12/console
Selecting previously unselected package curtin-common.
Preparing to unpack .../curtin-common_18.1-1-g45564eef-0ubuntu1~16.04.1_all.deb
...
Unpacking curtin-common
Xenial has been verified against MAAS CI:
http://:8080/job/proposed-maas-images-manual/32/console
maas-integration.TestMAASIntegration.test_create_admin ... ok
maas-integration.TestMAASIntegration.test_restart_dbus_avahi ... SKIP:
Avahi/DBUS are not used anymore
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104521/+files/ProcCpuinfoMinimal.txt
** Description changed:
From an ephemeral environment in an HPGen9, the machine fails to reboot
when the ephemeral environment is
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104523/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
collecting logs with mainline kernel.
** Summary changed:
- Rebooting bionic fails with hardware error
+ Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
** Description changed:
From an ephemeral environment in an HPGen9, the machine fails to reboot
when the ephemeral
Test both -proposed & 4.16 kernels, and the issue persists.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761796
Title:
Rebooting bionic fails with
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104424/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Summary changed:
- Rebooting bionic running on an ephemeral env (overlayfs) fails with hardware
error
+ Rebooting bionic fails with hardware error
** Description changed:
From an ephemeral environment in an HPGen9, the machine fails to reboot
- with the following
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104428/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761796
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104427/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761796
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104425/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104422/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761796
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104421/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761796
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104426/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761796
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104423/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761796
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104420/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104391/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761796
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104392/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104394/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761796
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104395/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761796
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104396/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761796
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104390/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761796
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104393/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104389/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761796
Title:
apport information
** Tags added: apport-collected uec-images
** Description changed:
From an ephemeral environment in an HPGen9, the machine fails to reboot
with the following hardware error.
This doesn't happen on xenial, it only happens in Bionic.
Full log from the moment the
** Description changed:
+ From an ephemeral environment in an HPGen9, the machine fails to reboot
+ with the following hardware error.
+
+ This doesn't happen on xenial, it only happens in Bionic.
+
+ Full log from the moment the 'sudo reboot' was executed:
+
Public bug reported:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling.
Stopping LVM2 metadata daemon...
[
** Description changed:
Deploying a machine with Bionic results in networking not configured in
the initramfs, which fails the deployment process.
Deploying Xenial works just fine.
Full log is available in: https://pastebin.ubuntu.com/p/y7nJttSt5x/
- [ 65.435628] async_tx: api
Public bug reported:
Deploying a machine with Bionic results in networking not configured in
the initramfs, which fails the deployment process.
Deploying Xenial works just fine.
Full log is available in: https://pastebin.ubuntu.com/p/y7nJttSt5x/
[ 65.435628] async_tx: api initialized (async)
** Changed in: maas
Status: Fix Committed => Fix Released
** Changed in: maas
Milestone: 2.3.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/1711203
Title:
Deployments fail when
** Changed in: maas
Milestone: 2.4.0beta2 => 2.4.0beta3
--
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
** Changed in: maas
Milestone: 2.4.0beta2 => 2.4.0beta3
--
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
>From IRC discussion:
1. /etc/maas/regiond.conf:maas_url was http:///MAAS
2. /etc/maas/rackd.conf:maas_url was http://localhost:5240/MAAS
3. /etc/maas/regiond.conf was updated to http://:5240/MAAS &
/etc/maas/rackd.conf was left as http://localhost:5240/MAAS
4. restart maas-regiond
5.
*** This bug is a duplicate of bug 1756846 ***
https://bugs.launchpad.net/bugs/1756846
Thanks to the investigation from Steve, it seems that during the dist-
upgrade process ifupdown was removed due a transient conflict during the
devel cycle. This caused it to be removed. It being removed
https://pastebin.ubuntu.com/p/YPRxSrjHZ9/
** Changed in: netplan.io (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761294
Title:
Network configuration
cloud-init-output.log after manually rebooting the machine.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => New
** Attachment added: "cloud-init-output.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1761294/+attachment/5101804/+files/cloud-init-output.log
**
I dont believe this is a cloud-init issue provided that cloud-init seems
to not run networking on reboots, and networking is disabled:
ubuntu@maas00:/etc/cloud/cloud.cfg.d$ cat
curtin-disable-cloudinit-networking.cfg
network: {config: disabled}
--
You received this bug notification because
Public bug reported:
I deployed Xenial in this machine with MAAS. After deployment i had re-
configured interfaces manually (on /etc/network/interfaces), and removed
/etc/network/interfaces.d. At some point, I upgraded the machine from
Xenial to Bionic, and everything was working just fine with
** Changed in: maas
Status: Won't Fix => Incomplete
** 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/1742324
Title:
Bionic kernel
** 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/1743249
Title:
High IO on the system prevents MAAS to provide PXE config in a timely
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
** 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
** 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
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
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
--
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)
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
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)
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)
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)
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
** 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
** 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
** 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
** 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
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]
** 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
** 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:
** 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:
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
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
** 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
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
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
** 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
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
** 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
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
** 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
** 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
** 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
** 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
** 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
; Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: andreserl sabdfl sil2100
> Launchpad-Bug-Reporter: Mark Shuttleworth (sabdfl)
> Launchpad-Bug-Modifier: Mark Shuttleworth (sabdfl)
> Launchpad-M
I've uploaded a new revision of the package fixing the binary to reflect
the correct soname.
--
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
Public bug reported:
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 features:
-
** Changed in: maas
Importance: High => Medium
** Changed in: maas
Status: Won't Fix => Triaged
** Changed in: maas
Importance: Medium => Low
** Changed in: maas
Milestone: None => 2.4.x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
- wsman is useful in MAAS for AMT device power control. In Bionic, curl3
- is being replaced with curl4, and upgrades are currently complicated by
- the fact that wsman ultimately depends on curl3 (via wsman-cli and
- libswman-curl-client-transport1 which depends on
ged in: wsmancli (Ubuntu)
Status: In Progress => Triaged
** Changed in: openwsman (Ubuntu)
Assignee: Andres Rodriguez (andreserl) => (unassigned)
** Changed in: wsmancli (Ubuntu)
Assignee: Andres Rodriguez (andreserl) => (unassigned)
** Changed in: openwsman (Ubuntu)
4.0alpha2
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas
Status: Triaged => In Progress
** Also affects: openwsman (Ubuntu)
Importance: Undecided
Status: New
** Also affects: wsmancli (Ubuntu)
Importance: Undecided
** Changed in: maas/2.3
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/1711203
Title:
Deployments fail when Secure Boot enabled
To manage notifications
** Changed in: maas/2.3
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
** Changed in: maas/2.3
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
I'm re-opening this. As per the previous comments, chrony indeed doesn't
work inside a container because it fails to set the time of the local
system, it crashes, and fails to start.
However, chrony should be able to run just fine inside a container even
if it cannot set the time of the local
rivate: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: andreserl dgrosvenor ltrager
> Launchpad-Bug-Reporter: Douglas (dgrosvenor)
> Launchpad-Bug-Modifier: Douglas (dgrosvenor)
> Launchpad-Message-Rationale: Subscriber (MAAS)
> Launchpad-Message-For:
pymacarrons 0.13.0 has made it into the ubuntu archive, dropping MIR for
python-libnacl.
** No longer affects: python-libnacl (Ubuntu)
** Description changed:
pymacaroons
=
1. Availability: all
2. Rationale:
macaroon is a new dependency that MAAS will use. This
Looking at the logs, I also see this:
2018-03-01 12:31:13 provisioningserver.rackdservices.tftp: [info] bootx64.efi
requested by a8:1e:84:f2:96:c5
2018-03-01 12:31:13 provisioningserver.rackdservices.tftp: [info] bootx64.efi
requested by a8:1e:84:f2:96:c5
2018-03-01 12:31:13
So in that pcap when I look at it with vim, I see things like:
¤Û^V^Fj^B^L*Å^@^C^C<9a>ons^@feature_200_final^@feature_nativedisk_cmd^@feature_timeout_style^@^@Possible
commands are:^@Possible devices are:^@Possible files are:^@Possible partitions
are:^@Possible arguments are:^@Possible things
Hi Rod,
Is this with Secure boot enabled? Could you also please attach:
Tcpdump of the pxe process for the specific MAC address.
That said, if there are other servers that boot fine in EFI mode, this, to me,
would normally indicate that there is a bug in grub itself or in the firmware.
I’m
@Rod,
MAAS doesn’t make any differentiation on what PXE interface the machine
boots on provided that we identify the MAC address and send the
configuration for it. The raw tcpdump should give us more info.
Please also attach the full console log.
--
You received this bug notification because
** Changed in: maas
Milestone: 2.4.x => 2.4.0alpha2
--
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
Actually, I think I may have spoken too soon. Lshw shows two banks of
memory:
lshw:node:
id: bank:1
claimed: true
class: memory
handle: DMI:001E
- lshw:description:
DIMM Synchronous 2400 MHz (0.4 ns)
-
So this is definitely and issue in LSHW. MAAS directly grabs the
information from there.
That said, I think it would be nice for MAAS to have an alternate method
of gathering the memory in case lshw is completely wrong as is this
case.
** Also affects: lshw (Ubuntu)
Importance: Undecided
Public bug reported:
1. Missing separators between sections
2. Organization/formatting all over the place
** Affects: maas
Importance: High
Status: Triaged
** Tags: vanilla-transition
** Tags added: vanilla-transition
** Changed in: maas (Ubuntu)
Importance: Undecided =>
I've run both manual and automated tests for Xenial and we haven't
identified any regressions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747059
Title:
sru cloud-init
** Merge proposal linked:
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/339706
** Merge proposal linked:
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/339707
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Merge proposal linked:
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/336685
** Changed in: maas (Ubuntu)
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notifi
201 - 300 of 4346 matches
Mail list logo
