Description of problem: I've tried PackStack to deploy OpenStack on several heterogeneous systems (based on Fedora 18) but the new naming convention of network interfaces used on Fedora systems is a serious problem because network interface names are different on each system. On a first one, the public interface is eth0, on another one, it's p49p1, on another, it's em1, etc. The new naming convention of network interfaces is not compatible with PackStack because the configuration variables (CONFIG_NOVA_COMPUTE_PRIVIF, CONFIG_NOVA_NETWORK_PUBIF, etc.) are global to the whole OpenStack installation and cannot be specified per system. Perhaps a note would be added in the Wiki documentation of PackStack about this problem. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I also have the same problem but in a different configuration: controller is a vm with eth0 and eth1 and nodes are physical machines with em1 and em2. Any solutions/workaround? Thanks Mario PS: I changed from RH components to fedora because the owner of the bug explicitly talked about f18
I've tried without success to reinstall all Fedora 18 servers with the biosdevname=0 kernel option. Another method is described on web page http://www.sysarchitects.com/em1_to_eth0 I've not tried it because I'm no more working on OpenStack.
Hi Philippe, thanks for the hints. I think that, in my case, trying yo get biosdevname working on the vm should be enough to obtain em* names and be able to install using packstack
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.