Outbound Network Connectivity Failing for Instances Connected to a Virtual Router

Problem

< A list of observable facts that characterize the undesirable behavior, starting with the most obvious and customer-identified, but continuing with those identified during the diagnostic process. Error messages, Bug references (link to Launchpad), log file entries, and behavior different than expected are all candidate symptoms. >

Environment

  • Platform9 Managed OpenStack - v4.0 and Higher

< The hardware, software, environmental conditions, and recent changes that are associated with this particular problem and resolution. Generally, our company’s product and/or product components are listed first. It’s OK for the environment to partially overlap with product category metadata. >

Cause

<The reason for the problem, if known.>

Resolution

[root@neen.platform9.net chinmay(admin)]# openstack router show 3d3ec419-e0e5-45fa-a661-bfeb14261658 -c ha
+-------+-------+
| Field | Value |
+-------+-------+
| ha | False |
+-------+-------+

There is no l3 agent hosting this router and since it has HA disabled it did not failover to any other node.

[root@neen.platform9.net chinmay(admin)]# neutron l3-agent-list-hosting-router 3d3ec419-e0e5-45fa-a661-bfeb14261658
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.

[root@neen.platform9.net chinmay(admin)]#
To correct this, added the router to another L3 agent.
[root@neen.platform9.net chinmay(admin)]# openstack network agent list | grep l3
| 57b9312f-1f60-42c6-9ed2-0e9f18d0d0b7 | L3 agent | e66b666a-29fe-4a4a-ad8d-168bc9cb3e16 | nova | :-) | UP | neutron-l3-agent |
| 673e1117-8962-4e67-baa2-fa8c6b91f0b3 | L3 agent | 48d1203d-8f7d-4d43-be67-da4850812c3f | nova | :-) | UP | neutron-l3-agent |

Additional Information

ZD case #1385911