Bug 1322981 - installer attempts to deactivate already-inactive devices
Summary: installer attempts to deactivate already-inactive devices
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python-blivet
Version: 7.2
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: David Lehman
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-31 20:04 UTC by David Lehman
Modified: 2021-09-03 14:13 UTC (History)
2 users (show)

Fixed In Version: python-blivet-0.61.15.48-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 23:52:54 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2168 0 normal SHIPPED_LIVE python-blivet bug fix and enhancement update 2016-11-03 13:15:34 UTC

Description David Lehman 2016-03-31 20:04:27 UTC
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:

Comment 1 David Lehman 2016-05-27 17:35:22 UTC
https://github.com/rhinstaller/blivet/pull/430

Comment 5 errata-xmlrpc 2016-11-03 23:52:54 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, 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


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