Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1342639 - Installation using liveimg does not apply configuration of the ks network directive
Summary: Installation using liveimg does not apply configuration of the ks network dir...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Brian Lane
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1326338 ovirt-node-ng-platform
TreeView+ depends on / blocked
 
Reported: 2016-06-03 18:17 UTC by Fabian Deutsch
Modified: 2016-11-03 23:25 UTC (History)
2 users (show)

Fixed In Version: anaconda-21.48.22.77-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 23:25:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:2158 0 normal SHIPPED_LIVE anaconda bug fix and enhancement update 2016-11-03 13:13:55 UTC

Description Fabian Deutsch 2016-06-03 18:17:00 UTC 
Description of problem:
When installing content using the liveimg directive, configurations performed using th ekickstart network directive are not applied.
However, this should be working in this regular installation flow.

For LiveCD installation flows this hebavior is probably correct.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create ks with liveimg source
2. Install a host in manual mode using this ks
3. Change i.e the hostname or apply othe rnetworking settings

Actual results:
The network settings are not applied during installation and not available after installation.

Expected results:
The networking after installation is as congiured during installation

Additional info:
Comment 1 Brian Lane 2016-06-03 19:11:47 UTC 
I'm not able to reproduce this. If I have, for example, a hostname set in the kickstart it is written to /etc/hostname on the target system and hostnamectl is executed.
Comment 2 Fabian Deutsch 2016-06-03 20:33:22 UTC 
See for example bug 1333034 and especially bug 1326338
Comment 3 Brian Lane 2016-06-03 20:54:43 UTC 
(In reply to Fabian Deutsch from comment #2)
> See for example bug 1333034 and especially bug 1326338

Yes, I saw those. I cannot reproduce the problem with the current nightly.
Comment 4 Fabian Deutsch 2016-06-03 21:30:25 UTC 
Right.

maybe you can try the iso from this location:
http://jenkins.ovirt.org/user/fabiand/my-views/view/ovirt-node-ng/job/ovirt-node-ng_master_build-artifacts-fc22-x86_64/lastSuccessfulBuild/artifact/exported-artifacts/

It is based on the latest CentOS 7 iso with our payload and kickstart.
Comment 5 David Shea 2016-06-03 21:58:11 UTC 

*** This bug has been marked as a duplicate of bug 1290858 ***
Comment 6 Brian Lane 2016-06-03 23:30:53 UTC 
Ok, I think I know what's happening. Your squashfs.img has a /etc/hostname in it already and mine didn't. You should be able to work around this for now by removing it in %post when creating the image.

These 3 files will have the same issue:

/etc/hostname
/etc/resolv.conf
/etc/sysconfig/network

I think we should probably also fix this in anaconda, checking for liveimg the same way we check for a livecd install.

https://github.com/rhinstaller/anaconda/pull/663
Comment 7 Fabian Deutsch 2016-06-06 09:18:08 UTC 
Yes, I could have mentioned this before, we already planned to do this and have patches to remove those files in our live image: https://gerrit.ovirt.org/58180

This bug was just about also fixing this from the anaconda side.
Comment 13 errata-xmlrpc 2016-11-03 23:25:16 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/RHEA-2016-2158.html
Note You need to log in before you can comment on or make changes to this bug.