Bug 1869143 - failed to reset the name of root partition
Summary: failed to reset the name of root partition
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-17 04:48 UTC by lnie
Modified: 2021-11-30 16:21 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-11-30 16:21:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda.tar (236.31 KB, application/gzip)
2020-08-17 04:48 UTC, lnie
no flags Details
screencast (242.83 KB, video/webm)
2020-08-17 04:50 UTC, lnie
no flags Details
anaconda log (58.67 KB, text/plain)
2020-08-17 04:51 UTC, lnie
no flags Details
storage.log (828.58 KB, text/plain)
2020-08-17 04:51 UTC, lnie
no flags Details

Description lnie 2020-08-17 04:48:25 UTC
Created attachment 1711538 [details]
anaconda.tar

Description of problem:
As shown in the attached screencast,try to reset the name of root partition(created by click"+" or "Click here to create them automatically") but failed.

Version-Release number of selected component (if applicable):
Fedora-Server-x86_64-Rawhide-20200811.n.0

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 lnie 2020-08-17 04:50:48 UTC
Created attachment 1711539 [details]
screencast

Comment 2 lnie 2020-08-17 04:51:19 UTC
Created attachment 1711540 [details]
anaconda log

Comment 3 lnie 2020-08-17 04:51:49 UTC
Created attachment 1711541 [details]
storage.log

Comment 4 Vladimír Slávik 2020-08-21 16:19:10 UTC
What I see in logs is that somehow the device is present, then hidden, and as the storage is later being created, it is missing.

The inconsistent "incomplete" is interesting.

INFO:blivet:type detected on 'sda2' is 'lvmpv'
DEBUG:blivet:                        LVMPhysicalVolume.__init__: uuid: um1sQX-2Nx9-XEeV-BnOd-wZrh-LkEO-QXSRpK ; label: None ; device: /dev/sda2 ; serial: 3600508b1001c451e3a456a9432498336 ; exists: True ; vg_name: fedora_storageqe-16 ; vg_uuid: Fv7EmD-T5EG-zKNO-YOVN-yn0y-ljOV-A72tUn ; pe_start: 1024 KiB ;
DEBUG:blivet:get_format('lvmpv') returning LVMPhysicalVolume instance with object id 32
DEBUG:blivet:                         PartitionDevice._set_format: sda2 ; type: lvmpv ; current: None ;
DEBUG:blivet:                       DeviceTree.get_device_by_uuid: uuid: Fv7EmD-T5EG-zKNO-YOVN-yn0y-ljOV-A72tUn ; incomplete: True ; hidden: False ;
DEBUG:blivet:                       DeviceTree.get_device_by_uuid returned None
DEBUG:blivet:                       DeviceTree.get_device_by_name: name: fedora_storageqe-16 ; incomplete: False ; hidden: False ;
DEBUG:blivet:                       DeviceTree.get_device_by_name returned None
INFO:blivet:Can't get exported information from VG info, assuming VG is not exported.

(...)

INFO:blivet:hiding device existing 77.32 GiB lvmlv fedora_storageqe-16-root (1927) with existing xfs filesystem
DEBUG:blivet:                                   LVMVolumeGroupDevice.remove_child: name: fedora_storageqe-16 ; child: root ; kids: 1 ;
INFO:blivet:removed lvmlv fedora_storageqe-16-root (id 1927) from device tree
DEBUG:blivet:lvm filter: adding fedora_storageqe-16-root to the reject list
INFO:blivet:hiding device existing 77.32 GiB lvmvg fedora_storageqe-16 (33)
DEBUG:blivet:                                PartitionDevice.remove_child: name: sda2 ; child: fedora_storageqe-16 ; kids: 1 ;
DEBUG:blivet:                                PartitionDevice.remove_child: name: mpatha1 ; child: fedora_storageqe-16 ; kids: 1 ;
INFO:blivet:removed lvmvg fedora_storageqe-16 (id 33) from device tree
DEBUG:blivet:lvm filter: adding fedora_storageqe-16 to the reject list
INFO:blivet:hiding device existing 10 GiB partition mpatha1 (1918) with existing lvmpv
DEBUG:blivet:                              MultipathDevice.remove_child: name: mpatha ; child: mpatha1 ; kids: 1 ;
INFO:blivet:removed partition mpatha1 (id 1918) from device tree
DEBUG:blivet:lvm filter: adding mpatha1 to the reject list
INFO:blivet:hiding device existing 10 GiB dm-multipath mpatha (1908) with existing msdos disklabel
DEBUG:blivet:                          FcoeDiskDevice.remove_child: name: sdb ; child: mpatha ; kids: 1 ;
DEBUG:blivet:                          FcoeDiskDevice.remove_child: name: sdc ; child: mpatha ; kids: 1 ;
INFO:blivet:removed dm-multipath mpatha (id 1908) from device tree
DEBUG:blivet:lvm filter: adding mpatha to the reject list

(...)
INFO:blivet:executing action: [2090] destroy format xfs filesystem on lvmlv fedora_storageqe-16-root (id 1927)
DEBUG:blivet:                  LVMLogicalVolumeDevice.setup: fedora_storageqe-16-root ; orig: True ; status: False ; controllable: True ;
DEBUG:blivet:                          LVMLogicalVolumeDevice.setup_parents: name: fedora_storageqe-16-root ; orig: True ;
DEBUG:blivet:                            LVMVolumeGroupDevice.setup: fedora_storageqe-16 ; orig: True ; status: False ; controllable: True ;
DEBUG:blivet:                                  LVMVolumeGroupDevice.setup_parents: name: fedora_storageqe-16 ; orig: True ;
DEBUG:blivet:                                    PartitionDevice.setup: sda2 ; orig: True ; status: True ; controllable: True ;
DEBUG:blivet:                                    LVMPhysicalVolume.setup: device: /dev/sda2 ; type: lvmpv ; status: False ;
DEBUG:blivet:                                    PartitionDevice.setup: mpatha1 ; orig: True ; status: True ; controllable: True ;
DEBUG:blivet:                                    LVMPhysicalVolume.setup: device: /dev/mapper/mpatha1 ; type: lvmpv ; status: False ;
INFO:program:Running... udevadm settle --timeout=300
DEBUG:program:Return code: 0
DEBUG:blivet:                                LVMVolumeGroupDevice.update_sysfs_path: fedora_storageqe-16 ; status: False ;
DEBUG:blivet:                    LVMLogicalVolumeDevice._setup: fedora_storageqe-16-root ; orig: True ; status: False ; controllable: True ;
INFO:program:[48] Calling the 'com.redhat.lvmdbus1.Lv.Activate' method on the '/com/redhat/lvmdbus1/Lv/1' object with the following parameters: '(0, 1, {'-K': <''>, '--config': <' devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] filter=["r|/fedora_storageqe-16-root$|","r|/mpatha1$|","r|/mpatha$|"] } log {level=7 file=/tmp/lvm.log syslog=0}'>})'
INFO:program:[48] Done.
INFO:program:[48] Got error: Failed to call the 'Activate' method on the '/com/redhat/lvmdbus1/Lv/1' object: GDBus.Error:org.freedesktop.DBus.Python.dbus.exceptions.DBusException: ('com.redhat.lvmdbus1.Lv', "Exit code 5, stderr =   WARNING: Couldn't find device with uuid P4zhZE-cB1u-gkjd-gIWa-GPRx-CkG7-5h2E8n.\n  WARNING: VG fedora_storageqe-16 is missing PV P4zhZE-cB1u-gkjd-gIWa-GPRx-CkG7-5h2E8n (last written to /dev/mapper/mpatha1).\n  Refusing activation of partial LV fedora_storageqe-16/root.  Use '--activationmode partial' to override.\n")

(...)

gi.overrides.BlockDev.LVMError: Failed to call the 'Activate' method on the '/com/redhat/lvmdbus1/Lv/1' object: GDBus.Error:org.freedesktop.DBus.Python.dbus.exceptions.DBusException: ('com.redhat.lvmdbus1.Lv', "Exit code 5, stderr =   WARNING: Couldn't find device with uuid P4zhZE-cB1u-gkjd-gIWa-GPRx-CkG7-5h2E8n.\n  WARNING: VG fedora_storageqe-16 is missing PV P4zhZE-cB1u-gkjd-gIWa-GPRx-CkG7-5h2E8n (last written to /dev/mapper/mpatha1).\n  Refusing activation of partial LV fedora_storageqe-16/root.  Use '--activationmode partial' to override.\n")

Comment 5 Vladimír Slávik 2020-08-21 16:36:22 UTC
Inie, thank you for the report. Did you repeat this one (not saying you must, just asking!), and if not, are you sure the hardware is ok? Were there any additional steps before you got this? Did the machine have more disks in some earlier attempts? The incomplete VG hints at something like that.

I cannot exactly reproduce this using 33.25, even though I found plenty other broken things :-/

Comment 6 Ben Cotton 2021-11-04 17:34:24 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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
Fedora 'version' of '33'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Ben Cotton 2021-11-30 16:21:28 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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. If you experience problems, please add a comment to this
bug.

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


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