Description of problem: Nova instance missing ifcfg-ethX file Version-Release number of selected component (if applicable): Openstack 5.0 RHEL7 How reproducible: reproducible Steps to Reproduce: 1. nova boot instance 2. check instance's /etc/sysconfig/network-scripts directgory for ifcfg-ethX file, where X could be 0 or 1. This file contains: DEVICE=ethX BOOPROTO=dhcp 3. Actual results: In my case all instances didn't have the ifcfg-eth1 file. Expected results: The ifcfg-ethX should exist for any instance so that it will be assigned an IP address via dhcp. Additional info:
(In reply to Jean-Tsung Hsiao from comment #0) > Description of problem: Nova instance missing ifcfg-ethX file > > > Version-Release number of selected component (if applicable): > > Openstack 5.0 > > RHEL7 > > How reproducible: reproducible > > > Steps to Reproduce: > 1. nova boot instance > 2. check instance's /etc/sysconfig/network-scripts directgory for ifcfg-ethX > file, where X could be 0 or 1. This file contains: > DEVICE=ethX > BOOPROTO=dhcp > > 3. > > Actual results: > In my case all instances didn't have the ifcfg-eth1 file. > > Expected results: > The ifcfg-ethX should exist for any instance so that it will be assigned an > IP address via dhcp. What guest image are you using? Is it set up to use cloud-init? Have you verified to see if the nova metadata service is responding as expected?
(In reply to Russell Bryant from comment #2) > (In reply to Jean-Tsung Hsiao from comment #0) > > Description of problem: Nova instance missing ifcfg-ethX file > > > > > > Version-Release number of selected component (if applicable): > > > > Openstack 5.0 > > > > RHEL7 > > > > How reproducible: reproducible > > > > > > Steps to Reproduce: > > 1. nova boot instance > > 2. check instance's /etc/sysconfig/network-scripts directgory for ifcfg-ethX > > file, where X could be 0 or 1. This file contains: > > DEVICE=ethX > > BOOPROTO=dhcp > > > > 3. > > > > Actual results: > > In my case all instances didn't have the ifcfg-eth1 file. > > > > Expected results: > > The ifcfg-ethX should exist for any instance so that it will be assigned an > > IP address via dhcp. > > What guest image are you using? Is it set up to use cloud-init? Use the one created by virt-install. Don't think it's setup to use cloud-init. The image has a eth0 in it. So, ifcfg-eth1 should be created for all nova instances. > > Have you verified to see if the nova metadata service is responding as > expected? Here are all the nova related services: openstack-nova-api: active openstack-nova-cert: active openstack-nova-compute: active openstack-nova-network: inactive (disabled on boot) openstack-nova-scheduler: active openstack-nova-volume: inactive (disabled on boot) openstack-nova-conductor: active Anything missing?
(In reply to Jean-Tsung Hsiao from comment #3) > (In reply to Russell Bryant from comment #2) > > (In reply to Jean-Tsung Hsiao from comment #0) > > > Description of problem: Nova instance missing ifcfg-ethX file > > > > > > > > > Version-Release number of selected component (if applicable): > > > > > > Openstack 5.0 > > > > > > RHEL7 > > > > > > How reproducible: reproducible > > > > > > > > > Steps to Reproduce: > > > 1. nova boot instance > > > 2. check instance's /etc/sysconfig/network-scripts directgory for ifcfg-ethX > > > file, where X could be 0 or 1. This file contains: > > > DEVICE=ethX > > > BOOPROTO=dhcp > > > > > > 3. > > > > > > Actual results: > > > In my case all instances didn't have the ifcfg-eth1 file. > > > > > > Expected results: > > > The ifcfg-ethX should exist for any instance so that it will be assigned an > > > IP address via dhcp. > > > > What guest image are you using? Is it set up to use cloud-init? > > Use the one created by virt-install. Don't think it's setup to use > cloud-init. > > The image has a eth0 in it. So, ifcfg-eth1 should be created for all nova > instances. Please try an image prepared for use with OpenStack. For a tiny test image, you can download CirrOS. Fedora also distributes cloud images (http://fedoraproject.org/en/get-fedora#clouds). We also make cloud iamges of RHEL. A better place to get help may be using the internal rhos-tech mailing list.
Looks like regression to me. Why can't a virt image be used? Is this a OSP 5.0 feature?