Bug 2328479 - WEB Anaconda - Failure in activating thinLVM to install Fedora Rawhide (F42)
Summary: WEB Anaconda - Failure in activating thinLVM to install Fedora Rawhide (F42)
Keywords:
Status: CLOSED DUPLICATE of bug 2309350
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: anaconda-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-23 13:59 UTC by Andrea Perotti
Modified: 2024-11-27 13:43 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-11-27 13:43:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Installer log (1.43 MB, text/plain)
2024-11-23 14:05 UTC, Andrea Perotti
no flags Details

Description Andrea Perotti 2024-11-23 13:59:03 UTC
Installer WebUI Critical Error:
org.fedoraproject.Anaconda.Error: Failed to call the 'Activate' method on the '/com/redhat/lvmdbus1/ThinPool/0' object: GDBus.Error:org.freedesktop.DBus.Python.dbus.exceptions.DBusException: ('com.redhat.lvmdbus1.Lv', 'Exit code 5, stderr = Activation of logical volume vg_int/pool00 is prohibited while logical volume vg_int/pool00_tmeta is active.')

Please attach the log file /tmp/webui.log to the issue.

Reproducible: Always

Steps to Reproduce:
0. run web anaconda
1. enter storage editor
2. create a GPT partition table
3. create EFI partition
4. create boot partition (XFS)
5. create PV on remaining space
6. create a thin pool in the PV
7. create a thinLV in the pool 
8. format thinLV (XFS) and set as / mount point


Actual Results:  
System do some checks, try to activate the ThinLVM and fails in doing do

Expected Results:  
The setup is enable with no error and installation proceed

Comment 1 Andrea Perotti 2024-11-23 14:05:20 UTC
Created attachment 2059503 [details]
Installer log

Comment 2 Vojtech Trefny 2024-11-27 13:43:13 UTC

*** This bug has been marked as a duplicate of bug 2309350 ***


Note You need to log in before you can comment on or make changes to this bug.