Description of problem: After deploying the undercloud on the director node, a KVM VM guest system with 2 NICs, and then rebooting the director node, the nics are renamed and the network does not come online. Version-Release number of selected component (if applicable): python-rdomanager-oscplugin-0.0.10-8.el7ost.noarch How reproducible: every Steps to Reproduce: 1. Install RHEL7.1 on a KVM VM with virtio devices 2. Follow https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html-single/Director_Installation_and_Usage and install Director 3. Deploy undercloud 4. reboot Actual results: No network Expected results: network! Additional info: The issue appears to be resolved *if* the HWADDR=aa:bb:cc:dd:ee:ff variable is added to the /etc/sysconfig/network-scripts/ifcfg-ethX files. This allows udev to determine the nic name and set it appropriately on system boot.
This should be resolved with the latest images using predictable names.
Dan, can you please provide some details as to how the vNICs were set up? NAT or bridge or..? I haven't managed to reproduce this yet, but that's probably because I always have HWADDR in my ifcfg scripts
(In reply to Dan Yasny from comment #5) > Dan, can you please provide some details as to how the vNICs were set up? > NAT or bridge or..? Bridge > > I haven't managed to reproduce this yet, but that's probably because I > always have HWADDR in my ifcfg scripts Me too. I wonder if this is a udev issue...?
After 11 subsequent deployments and various configurations, using the default instack VM created by instack-virt-setup I haven't seen this issue even once. Setting to verified
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-0604.html