** Changed in: maas
Importance: Critical => Undecided
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
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
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 Kernel
P
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 Kernel
Packages,
** Changed in: maas
Milestone: 2.5.0rc1 => None
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
kerne
** Tags added: track
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1743595
Title:
modprobing mlx5_core doesn't bring the interface up
Status in MAAS:
New
Status in linux package in U
Tested the 4.17 kernel, and this is the issue I now see:
[...]
[ 17.340040] raid6: sse2x1 xor() 2828 MB/s
[ 17.408036] raid6: sse2x2 gen() 7445 MB/s
[ 17.472037] raid6: sse2x2 xor() 5425 MB/s
[ 17.540032] raid6: sse2x4 gen() 10259 MB/s
[ 17.604037] raid6: sse2x4 xor() 6286
Maybe I did something wrong, but this kernel (4.18) causes a kernel
panic. The process I followed was same as always, to wget the *.deb,
dpkg -i *.deb && update-grub at the end to ensure this kernel is used:
[6.538003] evm: security.SMACK64
[6.539108] evm: security.SMACK64EXEC
[6.54038
Hi Joseph,
Sorry for such a late reply, but with all the recent business travel
I've been unable to continue working on this.
That said, now that things are calmer I can continue, however, I don't
have easy access the hardware in question and it is very time consuming
getting access to this while
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/144
Title:
Bionic 4.15.0-23-generic on ppc64 kernel panic's during
** Description changed:
- The MAAS CI has a PPC64 machine which is failing to boot into the
- ephemeral environment. Petite boot loads and kexecs 4.15.0-23-generic
- from 4.4.27-openpower1 but 4.15 panics before the initrd is loaded.
+ In the MAAS CI we test ppc64, and in the most recent runs (~fr
** Summary changed:
- 4.15.0-23-generic fails to PXE boot on PPC64
+ ppc64 4.15.0-23-generic kernel panic during PXE boot
** Summary changed:
- ppc64 4.15.0-23-generic kernel panic during PXE boot
+ Bionic 4.15.0-23-generic on ppc64 kernel panic's during PXE boot
--
You received this bug notif
*** This bug is a duplicate of bug 1768893 ***
https://bugs.launchpad.net/bugs/1768893
As such, I don't believe this is a MAAS issue.
** Changed in: maas
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
*** This bug is a duplicate of bug 1768893 ***
https://bugs.launchpad.net/bugs/1768893
After further looking into this, I can determine that:
1. Curtin installed successfully despite the kernel issues
1. Curtin told MAAS the installation completed successfully.
3. cloud-init told the machine
@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
@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
@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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772490
Title:
bcache: register_bcache() err
** 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
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
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
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
** Changed in: maas
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772490
Title:
bcache: register_bcache() error
Status in curtin:
New
Status in
@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...
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
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
This issue is not present in Artful. This issue is only present in
Bionic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761796
Title:
Rebooting bionic fails with hardware error on Pro
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 envir
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 Bio
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761796
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761796
Title:
Rebooting bionic fail
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761796
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
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 Kernel
Packages, which is subscribed to linux in 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
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 Kernel
Packages, which is subscribed to linux in 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761796
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 hardwa
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761796
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 's
** 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:
+ https://pastebin.ubuntu.com/p/hyD6VY
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...
[
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1742324
Title:
Bionic
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
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
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743595/+attachment/5037964/+files/uname-a.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/174
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743595/+attachment/5037965/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/174
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743595/+attachment/5037963/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743595/+attachment/5037962/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1743595
Public bug reported:
ubuntu@wrlsrvr321:~$ sudo -i
root@wrlsrvr321:~# lsmod
Module Size Used by
ipmi_devintf 20480 0
iscsi_tcp 20480 0
libiscsi_tcp 24576 1 iscsi_tcp
libiscsi 53248 2 libiscsi_tcp,iscsi_tcp
scsi_transport_iscsi
Hi Dimitrii,
This request seems like something we have never seen before. This
doesn't seem to be quite a complex thing to do. Right now, this is and
never has been in our plans to implement. This is also something that
has never come up before.
I'm going to mark this as a wishlist, and incomplet
@Tyler,
The reason why this wasn't seen before is that previously in Xenial,
cloud-init did not restart 'ntp' with a new config file. Since cloud-
init recently SRU'd a fixed cloud-init that does restart 'ntp' on
overlay, the issue started to show up.
In other words, after a cloud-init bugfix , t
@Frode,
Users running 2.2 *already* have the apparmor=0 work around for
*ephemeral* environments only.
For users running previous versions, we recommend you upgrade
immediately, provided that 2.0 and 2.1 are out of support. If you decide
not to upgrade, your options are:
1. Use a HWE kernel (suc
When using the following kernel (the default Xenial kernel, aka ga-16.04
in MAAS), we see this issue:
4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
When using the HWE kernel (aka hwe-16.04 in MAAS), we do NOT see this
issue:
4.8.0-58-generic #63~16.
@Tyler,
That's is correct, MAAS 2.2.0+ sends the apparmor=0 for the ephemeral
environments.
That said, however, this affects else who is not using 2.2 (which in
fact, affects customers who are still in 2.1). Also, based on my
testing, it seems that when using hwe-16.04 kernel this doesn't happen,
It seems that this only happens when using ga-16.04 and doesn't when
using hwe-16.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1701297
Title:
NTP reload failure (causing deployment
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu)
Importance: Undecided => Critical
--
Ok, I confirm the issue as per previous comment with Trusty+hwe-x
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1618572
Title:
apt-key add fails in overlayfs
Status in cloud-init:
Co
This may be related to https://bugs.launchpad.net/cloud-
init/+bug/1618572 .
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1620525
Title:
sbuild with overlayfs fails in yakkety
Status
Hi All,
I have come across what seems to be a related issue across the board. This is
not exactly the same way to reproduce but a simple 'apt-get update' shows this:
In Yakkety: http://pastebin.ubuntu.com/23149838/ on 4.4.0-9136-generic
In Xenial: http://pastebin.ubuntu.com/23149864/
Trusty sim
Don't think it matters, but:
http://pastebin.ubuntu.com/23119431/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1618572
Title:
cloud-init failing to configure sources and additional rep
*** This bug is a duplicate of bug 1563779 ***
https://bugs.launchpad.net/bugs/1563779
my guess is that a new kernel or a new package has hit xenial, and that
is causing the kernel to panic. THe maas images automatically use newest
stuff on the archives.
** Also affects: maas-images
Import
** No longer affects: maas
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1499869
Title:
maas wily deployment to HP Proliant m400 arm64 server cartridge fails
Status in cloud-init:
Co
I think the priority of this should be raised as the importance of this
being fixed is quite high!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1464442
Title:
installing or upgrading l
Hi David!
Yes this is targeted for 14.04.
Cheers.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1210393
Title:
MAAS ipmi fails on OCPv3 Roadrunner
Status in MAAS:
Triaged
Status in
** Changed in: maas
Assignee: Andres Rodriguez (andreserl) => Jason Hobbs (jason-hobbs)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1210393
Title:
MAAS ipmi fails on OC
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1210393
Title:
MAAS ipmi fails on OCPv3 Roadrunner
Sta
79 matches
Mail list logo
