dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` We finally got an ISO produced out of last night's pungi run in Fedora 26. The bad news is that there a bunch of failures on boot and you never get a login prompt and the machine never gets an IP address so you can't access it from traditional methods. Asking colin to take a look at this.
ISO image: https://kojipkgs.fedoraproject.org/compose/branched/Fedora-26-20170315.n.0/c... ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/257
The issue: `atomic host tree in F26 does not boot properly` of project: `atomic-wg` has been assigned to `walters` by dustymabe.
miabbott added a new comment to an issue you are following: `` Booted the ISO via `virt-manager` and collected the output from the console using:
`virsh console 16 | tee console.log`
Formatting got a bit mangled, but I put the majority of it into this paste
https://paste.fedoraproject.org/paste/17KsuOmnzXqs4bfU6Thy3F5M1UNdIGYhyRLivL...
Some notable failures:
``` [[0;1;31mFAILED[0m] Failed to start Setup Virtual Console.
See 'systemctl status systemd-vconsole-setup.service' for details. ```
``` [[0;1;31mFAILED[0m] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details. ``` ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/257
chrismurphy added a new comment to an issue you are following: `` OK this seems bad
plymouth-start.service: Executing: /usr/sbin/plymouthd --mode=boot --pid-file=/var/run/plymouth/pid --attach-to-session [ 3.372107] general protection fault: 0000 [#1] SMP [ 3.372654] Modules linked in: virtio_console(+) parport snd_timer qemu_fw_cfg snd soundcore i2c_piix4 nfsd auth_rpcgss nfs_acl lockd grace 8139too qxl drm_kms_helper ttm crct10dif_pclmul crc32_pclmul crc32c_intel drm ghash_clmulni_intel serio_raw virtio_pci virtio_ring 8139cp mii virtio ata_generic pata_acpi sunrpc scsi_transport_iscsi [ 3.374009] CPU: 1 PID: 667 Comm: systemd-udevd Not tainted 4.11.0-0.rc1.git0.1.fc26.x86_64 #1 [ 3.374009] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.9.3-1.fc25 04/01/2014 [ 3.374009] task: ffffa0b875210000 task.stack: ffffaf5a40758000 [ 3.374009] RIP: 0010:vp_modern_find_vqs+0x39/0x70 [virtio_pci] [ 3.374009] RSP: 0018:ffffaf5a4075ba68 EFLAGS: 00010282 [ 3.374009] RAX: ffffaf5a403ed000 RBX: 2d306f6974726976 RCX: 0000000000000000 [ 3.374009] RDX: 00000000000000fc RSI: ffffaf5a403ed01c RDI: 0000000000000001 [ 3.374009] RBP: ffffaf5a4075ba88 R08: 000000000001c8e0 R09: ffffffff9341ea29 [ 3.374009] R10: ffffe08981dd0c40 R11: 0000000000000000 R12: ffffa0b834bda708 [ 3.374009] R13: 0000000000000000 R14: ffffa0b834bda400 R15: 000000000000001f [ 3.374009] FS: 00007fd9211438c0(0000) GS:ffffa0b87fd00000(0000) knlGS:0000000000000000 [ 3.374009] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 3.374009] CR2: 000055f2eeb94728 CR3: 000000007610c000 CR4: 00000000003406e0 [ 3.374009] Call Trace: [ 3.374009] init_vqs+0x1a0/0x2e0 [virtio_console] [ 3.374009] virtcons_probe+0xb9/0x360 [virtio_console] [ 3.374009] virtio_dev_probe+0x144/0x1e0 [virtio] [ 3.374009] driver_probe_device+0x106/0x450 [ 3.374009] __driver_attach+0xa4/0xe0 [ 3.374009] ? driver_probe_device+0x450/0x450 [ 3.374009] bus_for_each_dev+0x6e/0xb0 [ 3.374009] driver_attach+0x1e/0x20 [ 3.374009] bus_add_driver+0x1d0/0x270 [ 3.374009] ? virtio_cons_early_init+0x1d/0x1d [virtio_console] [ 3.374009] driver_register+0x60/0xe0 [ 3.374009] ? virtio_cons_early_init+0x1d/0x1d [virtio_console] [ 3.374009] register_virtio_driver+0x20/0x30 [virtio] [ 3.374009] init+0x9f/0xfe3 [virtio_console] [ 3.374009] do_one_initcall+0x50/0x1a0 [ 3.374009] ? free_hot_cold_page+0x19a/0x300 [ 3.374009] ? kmem_cache_alloc_trace+0x15f/0x1c0 [ 3.374009] ? do_init_module+0x27/0x1e6 [ 3.374009] do_init_module+0x5f/0x1e6 [ 3.374009] load_module+0x22b7/0x2820 [ 3.374009] ? __symbol_put+0x60/0x60 [ 3.374009] SYSC_init_module+0x16f/0x1a0 [ 3.374009] SyS_init_module+0xe/0x10 [ 3.374009] do_syscall_64+0x67/0x170 [ 3.374009] entry_SYSCALL64_slow_path+0x25/0x25 [ 3.374009] RIP: 0033:0x7fd91fda53da [ 3.374009] RSP: 002b:00007ffdf7f18d38 EFLAGS: 00000246 ORIG_RAX: 00000000000000af [ 3.374009] RAX: ffffffffffffffda RBX: 000055f2eeb6f6a0 RCX: 00007fd91fda53da [ 3.374009] RDX: 00007fd9208da9c5 RSI: 000000000000b37b RDI: 000055f2eeb893a0 [ 3.374009] RBP: 00007fd9208da9c5 R08: 000055f2eeb74e80 R09: 0000000000000078 [ 3.374009] R10: 00007fd92005fb00 R11: 0000000000000246 R12: 000055f2eeb893a0 [ 3.374009] R13: 000055f2eeb6c140 R14: 0000000000020000 R15: 000055f2ede5dfca [ 3.374009] Code: 54 53 49 89 fe e8 78 0d 00 00 85 c0 41 89 c5 75 44 49 8b 9e 08 03 00 00 4d 8d a6 08 03 00 00 4c 39 e3 74 31 49 8b 86 38 03 00 00 <0f> b7 7b 28 48 8d 70 16 e8 3a e6 15 d3 49 8b 86 38 03 00 00 bf [ 3.374009] RIP: vp_modern_find_vqs+0x39/0x70 [virtio_pci] RSP: ffffaf5a4075ba68 [ 3.410405] ---[ end trace a110b926d7e8d96b ]---
``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/257
dustymabe added a new comment to an issue you are following: `` more worthy information:
- I built a cloud image locally and also had the same issues on boot - I rebased from an f25 atomic host and did not see issues booting
I rebased like so:
```text [vagrant@vanilla-f25atomic ~]$ cat /etc/ostree/remotes.d/f26.conf [remote "f26"] url=https://kojipkgs.fedoraproject.org/compose/atomic/26/ gpg-verify=false [vagrant@vanilla-f25atomic ~]$ sudo rpm-ostree rebase f26:fedora/26/x86_64/atomic-host ```
I do see some failures, but was ultimately able to log in:
```text [vagrant@vanilla-f25atomic ~]$ sudo systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● systemd-vconsole-setup.service loaded failed failed Setup Virtual Console
LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. ``` ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/257
dustymabe added a new comment to an issue you are following: `` Journal output from a booted system. Removed a ton of ` Looping too fast. Throttling execution a little.` lines.
[](/atomic-wg/issue/raw/files/23eea710399690cc933296fd7d75676b0b9f791790295597c1764f8c98f0fee4-journal.removeddups.txt) ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/257
walters added a new comment to an issue you are following: `` This is because:
``` $ guestmount --ro -m /dev/atomicos/root:/ -a /srv/libvirt/images/fedora-VAGRANTSLASH-26-atomic-host-test_vagrant_box_image_0.img ~/tmp/mnt/ $ grep ^passwd: ~/tmp/mnt/ostree/deploy/fedora-atomic/deploy/31be42e470a888fc0256fa436f33e54e74e8a180e3f85b0d090e81d2a8d3416b.0/etc/nsswitch.conf passwd: sss files systemd ``` ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/257
dustymabe added a new comment to an issue you are following: `` what should it be? - should we open an issue upstream somewhere? ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/257
miabbott added a new comment to an issue you are following: ``
what should it be? - should we open an issue upstream somewhere?
F25 Atomic Host has:
``` $ grep passwd /etc/nsswitch.conf #passwd: db files nisplus nis passwd: files altfiles sss ``` ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/257
walters added a new comment to an issue you are following: `` https://github.com/projectatomic/rpm-ostree/issues/685 ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/257
dustymabe added a new comment to an issue you are following: ``
what should it be? - should we open an issue upstream somewhere?
F25 Atomic Host has: $ grep passwd /etc/nsswitch.conf #passwd: db files nisplus nis passwd: files altfiles sss
I can confirm that fixing those lines allows me to get to a login prompt. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/257
dustymabe added a new comment to an issue you are following: `` @jlebon @mattdm - this is known [bug](https://bugzilla.redhat.com/show_bug.cgi?id=1430511) - the fix is currently being pushed to stable - next image build should have fix ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/257
dustymabe added a new comment to an issue you are following: `` images now boot. closing this. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/257
The status of the issue: `atomic host tree in F26 does not boot properly` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe.
-
Chris Murphy -
Colin Walters
-
Dusty Mabe
-
Micah Abbott