Description of problem: Error while running puppet agent -tv after adding host to Neutron Controller host group: "Error: Could not start Service[neutron-server]: Execution of '/sbin/service neutron-server start' returned 6: Error: /Stage[main]/Neutron::Server/Service[neutron-server]/ensure: change from stopped to running failed: Could not start Service[neutron-server]: Execution of '/sbin/service neutron-server start' returned 6: " Starting from command line gives this error: [root@rhos1 ~]# service neutron-server start neutron-db-check: ERROR: neutron database does not have version information. You must run the "neutron-db-manage stamp" command before starting neutron services. Version-Release number of selected component (if applicable): 12.12.1 code release, openstack-neutron-2013.2-15.el6ost.noarch How reproducible: Every time with 12.11 and 12.12 puddles Steps to Reproduce: 1. Install Foreman server and Neutron controller node base OS (RHEL 6.5) 2. Add 12.12.1 puddle + Lon's others repos and update 3. Run foreman_server.sh on Foreman server 4. Edit Neutron controller host group -- change admin password to 'password' 5. Run foreman_client.sh on Neutron controller node 6. Add Neutron controller node to the Neutron Controller host group in Foreman 7. Run puppet agent -tv on Neutron Controller node 8. Watch output for error near end of run Actual results: Error and neutron-server service fails to start Expected results: No errors and neutron-server service starts successfully Additional info:
So I repeated this result also using different systems. Interestingly enough, if the test systems were subscribed to the Beta channels, I did not see this error. Foreman was subscribed to the latest.
Need a lot more information. Please provide: - The NVR for both openstack-foreman-install and the packstack-modules-puppet. - The neutron server logs. - The neutron.conf file.
*** Bug 1043282 has been marked as a duplicate of this bug. ***
Ok, so there is a fix packstack added, we will likely do the same for now [1] It really seems to me that the neutron puppet module should do the right thing here, and that adding code to packstack OR foreman is a temporary hack to get around that issue. I may have to do the same as packstack for now in the foreman/quickstack modules, depending when/if this review lands for neutron puppet [2], which I have just asked dprince to try and get through, as it got marked abandoned. Once I can get at a test environment that matches that reported, I'll test and post the foreman version of the packstack fix. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1037675#c10 [2] https://review.openstack.org/#/c/50162/
Fix posted: https://github.com/redhat-openstack/astapor/pull/89
Related bug is #1043964
Tested RHOS 4.0 RC on RHEL 6.5 with: openstack-foreman-installer-1.0.0-1.el6ost.noarch packstack-modules-puppet-2013.2.1-0.20.dev936.el6ost.noarch Neutron controller host deployed and neuutron-server is running as expected. Marking as VERIFIED.
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. http://rhn.redhat.com/errata/RHEA-2013-1859.html