Public bug reported:
On a deploy of kubernetes, we're seeing a machine have issues with its
tg3 driven nics.
We see:
Dec 14 07:44:08 juju-fcf29c-0-lxd-1 kernel: [ 1496.772960] tg3
:02:00.1 eth1: transmit timed out, resetting
Around that time, we have issues with services losing network
conn
@ Ryan we do not test Xenial or Disco
On Thu, Aug 22, 2019 at 7:41 PM Ryan Harper <1784...@bugs.launchpad.net>
wrote:
> Finally, I did verify xenial proposed with our original test. I had
> over 100 installs with no issue.
>
> @Jason
>
> Have you had any runs on Xenial or Disco? (or do you not
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => New
--
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/1784665
Title:
bcache: bch_allocator_thread(): hung task timeout
** Attachment added: "spinda.maas-curtin_config.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5284072/+files/spinda.maas-curtin_config.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
We're still seeing a bcache timeout failure during curtin install
2019-08-22T10:16:40+00:00 spinda
cloud-init[1604]: finish:
cmd-install/stage-partitioning/builtin/cmd-block-meta/clear-holders: FAIL:
removing previous storage devices
2019-08-22T10:16:40+00:00 spinda cloud-init[1604]:
This is difficult for us to test in our lab because we are using MAAS, and
we hit this during MAAS deployments of nodes, so we would need MAAS images
built with these kernels. Additionally, this doesn't reproduce every time,
it is maybe 1/4 test runs. It may be best to find a way to reproduce this
** Tags added: cdo-qa foundations-engine
--
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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
New
This occurrs on a target machine during maas install. Apport is not
collected in this case.
** 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
@Christian
- release: bionic
- seabios: 1.10.2-1ubuntu1
- qemu: 1:2.11+dfsg-1ubuntu7.10
- libvirt: 4.0.0-1ubuntu8.8
- ovmf - this is a uefi thing right? we're not using it.
- kernel 2019-03-18T12:17:11+00:00 elastic-2 kernel: [0.00]
Linux version 4.15.0-46-generic (buildd@lgw01-amd64-038)
Bumped to field-high as we ran into this again in testing.
We have a workaround, but it's to not use 2G VM's, which is really silly
and hard to remember when we go and add new deployments, especially
because the failure mode is not obvious at all.
--
You received this bug notification because yo
This happens only sporadically. If it happens, is there some keyboard
sequence I can use to dump more information, or is the system totally
frozen at this point?
Jason
On Sat, Mar 16, 2019 at 11:35 AM Kai-Heng Feng
wrote:
> Would it be possible to get earlier trace?
>
> --
> You received this b
I can't get logs from the system because it's kernel panic'd.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
Public bug reported:
A machine in our test lab kernel panic'd during PXE boot from MAAS.
It was running 4.15.0-46-generic #49-Ubuntu
I've attached a screenshot of the call trace.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: cdo-qa foundations-engine
**
*** This bug is a duplicate of bug 1768893 ***
https://bugs.launchpad.net/bugs/1768893
** This bug has been marked a duplicate of bug 1768893
installation on several nodes failed with errors relating to dmsetup remove
of ceph devices.
--
You received this bug notification because you are
After updating firmware on the servers, we can't reproduce it at all
anymore.
--
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/1759445
Title:
kernel panic when trying to reboot in bionic
So far we've only been able to produce this by doing bionic deploys.
One thing that stands out in the rsyslog for bionic deploys is this
failure:
http://paste.ubuntu.com/p/y8xXc7PYjp/
Apr 2 17:48:35 leafeon blkdeactivate[1782]: /sbin/blkdeactivate: line
345: /bin/sort: No such file or directory
We reproduced it again... looking to try the testing now.
--
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/1759445
Title:
kernel panic when trying to reboot in bionic
Status in MAAS:
In
We can no longer reproduce this.
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => 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/1759445
Title:
kernel panic whe
** Tags added: foundations-engine
--
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/1759445
Title:
kernel panic when trying to reboot in bionic
Status in MAAS:
Invalid
Status in linux pa
This bug is a kernel panic when rebooting at the end of a MAAS
deployment of bionic; there is no way to run apport-collect.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- Bionic due to kernel panic
+ kernel panic when trying to reboot in bionic
--
Yo
@james-page When will the 2.8.1 release be?
--
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/1742505
Title:
gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
Status in
Testing on arm64, the workaround of adding xenial-proposed via maas
doesn't work - the newer ubuntu-fan package isn't being installed
http://paste.ubuntu.com/26178859/
I don't know how that can be, since the repo is being added (or should
be added) before juju installs ubuntu-fan.
--
You receiv
I just tested this also and can verify it fixed it in the
environment/test where it was originally reported as broken.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1737640
Title:
y up
using either 4.4.0-59-generic #80 or 4.4.0-62-generic #83, and haven't gone
offline yet from the "cat /dev/urandom > /dev/sdb" test. I will leave them
running over night.
On Mon, Jan 30, 2017 at 6:51 PM, Jason Hobbs
wrote:
> So, I appear to have spoken too soon on ex
PM, Jason Hobbs
wrote:
> We found testing with the latest Xenial kernel (4.4.0.62.65) from
> https://launchpad.net/~canonical-kernel-
> team/+archive/ubuntu/ppa/+build/11278866 fixes this issue - no firmware
> updates required. We did also test with just the latest firmware
> upda
We found testing with the latest Xenial kernel (4.4.0.62.65) from
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/11278866 fixes this issue - no firmware
updates required. We did also test with just the latest firmware
updates, and that did not fix the issue. Latest firmwa
** Description changed:
I'm using MAAS to enable the following kernel flags on install/boot:
iommu=pt intel_iommu=on
in order to be able to passthrough SR-IOV VF functions to KVM guess;
however when these options are enabled, the servers fail to install (see
attached screenshot).
** Tags added: oil
--
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:
Confirmed
Status in linux package in Ubuntu:
Co
Steve's suggested work around:
> # dpkg-divert --rename --add /sbin/telinit
> # cat > /sbin/telinit
> #!/bin/sh
> exit 0
> ^D
> # apt-get install [...]
> # dpkg-divert --rename --remove /sbin/telinit
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
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/1444003
Title:
BUG: soft lockup - CPU#6 stuck for 22s! [systemd-udevd:166]
Hey,
I also have this problem with my HP Stream 11.
Happy to help out in anyway.
Basically the touchpad works, but it seems to stop working after using
the keyboard, or clicking/tapping.. yet the cursor still can move about
no matter what. Changing the settings in the system control panel does
I don't believe there are plans to fix this against Saucy.
** Changed in: linux (Ubuntu Saucy)
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/1210393
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: opencompute
Status: Confirmed => Fix Released
--
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/12
Private bug reported:
please ignore for now - filling out details in a minute
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Public to Private
--
You received this bug notification because you are a member of Kernel
Packages, which i
** Changed in: maas
Assignee: David Duffey (david-duffey) => 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
** Tags added: server-hwe
--
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:
Fix Committed
Status in Open Compute Projec
** Tags added: server-hwe
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to cpu-checker in Ubuntu.
https://bugs.launchpad.net/bugs/1282329
Title:
juju requires cpu-checker which is unavailable on arm64/ppc64el
Status in juju-core:
Inva
Hey Dustin - I reassigned to David since I'm not sure who will be
testing it. David/Samantha/Rod - please reassign to whoever is doing
the test!
** Changed in: maas
Status: Triaged => In Progress
** Changed in: maas
Assignee: Jason Hobbs (jason-hobbs) => David Duffey (d
Cool David - let me know how it works out. The branch is otherwise
complete/reviewed and ready to land.
--
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 O
I've posted a branch with a fix to lp:~jason-hobbs/maas/lp-1210393
I've manually tested this, but for lack of access, not on OCPv3
Roadrunner.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
** Branch linked: lp:~jason-hobbs/maas/lp-1210393
--
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
Milestone: None => 14.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/1210393
Title:
MAAS ipmi fails on OCPv3 Roadrunner
Status in MAAS:
Triaged
Status in Op
I've started work on a patch to fix this. It will find either an
existing maas user, or will find the first disabled user with an empty
username. If it can't find either it will bail and give up on automatic
IPMI config.
--
You received this bug notification because you are a member of Kernel
Pac
43 matches
Mail list logo
