Bug 1669055
| Summary: | fc29 net install stuck on grub prompt after net install on ppc64le | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michel Normand <normand> | ||||||||
| Component: | grub2 | Assignee: | Peter Jones <pjones> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | high | ||||||||||
| Version: | 29 | CC: | caleb.mccarthy, dan, dhorak, fmartine, lkundrak, michel, pjones | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | powerpc | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2019-01-28 10:31:15 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 1071880 | ||||||||||
| Attachments: |
|
||||||||||
* using "Rescue a Fedora System" was able to mount installed disk
and retrieve from /var/log the anaconda logs
* in anaconda.log there was a reported ERR about "failed to recreate path"
* in journal.log same failed action but program still return code: 0
So not sure this is the cause of failure at reboot time.
* I will attach the two logs.
=== extract anaconda.log
08:11:55,786 INF installation: Task started: Install bootloader (17/18)
08:11:55,788 INF bootloader: boot loader stage1 target device is sda1
08:11:55,788 INF bootloader: boot loader stage2 target device is sda2
08:11:55,864 DBG bootloader: new default image: <pyanaconda.bootloader.LinuxBootLoaderImage object at 0x7fff81c78e10>
08:11:55,866 ERR bootloader: failed to recreate path to default kernel image
08:11:56,148 DBG bootloader: updateNVRAMBootList: self.stage1_device.path = /dev/sda1
=== extract journal.log
Jan 24 08:11:55 localhost anaconda[3679]: anaconda: installation: Task started: Install bootloader (17/18)
Jan 24 08:11:55 localhost anaconda[3679]: anaconda: bootloader: boot loader stage1 target device is sda1
Jan 24 08:11:55 localhost anaconda[3679]: anaconda: bootloader: boot loader stage2 target device is sda2
Jan 24 08:11:55 localhost anaconda[3679]: anaconda: bootloader: new default image: <pyanaconda.bootloader.LinuxBootLoaderImage object at 0x7fff81c78e10>
Jan 24 08:11:55 localhost anaconda[3679]: anaconda: bootloader: failed to recreate path to default kernel image
Jan 24 08:11:56 localhost anaconda[3679]: anaconda: bootloader: updateNVRAMBootList: self.stage1_device.path = /dev/sda1
Jan 24 08:11:56 localhost anaconda[3679]: program: Running... nvram --print-config=boot-device
Jan 24 08:11:56 localhost audit[3667]: AVC avc: denied { read } for pid=3667 comm=746D75783A20736572766572 path="/dev/ptmx" dev="devtmpfs" ino=1106 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:ptmx_t:s0 tclass=chr_file permissive=1
Jan 24 08:11:56 localhost audit[3667]: SYSCALL arch=c0000015 syscall=145 success=yes exit=71 a0=b a1=7fffd67f14f8 a2=1 a3=3d0 items=0 ppid=1 pid=3667 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=746D75783A20736572766572 exe="/usr/bin/tmux" subj=system_u:system_r:init_t:s0 key=(null)
Jan 24 08:11:56 localhost audit: PROCTITLE proctitle=2F7573722F62696E2F746D7578002D75002D66002F7573722F73686172652F616E61636F6E64612F746D75782E636F6E66007374617274
Jan 24 08:11:56 localhost anaconda[3679]: program:
Jan 24 08:11:56 localhost anaconda[3679]: program: Return code: 0
===
Created attachment 1523042 [details]
anaconda.log
Created attachment 1523043 [details]
journal.log
There is no such problem, if trying a net install of fc28. may be same cause when trying to use fc29 Cloud qcow2, that passed with 20190122 image and failed (same grub prompt) with 20190123 image. === https://kojipkgs.fedoraproject.org/compose/cloud/Fedora-Cloud-29-20190122.0/compose/Cloud/ppc64le/images/Fedora-Cloud-Base-29-20190122.0.ppc64le.qcow2 passed https://kojipkgs.fedoraproject.org/compose/cloud/Fedora-Cloud-29-20190123.0/compose/Cloud/ppc64le/images/Fedora-Cloud-Base-29-20190123.0.ppc64le.qcow2 failed === Having the same problem installing fedora 29 through the net installer on a thinkpad T480. The text based installer appears to be broken on all systems. There doesn't seem to be any update to grub2 after the F-29 GA, but there was an update to anaconda. But the change seems completely unrelated. Created attachment 1523276 [details]
GRUB menu after netinstalling F29 via kickstart
Seeing the same kickstarting F29 on both Thinkpads and VirtualBox VMs
may be same as other bug https://bugzilla.redhat.com/show_bug.cgi?id=1669256#c0 that already pushed a correction in f29 https://bodhi.fedoraproject.org/updates/FEDORA-2019-827d700f48 problem solved with last update pushed as correction of other bug#1669256 *** This bug has been marked as a duplicate of bug 1669256 *** |
fc29 net install stuck on grub prompt after net install on ppc64le Try a net install on a ppc64le guest; the install seems to properly work in anaconda until completion, but after reboot the console is stuck at grub prompt. If I try a grub exit, a short error msg is displayed and switch back to grub. === grub menu: Reboot Exit to Open Firmware <= selected that one Use the ^ and v keys to change the selection. Press 'e' to edit the selected item, or 'c' for a command prompt. Press Escape to return to the previous menu. === W3411: Client application returned. E3406: Client application returned an error. Trying to load: from: /vdevice/v-scsi@2000/disk@8000000000000000 ... Successfully loaded Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> grub> exit grub> W3411: Client application returned. E3406: Client application returned an error. Trying to load: from: /vdevice/v-scsi@2000/disk@8000000000000000 ... Successfully loaded Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> === There was no such failure at GA time, so I assume problem related to last updates of fc29; do not know how to identify which one.