VMs not pingable after host reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Won't Fix
|
Medium
|
Steven Webster |
Bug Description
Brief Description
-----------------
Boot up VMs on a single node system, make sure VMs are pingable. After host reboot host, VMs are in Active state, but some of VMs are not pingable.
Severity
--------
Major
Steps to Reproduce
------------------
1. boot up 5VMs, ping 5 VMs
2. reboot -f host
3. check VMs in Active state
4. ping VMs
Expected Behavior
------------------
All pings success
Actual Behavior
----------------
some VM(s) failed to ping
Reproducibility
---------------
Intermittent (about 4/10 reproducing rate)
System Configuration
-------
One node system
Branch/Pull Time/Commit
-------
master as of 2018-09-09_20-18-00
Timestamp/Logs
--------------
[2018-09-10 06:05:46,435] 264 DEBUG MainThread ssh.send :: Send 'nova --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://
[2018-09-10 06:05:50,108] 391 DEBUG MainThread ssh.expect :: Output:
+------
| ID | Name | Tenant ID | Status | Task State | Power State | Networks |
+------
| 7379e11d-
[2018-09-10 06:05:52,424] 2628 INFO MainThread network_
[2018-09-10 06:05:52,424] 428 DEBUG MainThread ssh.exec_cmd:: Executing command...
[2018-09-10 06:05:52,424] 264 DEBUG MainThread ssh.send :: Send 'ping -c 3 192.168.251.11'
[2018-09-10 06:05:55,534] 391 DEBUG MainThread ssh.expect :: Output:
PING 192.168.251.11 (192.168.251.11) 56(84) bytes of data.
From 192.168.51.3 icmp_seq=1 Destination Host Unreachable
From 192.168.51.3 icmp_seq=2 Destination Host Unreachable
From 192.168.51.3 icmp_seq=3 Destination Host Unreachable
--- 192.168.251.11 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2016ms
pipe 3
description: | updated |
tags: | added: stx.2018.10 stx.networking |
Changed in starlingx: | |
assignee: | Ghada Khalil (gkhalil) → nobody |
Changed in starlingx: | |
assignee: | nobody → Steven Webster (swebster-wr) |
tags: |
added: stx.1.0 removed: stx.2018.10 |
As this issue occurs at a fairly high rate (40%), marking this gating for the 2018.10 milestone.