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):
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
The network settings are not applied during installation and not available after installation.
The networking after installation is as congiured during installation
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.
See for example bug 1333034 and especially bug 1326338
(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.
maybe you can try the iso from this location:
It is based on the latest CentOS 7 iso with our payload and kickstart.
*** This bug has been marked as a duplicate of bug 1290858 ***
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:
I think we should probably also fix this in anaconda, checking for liveimg the same way we check for a livecd install.
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.
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.