Router interfaces down and VM unreachable after changing neutron router to DVR then back to centralized
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| StarlingX |
High
|
marvin Yu |
Bug Description
Brief Description
-----------------
update neutron to DVR, then update it to centralized. The router interfaces and VM are not reachable.
Severity
--------
Major
Steps to Reproduce
------------------
Create router as centralized
update router to DVR
update route to centralized.
tried to reach tenant1-mgmt-net, but failed
TC-name:
test_dvr_
Expected Behavior
------------------
Actual Behavior
----------------
Reproducibility
---------------
Reproducible
System Configuration
-------
Multi-node system
Lab-name: WCP_3-6
Branch/Pull Time/Commit
-------
2019-11-21_20-00-00
Last Pass
---------
2019-08-23_20-59-00
Timestamp/Logs
--------------
[2019-11-23 17:56:48,357] 311 DEBUG MainThread ssh.send :: Send 'openstack --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://
[2019-11-23 17:56:53,524] 311 DEBUG MainThread ssh.send :: Send 'openstack --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://
[2019-11-23 18:14:49,567] 311 DEBUG MainThread ssh.send :: Send 'openstack --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://
[2019-11-23 18:14:54,518] 311 DEBUG MainThread ssh.send :: Send 'openstack --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://
+------
| ID | Name | MAC Address | Fixed IP Addresses | Status | Security Groups | Device Owner | Tags |
+------
| 108f184a-
| 58454d50-
| 65496f91-
| f8405df0-
+------
[2019-11-23 18:17:42,525] 311 DEBUG MainThread ssh.send :: Send 'ssh -v -o RSAAuthenticati
[2019-11-23 18:17:45,572] 433 DEBUG MainThread ssh.expect :: Output:
OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g 1 Mar 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 192.168.120.15 [192.168.120.15] port 22.
debug1: connect to address 192.168.120.15 port 22: No route to host
ssh: connect to host 192.168.120.15 port 22: No route to host
svc-cgcsauto@
[2019-11-23 18:17:45,573] 1241 INFO MainThread ssh.connect :: Unable to ssh to 192.168.120.15
Test Activity
-------------
Regression Testing
Peng Peng (ppeng) wrote : | #1 |
Ghada Khalil (gkhalil) wrote : | #2 |
Changed in starlingx: | |
assignee: | nobody → Le, Huifeng (hle2) |
tags: | added: stx.3.0 stx.distro.openstack stx.networking |
Changed in starlingx: | |
importance: | Undecided → High |
Yang Liu (yliu12) wrote : | #3 |
OpenStack configuration for WR lab is attached.
The neutron routers were created as centralized by default, and they were working fine initially until router update.
description: | updated |
Changed in starlingx: | |
assignee: | Le, Huifeng (hle2) → marvin Yu (marvin-yu) |
marvin Yu (marvin-yu) wrote : | #4 |
Due to device limitation, I have tried to reproduce this bug at stx-aio-dx.
Steps to Reproduce
------------------
Create router as centralized (pass)
update router to DVR (pass)
update route to centralized (pass)
ping to vm (pass)
It`s seems work well and no exception occur. if I’ve missed some steps, Let me know.
By the way, EXEC the command "openstack router set --disable --distributed a3ec2cca-
controller-
+------
| ID | Name | Status | State | Project | Distributed | HA |
+------
| 43e237e1-
| a3ec2cca-
+------
controller-
BadRequestExcep
Ghada Khalil (gkhalil) wrote : | #5 |
As discussed in the stx networking meeting, reproduction should be attempted on a multi-node system. This issue could be specific to this configuration.
Changed in starlingx: | |
status: | New → In Progress |
marvin Yu (marvin-yu) wrote : | #6 |
I have deployed a multi-node env to test, the ISO was created on 11/25. But Refer to the following steps, I can`t reproduce this bug.
Steps to Reproduce
------------------
Create router as centralized (pass)
update router to DVR (pass)
update route to centralized (pass)
ssh to vm (pass)
@pengpeng, could you help to check the detail steps as below?
if I miss some steps important, please Let me know.
controller-
+------
| ID | Name | Status | State | Project | Distributed | HA |
+------
| 1ec156a2-
| 6db39de6-
+------
controller-
controller-
controller-
controller-
+------
| ID | Name | Status | State | Project | Distributed | HA |
+------
| 1ec156a2-
| 6db39de6-
+------
controller-
controller-
controller-
controller-
+------
| ID | Name | Status | State | Project | Distributed | HA |
+------
| 1ec156a2-
Yang Liu (yliu12) wrote : | #7 |
Hi Marvin,
How did you configure your neutron router?
Could you please check the ports for the router?
For peng, the internal interfaces for the router went down after the router update, that is the cause for vm not reachable. The vm may still have an ip assigned in this state.
Assigning to networking PL for follow-up