VM boot with pci-passthrough interface failed to ping internal-net

Bug #1790174 reported by Peng Peng
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Invalid
High
Steven Webster

Bug Description

Brief Description
-----------------
Booting a vm with pci-passthrough vif model on internal net, then adding vlan to pci-passthrough interface for VM, then ping vm over mgmt and internal nets from base vm, but failed.

Severity
--------
Major

Steps to Reproduce
------------------
1. Get a network that supports pci-passthrough to boot vm
2. Create a flavor with dedicated cpu policy
3. Boot a base vm with above flavor and virtio nics
4. Create a flavor with specified extra-specs and dedicated cpu policy
5. Set extra-specs to the flavor
6. Boot a vm with pci-passthrough vif model on internal net
7. Add vlan to pci-passthrough interface for VM
8. Ping vm over mgmt and internal nets from base vm

Expected Behavior
------------------
Ping success

Actual Behavior
----------------
Ping failed

Reproducibility
---------------
100% Reproducible

System Configuration
--------------------
Storage system

Branch/Pull Time/Commit
-----------------------
master as of 2018-08-30_20-18-00

Timestamp/Logs
--------------
[2018-08-31 10:49:23,632] 264 DEBUG MainThread ssh.send :: Send 'ping -c 5 10.10.2.134'
[2018-08-31 10:49:37,737] 391 DEBUG MainThread ssh.expect :: Output:
PING 10.10.2.134 (10.10.2.134) 56(84) bytes of data.

--- 10.10.2.134 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

]0;root@tenant2-pci-passthrough-8:~tenant2-pci-passthrough-8:~#
[2018-08-31 10:49:37,737] 264 DEBUG MainThread ssh.send :: Send 'echo $?'
[2018-08-31 10:49:37,840] 391 DEBUG MainThread ssh.expect :: Output:
1
]0;root@tenant2-pci-passthrough-8:~tenant2-pci-passthrough-8:~#
[2018-08-31 10:49:37,840] 2631 INFO MainThread network_helper.ping_server:: retry in 3 seconds
[2018-08-31 10:49:40,843] 2638 WARNING MainThread network_helper.ping_server:: Ping from 192.168.231.12 to 10.10.2.134 failed.

[2018-08-31 10:51:52,603] 264 DEBUG MainThread ssh.send :: Send 'ip addr'
......
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 3c:fd:fe:9c:8b:a9 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::3efd:feff:fe9c:8ba9/64 scope link
       valid_lft forever preferred_lft forever
4: eth1.2705@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 3c:fd:fe:9c:8b:a9 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::3efd:feff:fe9c:8ba9/64 scope link
       valid_lft forever preferred_lft forever

Revision history for this message
Ghada Khalil (gkhalil) wrote :

Marked as gating for stx.2018.10 as it's expected that this should work in starlingx

tags: added: stx.network
tags: added: stx.2018.10 stx.networking
removed: stx.network
Changed in starlingx:
assignee: nobody → Steven Webster (swebster-wr)
importance: Undecided → High
status: New → Triaged
Revision history for this message
Ghada Khalil (gkhalil) wrote :
Changed in starlingx:
status: Triaged → Invalid
Revision history for this message
Ghada Khalil (gkhalil) wrote :

Marking as Invalid; same as the duplicate bug report

Ken Young (kenyis)
tags: added: stx.1.0
removed: stx.2018.10
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.