Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
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.
(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.
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
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.
https://rhn.redhat.com/errata/RHEA-2016-2158.html