Hi all,
The current F25 Atomic images are failing to boot[1], I never managed to reach dracut emergency shell in my local box.
Can anyone else also please have a look?
[1] https://apps.fedoraproject.org/autocloud/jobs/704/output
Kushal
On Wed, Sep 28, 2016 at 9:26 PM, Kushal Das mail@kushaldas.in wrote:
Hi all,
The current F25 Atomic images are failing to boot[1], I never managed to reach dracut emergency shell in my local box.
Can anyone else also please have a look?
[1] https://apps.fedoraproject.org/autocloud/jobs/704/output
All the Fedora 25 Atomic images: qcow2, vagrant-libvirt, vagrant-virtualbox are failing to boot.
On 10/03/2016 02:47 AM, Trishna Guha wrote:
On Wed, Sep 28, 2016 at 9:26 PM, Kushal Das mail@kushaldas.in wrote:
Hi all,
The current F25 Atomic images are failing to boot[1], I never managed to reach dracut emergency shell in my local box.
Can anyone else also please have a look?
[1] https://apps.fedoraproject.org/autocloud/jobs/704/output
All the Fedora 25 Atomic images: qcow2, vagrant-libvirt, vagrant-virtualbox are failing to boot.
There is a kernel panic happening early in boot. Here is the serial console log from one of those boots:
https://paste.fedoraproject.org/442720/14755209/
Dusty
On Mon, Oct 3, 2016, at 02:57 PM, Dusty Mabe wrote:
There is a kernel panic happening early in boot. Here is the serial console log from one of those boots:
On 10/03/2016 03:06 PM, Colin Walters wrote:
On Mon, Oct 3, 2016, at 02:57 PM, Dusty Mabe wrote:
There is a kernel panic happening early in boot. Here is the serial console log from one of those boots:
Thanks Colin
On Mon, Oct 3, 2016 at 1:06 PM, Colin Walters walters@verbum.org wrote:
On Mon, Oct 3, 2016, at 02:57 PM, Dusty Mabe wrote:
There is a kernel panic happening early in boot. Here is the serial console log from one of those boots:
Does this need to be marked as a freeze exception to back the change out for beta candidate images to work?
On Monday, October 3, 2016 1:16:04 PM CDT Chris Murphy wrote:
On Mon, Oct 3, 2016 at 1:06 PM, Colin Walters walters@verbum.org wrote:
On Mon, Oct 3, 2016, at 02:57 PM, Dusty Mabe wrote:
There is a kernel panic happening early in boot. Here is the serial
console log from one of those boots:
Does this need to be marked as a freeze exception to back the change out for beta candidate images to work?
No it does not. Atomic is not a release deliverable anymore.
Dennis
On 10/03/2016 02:57 PM, Dusty Mabe wrote:
On 10/03/2016 02:47 AM, Trishna Guha wrote:
On Wed, Sep 28, 2016 at 9:26 PM, Kushal Das mail@kushaldas.in wrote:
Hi all,
The current F25 Atomic images are failing to boot[1], I never managed to reach dracut emergency shell in my local box.
Can anyone else also please have a look?
[1] https://apps.fedoraproject.org/autocloud/jobs/704/output
All the Fedora 25 Atomic images: qcow2, vagrant-libvirt, vagrant-virtualbox are failing to boot.
There is a kernel panic happening early in boot. Here is the serial console log from one of those boots:
Interesting thing to note from the atomic host's kernel log:
``` [ 1.805434] x86/mm: Checked W+X mappings: passed, no W+X pages found. Fatal: no entropy gathering module detected [ 1.820475] traps: init[1] general protection ip:7f544fd74652 sp:7fff58acd720 error:0 in libc-2.24.so[7f544fd3d000+1bd000] [ 1.823822] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ```
Where the Fedora cloud base image (boots fine) has this:
``` [ 0.793666] x86/mm: Checked W+X mappings: passed, no W+X pages found. [ 0.799823] random: systemd: uninitialized urandom read (16 bytes read) [ 0.800433] random: systemd: uninitialized urandom read (16 bytes read) [ 0.800446] random: systemd: uninitialized urandom read (16 bytes read) [ 0.811359] systemd[1]: systemd 231 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN) ```
Looks like there is some problem with generating/obtaining random data on boot for Atomic Host.
Dusty
Just an update on this. We're passed the kernel panic issue now that dracut-fips was backed out, but we're now getting a reboot loop due to:
https://bugzilla.redhat.com/show_bug.cgi?id=1290659
----- Original Message -----
On 10/03/2016 02:47 AM, Trishna Guha wrote:
On Wed, Sep 28, 2016 at 9:26 PM, Kushal Das mail@kushaldas.in wrote:
Hi all,
The current F25 Atomic images are failing to boot[1], I never managed to reach dracut emergency shell in my local box.
Can anyone else also please have a look?
[1] https://apps.fedoraproject.org/autocloud/jobs/704/output
All the Fedora 25 Atomic images: qcow2, vagrant-libvirt, vagrant-virtualbox are failing to boot.
There is a kernel panic happening early in boot. Here is the serial console log from one of those boots:
https://paste.fedoraproject.org/442720/14755209/
Dusty _______________________________________________ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-leave@lists.fedoraproject.org
On 10/04/2016 03:52 PM, Jonathan Lebon wrote:
Just an update on this. We're passed the kernel panic issue now that dracut-fips was backed out, but we're now getting a reboot loop due to:
Fun stuff. Thanks for digging into this!
-
Chris Murphy -
Colin Walters -
Dennis Gilmore -
Dusty Mabe -
Jonathan Lebon -
Kushal Das -
Trishna Guha