Bug 1042933
| Summary: | neutron-server fails to start when deploying Neutron controller host group via Foreman | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | jliberma <jliberma> |
| Component: | openstack-foreman-installer | Assignee: | Jason Guiditta <jguiditt> |
| Status: | CLOSED ERRATA | QA Contact: | Omri Hochman <ohochman> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.0 | CC: | breeler, hateya, jguiditt, jliberma, mlopes, morazi, ohochman, rhos-maint, rohara, sclewis, sreichar, yeylon |
| Target Milestone: | rc | ||
| Target Release: | 4.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-foreman-installer-1.0.0-1.el6ost | Doc Type: | Bug Fix |
| Doc Text: |
Networking now requires 'neutron-db-manage stamp' be run at install time, prior to starting the Networking service. An exec as been added to the puppet manifest that calls 'neutron-db-manage stamp' before attempting to start the Networking server.
The result is that the Networking server can be successfully started. Development work is currenly undergoing to enforce the order of resource execution. In the interim, a second run of puppet agent is expected to resolve this successfully.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-20 00:44:28 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1040649 | ||
|
Description
jliberma@redhat.com
2013-12-13 16:28:08 UTC
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/ 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 |