Description of problem: packstack expects eth0 interface names. In some situations users may not want to setup on eth0. Version-Release number of selected component (if applicable): rdo-3 repo How reproducible: 100% Steps to Reproduce: 1. setup a vm with an eth1 but no eth0 2. run packstack --install-hosts=x,y,z where z contains a vm with eth1 3. Actual results: packstack expecting eth0 when there is none Expected results: packstack should install regardless of ethernet interface name Additional info: [sdake@brew64 ~]$ packstack --install-hosts=192.168.122.10,192.168.122.11,192.168.122.12 Welcome to Installer setup utility Packstack changed given value to required value /home/sdake/.ssh/id_rsa.pub Installing: Clean Up... [ DONE ] Setting up ssh keys...root.122.10's password: root.122.11's password: root.122.12's password: [ DONE ] Adding pre install manifest entries... [ DONE ] Adding MySQL manifest entries... [ DONE ] Adding QPID manifest entries... [ DONE ] Adding Keystone manifest entries... [ DONE ] Adding Glance Keystone manifest entries... [ DONE ] Adding Glance manifest entries... [ DONE ] Adding Cinder Keystone manifest entries... [ DONE ] Installing dependencies for Cinder... [ DONE ] Checking if the Cinder server has a cinder-volumes vg... [ DONE ] Adding Cinder manifest entries... [ DONE ] Adding Nova API manifest entries... [ DONE ] Adding Nova Keystone manifest entries... [ DONE ] Adding Nova Cert manifest entries... [ DONE ] Adding Nova Conductor manifest entries... [ DONE ] Adding Nova Compute manifest entries... [ DONE ] Adding Nova Network manifest entries... ERROR : Error running remote script: Device eth0 does not exist Please check log file /var/tmp/packstack/20130514-155740-O_bVKz/openstack-setup.log for more information Additional information: * A new answerfile was created in: /home/sdake/packstack-answers-20130514-155740.txt * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
A bit more information: Some of my VMs had eth0 and some had eth1 which is what seems to cause the issue.
We do not plan to support heterogeneous environments. Foreman may be able to handle this scenario gracefully though.
*** Bug 978678 has been marked as a duplicate of this bug. ***