Red Hat Bugzilla – Bug 1028619
Neutron Networker host group inherits admin_password from params.pp instead of password generated in FOreman
Last modified: 2013-12-19 19:34:39 EST
Description of problem: Foreman deployed Neutron Networker host group does not use correct neutron admin password in /etc/neutron/neutron.conf. The Controller and Compute host groups use correct password. This host group inherits CHANGEME from params.pp. This causes nova boot commands to fail as instances cannot attach to network.
Version-Release number of selected component (if applicable):
10-28.2 openstack release
Steps to Reproduce:
1. Install Foreman installer
2. Install Neutron Controller node
3. Install Neutron Networker node
4. Install Neutron Compute node(s)
5. Compare admin_passwd in /etc/neutron/neutron.conf on all nodes.
admin_password = CHANGEME on networker
admin_password = same as compute and controller
I get Neutron client authentication errors when I attempt to launch an instance but correcting this password and restarting the services does not resolve it.
This should get fixed with https://github.com/redhat-openstack/astapor/pull/59 . To test, I overrode the neutron_user_password parameter in the neutron controller, compute and networker host groups, then spot checked that /etc/neutron/neutron.conf were consistent across the three associated host, e.g.:
$ grep admin_ /etc/neutron/neutron.conf
# admin_tenant_name = %SERVICE_TENANT_NAME%
admin_tenant_name = services
# admin_user = %SERVICE_USER%
admin_user = neutron
# admin_password = %SERVICE_PASSWORD%
admin_password = realdeal
Also relevant: the already merged https://github.com/redhat-openstack/astapor/pull/53 . Between the 2 PR's, we are handling neutron_config (/etc/neutron/neutron.con) exactly the same for the compute.pp and networker.pp manifests.
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.