vifs not reachable when VM have multiple vifs on same tenant network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Invalid
|
High
|
Patrick Bonnell |
Bug Description
Brief Description
-----------------
Only first vif is reachable when vm has multiple vifs over the same tenant net
Severity
--------
Major
Steps to Reproduce
------------------
1. Launch VM with management + 15 vifs.
[2018-09-02 01:11:43,528] 690 INFO MainThread vm_helper.boot_vm :: Booting VM tenant2-
[2018-09-02 01:11:43,529] 691 INFO MainThread vm_helper.boot_vm :: nova boot --image 71deccb7-
2. Verify all vnics are pingable from natbox
Expected Behavior
------------------
All interfaces should be pingable
Actual Behavior
----------------
]0;root@
[2018-09-02 01:41:58,063] 428 DEBUG MainThread ssh.exec_cmd:: Executing command...
[2018-09-02 01:41:58,063] 264 DEBUG MainThread ssh.send :: Send 'ip route'
[2018-09-02 01:41:58,169] 391 DEBUG MainThread ssh.expect :: Output:
default via 192.168.185.1 dev eth0
169.254.169.254 via 172.18.1.128 dev eth15 proto static
172.18.1.0/24 dev eth1 proto kernel scope link src 172.18.1.131
172.18.1.0/24 dev eth2 proto kernel scope link src 172.18.1.133
172.18.1.0/24 dev eth3 proto kernel scope link src 172.18.1.142
172.18.1.0/24 dev eth4 proto kernel scope link src 172.18.1.143
172.18.1.0/24 dev eth5 proto kernel scope link src 172.18.1.137
172.18.1.0/24 dev eth6 proto kernel scope link src 172.18.1.139
172.18.1.0/24 dev eth7 proto kernel scope link src 172.18.1.134
172.18.1.0/24 dev eth8 proto kernel scope link src 172.18.1.144
172.18.1.0/24 dev eth9 proto kernel scope link src 172.18.1.129
172.18.1.0/24 dev eth10 proto kernel scope link src 172.18.1.146
172.18.1.0/24 dev eth11 proto kernel scope link src 172.18.1.147
172.18.1.0/24 dev eth12 proto kernel scope link src 172.18.1.140
172.18.1.0/24 dev eth13 proto kernel scope link src 172.18.1.135
172.18.1.0/24 dev eth14 proto kernel scope link src 172.18.1.149
172.18.1.0/24 dev eth15 proto kernel scope link src 172.18.1.132
192.168.185.0/27 dev eth0 proto kernel scope link src 192.168.185.10
192.168.185.32/27 dev eth0 proto static scope link
192.168.185.64/27 dev eth0 proto static scope link
E Details: Ping unsuccessful from vm (logged in via 192.168.185.3): {'172.18.1.149': 100, '172.18.1.142': 100, '172.18.1.137': 100, '172.18.1.129': 100, '172.18.1.144': 100, '172.18.1.135': 100, '172.18.1.147': 100, '172.18.1.134': 100, '172.18.1.139': 100, '172.18.1.146': 100, '172.18.1.133': 100, '172.18.1.131': 0, '172.18.1.143': 100, '172.18.1.140': 100, '172.18.1.132': 100}
Only first vif is reachable when vm has multiple vifs over the same tenant net
Reproducibility
---------------
Reproducible
System Configuration
-------
Any
Branch/Pull Time/Commit
-------
StarlingX master as of 2018-08-31_20-18-00
tags: | added: stx.networking |
Changed in starlingx: | |
assignee: | nobody → Steven Webster (swebster-wr) |
Changed in starlingx: | |
assignee: | Steven Webster (swebster-wr) → Patrick Bonnell (pbonnell) |
Changed in starlingx: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: |
added: stx.1.0 removed: stx.2018.10 |
Issue seems to be reproducible in a number of automated runs. Marking for stx.2018.10