Bug 1249210
| Summary: | rhel-osp-director: Single controller overcloud deployment - neutron-l3-agent is down. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Alexander Chuzhoy <sasha> | ||||
| Component: | rhosp-director | Assignee: | Brent Eagles <beagles> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Shai Revivo <srevivo> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | unspecified | CC: | amuller, augol, beagles, dmacpher, mburns, rhel-osp-director-maint, sasha | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 10.0 (Newton) | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Known Issue | |||||
| Doc Text: |
A timing issue sometimes causes Overcloud neutron services to not automatically start correctly. This means instances are not accessible. As a workaround, you can run the following command on the Controller node cluster:
$ sudo pcs resource debug-start neutron-l3-agent
Instances will work correctly.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-10-14 17:05:32 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: | |||||||
| Attachments: |
|
||||||
Environment: python-neutron-lbaas-2015.1.0-5.el7ost.noarch openstack-neutron-ml2-2015.1.0-12.el7ost.noarch python-neutron-2015.1.0-12.el7ost.noarch python-neutronclient-2.4.0-1.el7ost.noarch openstack-neutron-common-2015.1.0-12.el7ost.noarch openstack-neutron-lbaas-2015.1.0-5.el7ost.noarch openstack-neutron-2015.1.0-12.el7ost.noarch openstack-neutron-metering-agent-2015.1.0-12.el7ost.noarch openstack-neutron-openvswitch-2015.1.0-12.el7ost.noarch instack-undercloud-2.1.2-22.el7ost.noarch Created attachment 1058127 [details]
neutron conf and logs
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10. The L3 agent is no longer a pacemaker managed service. Is this issue actually relevant for OSP-10 or should it be retargeted to OSP-9? I suspect this is closed currentrelease, but we should ask QE to test. If you think this should be explicitly tested on both 9 and 10, then let's do that. Please re-open with relevant OSP version if needed. closed, no need for needinfo. |
rhel-osp-director: Single controller overcloud deployment - neutron-l3-agent is down. Environment: Steps to reproduce: 1. Deploy undercloud. 2. Deploy overcloud with: 1 controller, 1 compute, 1 ceph. 3. Check the status of neutron-l3-agent Result: [root@overcloud-controller-0 ~]# pcs resource|grep -B2 -i Stop Started: [ overcloud-controller-0 ] Clone Set: neutron-l3-agent-clone [neutron-l3-agent] Stopped: [ overcloud-controller-0 ] -- Started: [ overcloud-controller-0 ] Clone Set: neutron-metadata-agent-clone [neutron-metadata-agent] Stopped: [ overcloud-controller-0 ] -- Started: [ overcloud-controller-0 ] Clone Set: neutron-dhcp-agent-clone [neutron-dhcp-agent] Stopped: [ overcloud-controller-0 ] One symptom is inability to communicate with the launched instances. Expected result: No stopped resources. Note: The W/A I applied was "pcs resource debug-start neutron-l3-agent" After that was able to launch instances and communicate with them.