Unable to connect to router after host reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Won't Fix
|
High
|
Joseph Richard |
Bug Description
Brief Description
-----------------
router gateway ip unreachable after host reboots.
Severity
--------
Major
Steps to Reproduce
------------------
Note that step2&3 are possible operations that may relate to the failure, but exact steps are unknown.
1. Following VM using above router are reachable at first.
[2019-05-22 08:42:31,736] 262 DEBUG MainThread ssh.send :: Send 'ping -c 3 192.168.247.67'
PING 192.168.247.67 (192.168.247.67) 56(84) bytes of data.
64 bytes from 192.168.247.67: icmp_seq=1 ttl=63 time=0.608 ms
| be9d3256-
2. Force reboot active controller
[2019-05-22 08:49:27,127] 139 INFO MainThread host_helper.
[2019-05-22 08:49:27,127] 262 DEBUG MainThread ssh.send :: Send 'sudo reboot -f'
3. Lock/unlock a compute host
[2019-05-22 09:16:58,318] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://
4. Router interface unreachable at following time:
[2019-05-22 09:27:28,961] 262 DEBUG MainThread ssh.send :: Send 'ping -c 3 192.168.247.83'
PING 192.168.247.83 (192.168.247.83) 56(84) bytes of data.
From 192.168.47.1 icmp_seq=1 Destination Host Unreachable
| b0a6890e-
Expected Behavior
------------------
4. router gateway and VM should be reachable
Actual Behavior
----------------
4. router gateway and VM are no longer reachable
Reproducibility
---------------
Intermittent
System Configuration
-------
2+3 system
Lab-name: wcp99-103
Branch/Pull Time/Commit
-------
stx master as of "2019-05-
Last Pass
---------
Not sure. Saw same test passed on 2019-05-
Timestamp/Logs
--------------
See Steps to Reproduce for time stamps of each step.
Following vim log shows router scheduling failed briefly, however it is likely due to compute-2 (original router host) was being lock/unlocked. So the error could be expected. We are seeing router is moved to compute-1 later on, but the router interfaces are not reachable even after router is rescheduled successfully.
2019-05-
2019-05-
2019-05-
2019-05-
[2019-05-22 09:30:33,609] 387 DEBUG MainThread ssh.expect :: Output:
+------
| ID | Agent Type | Host | Availability Zone | Alive | State | Binary |
+------
| 65d5cb77-
+------
controller-1:~$
Test Activity
-------------
Sanity
tags: | added: stx.retestneeded |
tags: | added: stx.sanity |
description: | updated |
tags: |
added: stx.2.0 removed: stx.distro.openstack |
Changed in starlingx: | |
importance: | Undecided → High |
vswitch is ovs-dpdk