Bug 1203608

Summary: [atomic] iSCSI device configuration is not passed to installed system
Product: Red Hat Enterprise Linux 7 Reporter: Radek Vykydal <rvykydal>
Component: anacondaAssignee: Radek Vykydal <rvykydal>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: anaconda-maint-list, extras-qa, g.kaviyarasu, jonathan, jstodola, mbanas, vanmeeuwen+fedora, walters
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: anaconda-21.48.22.7-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1203234 Environment:
Last Closed: 2015-11-19 09:59:29 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 Radek Vykydal 2015-03-19 09:20:59 UTC
+++ This bug was initially created as a clone of Bug #1203234 +++

When configuring as iSCSI device in Atomic installer the configuration is not copied to installed system (/var/lib/iscsi) because in time of storage.write() the shared var is not mounted to deployment var.

--- Additional comment from Radek Vykydal on 2015-03-18 08:41:56 EDT ---

I checked that all other subtasks of storage.write() are only dealing with /etc so we should be good moving the call after deployment root bind mounts happen?

--- Additional comment from Colin Walters on 2015-03-18 09:05:45 EDT ---

This is indeed simpler.  My vague recollection here is there's no specific reason why I had the original storage.write() call duplicated there.

Comment 4 errata-xmlrpc 2015-11-19 09:59:29 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-2015-2284.html