RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1961739 - Kickstart installations fail when a previous installation contains an lvm snapshot
Summary: Kickstart installations fail when a previous installation contains an lvm sna...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: python-blivet
Version: 8.3
Hardware: x86_64
OS: Linux
high
high
Target Milestone: beta
: ---
Assignee: Vojtech Trefny
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-18 15:35 UTC by jcastran
Modified: 2024-12-20 20:04 UTC (History)
3 users (show)

Fixed In Version: python-blivet-3.4.0-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 18:49:19 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 6268441 0 None None None 2021-08-18 14:15:16 UTC
Red Hat Product Errata RHBA-2021:4297 0 None None None 2021-11-09 18:49:35 UTC

Comment 1 Jan Stodola 2021-05-19 05:43:42 UTC 
Reproduced also on RHEL-8.4 with the following partitioning in the kickstart file:

bootloader --location=mbr
zerombr
clearpart --all --initlabel
autopart
Comment 3 Jan Stodola 2021-05-19 06:13:06 UTC 
Also reproducible on RHEL-9, bug 1961944.
Comment 4 Vojtech Trefny 2021-05-20 11:57:42 UTC 
upstream PR: https://github.com/storaged-project/blivet/pull/958

updates image for 8.5: http://file.emea.redhat.com/~vtrefny/img/rhbz1961739.img
Comment 5 Marta Lewandowska 2021-06-30 14:07:33 UTC 
Tested using compose RHEL-8.5.0-20210626.d.0 (python3-blivet-3.4.0-1.el8) and problem is still occurring.
In graphical installation, once storage configuration starts, a window pops up saying "An error occurred while activating your storage configuration" "device path does not exist or is not writable". 

from storage.log:

INFO:blivet:executing action: [226] destroy format xfs filesystem on lvmsnapshot vg_test-snap (id 85)
INFO:program:Running... udevadm settle --timeout=300
DEBUG:program:Return code: 0
DEBUG:testdata:sysfs attr /sys/class/block/sr0/device/model: 51454d55204456442d524f4d202020200a
DEBUG:blivet:               XFS.destroy: device: /dev/mapper/vg_test-snap ; type: xfs ; status: False ;
INFO:program:Running... udevadm settle --timeout=300
DEBUG:program:Return code: 0
DEBUG:testdata:sysfs attr /sys/class/block/sr0/device/model: 51454d55204456442d524f4d202020200a
ERROR:anaconda.modules.storage.installation:Failed to activate filesystems: device path does not exist or is not writable
INFO:anaconda.threading:Thread Failed: AnaTaskThread-ActivateFilesystemsTask-1 (139880334898944)
ERROR:anaconda.modules.common.task.task:Thread AnaTaskThread-ActivateFilesystemsTask-1 has failed: Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/pyanaconda/threading.py", line 280, in run
    threading.Thread.run(self)
  File "/usr/lib64/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/common/task/task.py", line 97, in _task_run_callback
    self._set_result(self.run())
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/storage/installation.py", line 94, in run
    raise StorageInstallationError(str(e)) from None
pyanaconda.modules.common.errors.installation.StorageInstallationError: device path does not exist or is not writable

INFO:anaconda.threading:Thread Done: AnaTaskThread-ActivateFilesystemsTask-1 (139880334898944)
WARNING:dasbus.server.handler:The call org.fedoraproject.Anaconda.Task.Finish has failed with an exception:
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/dasbus/server/handler.py", line 421, in _method_callback
    *unwrap_variant(parameters)
  File "/usr/lib/python3.6/site-packages/dasbus/server/handler.py", line 234, in _handle_call
    return handler(*parameters)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/common/task/task_interface.py", line 114, in Finish
    self.implementation.finish()
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/common/task/task.py", line 161, in finish
    threadMgr.raise_if_error(self._thread_name)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/threading.py", line 171, in raise_if_error
    raise exc_info[0](exc_info[1]).with_traceback(exc_info[2])
  File "/usr/lib64/python3.6/site-packages/pyanaconda/threading.py", line 280, in run
    threading.Thread.run(self)
  File "/usr/lib64/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/common/task/task.py", line 97, in _task_run_callback
    self._set_result(self.run())
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/storage/installation.py", line 94, in run
    raise StorageInstallationError(str(e)) from None
pyanaconda.modules.common.errors.installation.StorageInstallationError: device path does not exist or is not writable
Comment 11 Marta Lewandowska 2021-07-09 09:46:24 UTC 
Fix confirmed using test compose which includes python3-blivet-3.4.0-2.el8.
Comment 14 Jan Stodola 2021-07-16 16:49:35 UTC 
python3-blivet-3.4.0-2.el8 is present in RHEL-8.5.0-20210716.n.0, moving to VERIFIED.
Comment 17 errata-xmlrpc 2021-11-09 18:49:19 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (python-blivet bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4297
Note You need to log in before you can comment on or make changes to this bug.