Bug 1276706 - Issue getting an IP address on the cfme-5.5 appliance
Issue getting an IP address on the cfme-5.5 appliance
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: Beta 2
: 5.5.0
Assigned To: Nick Carboni
Milan Falešník
Depends On:
  Show dependency treegraph
Reported: 2015-10-30 10:57 EDT by Chris Pelland
Modified: 2015-12-08 08:42 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-12-08 08:42:42 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Pelland 2015-10-30 10:57:56 EDT
There is a problem getting an IP address on the cfme-5.5 appliance (Only tested
vSphere) in build

To obtain IP address after booting up, please add the following line to /etc/sysconfig/network-scripts/ifcfg-eth0:


Devel status 10/29: Devel made a fix in the kickstart that will ensure that we have the configuration we need on first boot and we just finished testing out both upstream and downstream appliances built with that fix in place.

PR has been created and waiting to be merged: 

Devel is still diagnosing the underlying issue that is causing us to end up with an invalid configuration after the build.
Comment 1 Nick Carboni 2015-10-30 11:38:36 EDT
The root cause is the difference in tools writing the configuration files in question.

/etc/sysconfig/network-scripts/ifcfg-eth0 is being written by the anaconda dracut module parse-kickstart file upstream.

This means we write the device line we need here (https://git.fedorahosted.org/cgit/anaconda.git/tree/dracut/parse-kickstart?h=anaconda-19.31.122-1#n363) unconditionally.

The same file downstream is being written by dracut's ifcfg module.
We are running into issues with the "eth0" interface being recognized as a "kernel ethernet name" here (http://git.kernel.org/cgit/boot/dracut/dracut.git/tree/modules.d/45ifcfg/write-ifcfg.sh?h=RHEL-7#n109) and here (http://git.kernel.org/cgit/boot/dracut/dracut.git/tree/modules.d/40network/net-lib.sh?h=RHEL-7#n705)

If dracut sees a "kernel ethernet name" it writes the HWADDR rather than DEVICE.  One should be all we need for proper network configuration, but imagefactory removes the HWADDR here (https://github.com/redhat-imaging/imagefactory/blob/master/imgfac/FactoryUtils.py#L109) because we wouldn't want to specify a device MAC on a VM image (as the mac should be unique across multiple deployments)

So the PR referenced above may be our best bet until we can either move to the new network interface naming scheme (http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/) which should remove the issue with dracue or alter our build process to do what we need it to do regarding network interface config.
Comment 2 Nick Carboni 2015-11-03 10:22:05 EST
Latest build still had issue.  Moving back to ON_DEV
Comment 4 CFME Bot 2015-11-03 11:27:35 EST
New commit detected on ManageIQ/manageiq-appliance-build/master:

commit 299b249d7ddb6ca0a6fd9be9c92c4f3332115e7d
Author:     Nick Carboni <ncarboni@redhat.com>
AuthorDate: Tue Nov 3 10:23:12 2015 -0500
Commit:     Nick Carboni <ncarboni@redhat.com>
CommitDate: Tue Nov 3 10:23:12 2015 -0500

    Fix the line that conditionally prints DEVICE=
    The original PR used && in place of ||

 kickstarts/base.ks.erb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Comment 5 Milan Falešník 2015-11-04 12:08:16 EST
This issue is no longer present on, the appliance gets an IP address "out of the box"
Comment 7 errata-xmlrpc 2015-12-08 08:42:42 EST
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.


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