Bug 1322981

Summary:	installer attempts to deactivate already-inactive devices
Product:	Red Hat Enterprise Linux 7	Reporter:	David Lehman <dlehman>
Component:	python-blivet	Assignee:	David Lehman <dlehman>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	jstodola, mkovarik
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	python-blivet-0.61.15.48-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-03 23:52:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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