Bug 1954149

Summary: pyanaconda.modules.common.errors.installation.BootloaderInstallationError: Could not get stage2 filesystem UUID
Product: [Fedora] Fedora Reporter: Be <be.0>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: anaconda-maint-list, bootloader-eng-team, carl, deekej, javierm, jonathan, kellin, mb+fedora, ngompa13, vanmeeuwen+fedora, vponcova, vtrefny, w
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:77acba9a2e9b0e30243534acca53b886dcf7685a2c27021eedf0dd8943ac0e75;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-07 20:05:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: anaconda-tb
none
File: anaconda.log
none
File: dbus.log
none
File: environ
none
File: journalctl
none
File: lsblk_output
none
File: lvm.log
none
File: nmcli_dev_list
none
File: os_info
none
File: program.log
none
File: storage.log
none
File: packaging.log
none
Anaconda log files from failed BTRFS on /boot installation none

Description Be 2021-04-27 16:55:20 UTC
Description of problem:
installing Fedora 34 with btrfs for /boot

Version-Release number of selected component:
anaconda-core-34.24.9-1.fc34.x86_64

The following was filed automatically by anaconda:
anaconda 34.24.9 exception report
Traceback (most recent call first):
  File "/usr/lib/python3.9/site-packages/dasbus/client/handler.py", line 497, in _handle_method_error
    raise exception from None
  File "/usr/lib/python3.9/site-packages/dasbus/client/handler.py", line 477, in _get_method_reply
    return self._handle_method_error(error)
  File "/usr/lib/python3.9/site-packages/dasbus/client/handler.py", line 444, in _call_method
    return self._get_method_reply(
  File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/common/task/__init__.py", line 46, in sync_run_task
    task_proxy.Finish()
  File "/usr/lib64/python3.9/site-packages/pyanaconda/installation.py", line 322, in run_install_bootloader
    sync_run_task(STORAGE.get_proxy(task))
  File "/usr/lib64/python3.9/site-packages/pyanaconda/installation_tasks.py", line 458, in run_task
    self._task(*self._task_args, **self._task_kwargs)
  File "/usr/lib64/python3.9/site-packages/pyanaconda/installation_tasks.py", line 496, in start
    self.run_task()
  File "/usr/lib64/python3.9/site-packages/pyanaconda/installation_tasks.py", line 311, in start
    item.start()
  File "/usr/lib64/python3.9/site-packages/pyanaconda/installation_tasks.py", line 311, in start
    item.start()
  File "/usr/lib64/python3.9/site-packages/pyanaconda/installation_tasks.py", line 311, in start
    item.start()
  File "/usr/lib64/python3.9/site-packages/pyanaconda/installation.py", line 372, in run_installation
    queue.start()
  File "/usr/lib64/python3.9/threading.py", line 892, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.9/site-packages/pyanaconda/threading.py", line 275, in run
    threading.Thread.run(self)
pyanaconda.modules.common.errors.installation.BootloaderInstallationError: Could not get stage2 filesystem UUID

Additional info:
addons:         com_redhat_kdump
cmdline:        /usr/bin/python3  /sbin/anaconda --liveinst --graphical
cmdline_file:   BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-34-1-2 rd.live.image quiet
dnf.librepo.log: 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         5.11.12-300.fc34.x86_64
other involved packages: python3-libs-3.9.2-1.fc34.x86_64, python3-dasbus-1.4-3.fc34.noarch
product:        Fedora
release:        Fedora release 34 (Thirty Four)
type:           anaconda
version:        34

Comment 1 Be 2021-04-27 16:55:24 UTC
Created attachment 1776090 [details]
File: anaconda-tb

Comment 2 Be 2021-04-27 16:55:26 UTC
Created attachment 1776091 [details]
File: anaconda.log

Comment 3 Be 2021-04-27 16:55:27 UTC
Created attachment 1776092 [details]
File: dbus.log

Comment 4 Be 2021-04-27 16:55:27 UTC
Created attachment 1776093 [details]
File: environ

Comment 5 Be 2021-04-27 16:55:30 UTC
Created attachment 1776094 [details]
File: journalctl

Comment 6 Be 2021-04-27 16:55:31 UTC
Created attachment 1776095 [details]
File: lsblk_output

Comment 7 Be 2021-04-27 16:55:33 UTC
Created attachment 1776096 [details]
File: lvm.log

Comment 8 Be 2021-04-27 16:55:34 UTC
Created attachment 1776097 [details]
File: nmcli_dev_list

Comment 9 Be 2021-04-27 16:55:35 UTC
Created attachment 1776098 [details]
File: os_info

Comment 10 Be 2021-04-27 16:55:36 UTC
Created attachment 1776099 [details]
File: program.log

Comment 11 Be 2021-04-27 16:55:37 UTC
Created attachment 1776100 [details]
File: storage.log

Comment 12 Be 2021-04-27 16:55:38 UTC
Created attachment 1776101 [details]
File: packaging.log

Comment 13 mb+fedora 2021-05-09 08:37:18 UTC
I've tripped up on this, too, on aarch64.

In case it's useful, I think it's a regression as I got a working image with F34 in its pre-release state in March (9th I think).

Comment 14 Vendula Poncova 2021-05-10 11:19:45 UTC
It seems to be related to this change: https://github.com/rhinstaller/anaconda/commit/2efdec8

Javier, could you look at this please?

Comment 15 Vendula Poncova 2021-05-10 11:20:47 UTC
Vojta, could you help us with this fix, please?

Comment 16 Carl George 🎩 2021-07-10 03:28:04 UTC
I hit the same error while trying to set up a system without a separate /boot partition, specifically with these volumes:

- /boot/efi (efi system partition)
- / (btrfs subvolume)
- /home (btrfs subvolume)

Comment 17 Vendula Poncova 2021-07-16 15:01:33 UTC
Hi, I am not able to reproduce the error. Could someone provide the steps to reproduce, please?

Comment 18 David Kaferad // Dee'Kej 2021-07-20 13:56:18 UTC
Created attachment 1803758 [details]
Anaconda log files from failed BTRFS on /boot installation

I've hit the same problem as described by the reporter. Here's the kickstart file that has triggered the issue for me:
* https://github.com/deekej/fedora-kickstart/blob/bz1954149/fedora-kickstart.ks

I'm attaching the log files from the failed installation, hopefully, this helps. :)

NOTE: If you are trying to reproduce this with the kickstart file above, then I suggest reducing the number of package groups used in the installation to speed it up. Otherwise, you'll be waiting quite some time. :)

Comment 19 Ben Cotton 2022-05-12 14:57:31 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 20 Ben Cotton 2022-06-07 20:05:07 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 21 Red Hat Bugzilla 2023-09-15 01:33:47 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days