fozzie works with the proposed Artful kernel in this cycle. Closing this bug.
4.13.0-38.43
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu Artful)
Status: Triaged => 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/1755149
Title:
Artful i386 with MaaS deployment will bump into kernel panic issue
(4.13.0-36)
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Artful:
Invalid
Bug description:
This issue was only spotted with a specific HW, node "fozzie" Dell
PowerEdge R320, in our test pool. Other nodes like onibi (Dell
PowerEdge R310), gonzo (Dell PowerEdge R415), pepe (Dell PowerEdge
R310), onza (Dell PowerEdge R310) they don't have such issue.
Steps:
1. Deploy the system with i386 Artful, with a SRU regression-testing job on
jenkins.
Result:
* The deployment task will fail, from the virtual console you will see
kernel panic error message
The deployment will stuck here after the "Rebooting for dist-upgrade" task:
+ /var/lib/jenkins/kernel-testing/metal --debug --nc --series=artful
--arch=i386 --flavour=generic --required-kernel-version=4.13.0-37.42
--pkg-name=None fozzie
. Provisioner setup
Releasing...
Allocating...
Deploying...
Deployed
. Fixup /etc/hosts
. Remove /etc/apt/apt.conf.d/90curtin-aptproxy
. Enabling Proposed
. Enabling Src
. for the pure love of rebooting
. Disabling Periodic APT Updates
. Installing python-minimal
. Installing Required Packages
. Dist Upgrade
. Rebooting for dist-upgrade
Build was aborted
Here is the MaaS deployment log:
https://pastebin.canonical.com/p/PhqxJCmDdw/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755149/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
