Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 899459[details]
bug report for exception occur
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Comment on attachment 899459[details]
bug report for exception occur
The following was filed automatically by anaconda:
anaconda 13.21.215 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/storage/devicelibs/lvm.py", line 416, in lvactivate
raise LVMError("lvactivate failed for %s: %s" % (lv_name, msg))
File "/usr/lib/anaconda/storage/devices.py", line 2506, in setup
lvm.lvactivate(self.vg.name, self._name)
File "/usr/lib/anaconda/storage/devicetree.py", line 1631, in handleVgLvs
lv_device.setup()
File "/usr/lib/anaconda/storage/devicetree.py", line 2068, in _setupLvs
if self.handleVgLvs(device):
File "/usr/lib/anaconda/storage/devicetree.py", line 2162, in populate
if self._setupLvs():
File "/usr/lib/anaconda/storage/__init__.py", line 452, in reset
self.devicetree.populate(prog)
File "/usr/lib/anaconda/storage/__init__.py", line 109, in storageInitialize
storage.reset(examine_all=examine_all)
File "/usr/lib/anaconda/dispatch.py", line 210, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
self.moveStep()
File "/usr/lib/anaconda/gui.py", line 1458, in setScreen
self.anaconda.dispatch.gotoNext()
File "/usr/lib/anaconda/gui.py", line 1371, in nextClicked
self.setScreen ()
LVMError: lvactivate failed for lv_swap: 15:42:42,450 ERROR : Unable to resume vg_01hw722308-lv_swap (253:2)
Comment 3Samantha N. Bueno
2014-05-27 12:17:33 UTC
Please provide a set of steps to reproduce the issue.
Created attachment 899459 [details] bug report for exception occur Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: