I tried to reproduce this problem by rebooting the network node instead of killing the L3-agent and deleting the qrouter namespace. I cannot reproduce the problem. This time I am able to ping and ssh the VMs after the L3-agent is started up again.
The steps taken are:
Repeat steps 1-3. The node has the neutron-server, neutron-dhcp-agent, neutron-metadata-agent, neutron-openvswitch-agent, as well as the neutron-l3-agent running.
Then
4. reboot the node.
5. After the node comes back up, start all the neutron components that were previously running:
a. start the neutron-server,
b. start the neutron-openvswitch-agent
c. start the neutron-dhcp-agent
d. start the neutron-metadata-agent
e. start the neutron-l3-agent.
6. Afterwards, ping and ssh to the VM works. The qrouter namespace has the same interfaces and IP addresses as before the node reboot.
I tried to reproduce this problem by rebooting the network node instead of killing the L3-agent and deleting the qrouter namespace. I cannot reproduce the problem. This time I am able to ping and ssh the VMs after the L3-agent is started up again.
The steps taken are:
Repeat steps 1-3. The node has the neutron-server, neutron-dhcp-agent, neutron- metadata- agent, neutron- openvswitch- agent, as well as the neutron-l3-agent running.
Then openvswitch- agent metadata- agent
4. reboot the node.
5. After the node comes back up, start all the neutron components that were previously running:
a. start the neutron-server,
b. start the neutron-
c. start the neutron-dhcp-agent
d. start the neutron-
e. start the neutron-l3-agent.
6. Afterwards, ping and ssh to the VM works. The qrouter namespace has the same interfaces and IP addresses as before the node reboot.