Bug 595569 – /sbin/device_cio_free needs to clear $DEVICE at start

Bug 595569 - /sbin/device_cio_free needs to clear $DEVICE at start

Summary:	/sbin/device_cio_free needs to clear $DEVICE at start

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	s390utils (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Dan Horák
QA Contact:	Yulia Kopkova
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-05-24 22:19 EDT by David Cantrell
Modified:	2010-11-10 17:18 EST (History)
CC List:	3 users (show)

See Also:
Fixed In Version:	s390utils-1.8.2-25.el6
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-11-10 17:18:44 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description David Cantrell 2010-05-24 22:19:35 EDT

The device_cio_ignore command needs to clear $DEVICE at run time, or else it inherits from the environment when it runs.

For example, when I do:

    /sbin/zfcp_cio_free -d 0.0.a002

From inside the installation environment, zfcp_cio_free appends 0.0.a002 to $DEVICE because $DEVICE is set to 'eth0' by /sbin/init, so it tries to free this list:

    "eth0,0.0.a002"

Adding:

    DEVICE=

to the top of the script should fix this up.

Comment 2 Dan Horák 2010-05-28 04:29:57 EDT

fixed in upstream commit 5655284a (http://fedorapeople.org/gitweb?p=sharkcz/public_git/utils.git;a=summary)

Comment 5 releng-rhel@redhat.com 2010-11-10 17:18:44 EST

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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