Red Hat Bugzilla – Bug 997137
Cannot create quantum networks after installation of OpenStack using packstack
Last modified: 2015-02-17 11:46:04 EST
Description of problem: Cannot create quantum networks after installation of OpenStack using packstack --allinone . Both CLI fails as well as horizon. This problem also appears to effect the operation of horizon as a whole, as each loaded page results in an error message in the top right corner.
Version-Release number of selected component (if applicable):
Have tried on two separate VMs with same result.
Steps to Reproduce:
1. Clean install of Fedora 19 using Netinstall CD.
2. Enable updates-testing repo.
3. yum clean all && yum update
4. yum install openstack-packstack
5. Apply bug work-arounds listed below
6. packstack --allinone
7. source keystonerc_admin
8. quantum net-list
OpenStack will install successfully and create keystonerc_admin and keystonerc_demo files, but quantum net-list command will fail, Errno 111.
Show list of networks
My environment is a VM on ESXi 5.1.
Applied bug work-arounds: Must edit nova_compute.pp to account for missing kvm.modules, must manually install python-django14 prior to running packstack --allinone.
After review several config files, I noticed the in the [filter:authtoken] section of /etc/quantum/api-paste.ini that admin_password=<password> seemed out of order. It was originally above auth_protocol, so I cut and pasted the entry below admin_user=<username> line, and now quantum works as intended. Errors in horizon have also ceased.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.
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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
Thank you for reporting this bug and we are sorry it could not be fixed.