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.

Description of problem:
As a result of the fix for bug 1182229 (specifically, commit a909ea38) led to a problem in blivet's logic that causes it to try to deactivate devices that are already inactive as part of a recursive teardown. This can lead to messy error output in program.log, makes us look silly, and could potentially be problematic in some unforeseen scenario(s).

Version-Release number of selected component (if applicable):
python-blivet-0.61.15.39-1

How reproducible:
Always

Steps to Reproduce:
1. install a system with multiple lvs in a single vg
2. go to the main storage screen/hub in the 7.2 installer
3. examine /tmp/program.log

Actual results:
You will see several lvchange -an calls for already-inactive lvs.

Expected results:
We don't try to deactivate inactive devices.

Additional info:

https://github.com/rhinstaller/blivet/pull/430

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, 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://rhn.redhat.com/errata/RHBA-2016-2168.html