| 2020-01-07 21:19:35 |
Jason Hobbs |
bug |
|
|
added bug |
| 2020-01-07 21:21:00 |
Jason Hobbs |
description |
I'm using pci-alias and a flavor referencing it to attach sr-iov VF interfaces to instances.
The instance gets the sr-iov device:
[ 1.521402] ixgbevf 0000:00:06.0 ens6: renamed from eth1
But it also gets an unwanted virtio device:
[ 1.544294] virtio_net virtio0 ens3: renamed from eth0
This virtio device is associated with the port created for the instance:
http://paste.ubuntu.com/p/VvdbvdWWDw/
instance:
http://paste.ubuntu.com/p/SSXCtgfDzx/
The desired behavior is for the instance to have only the sr-iov interface and for the port to be associated with it. The current behavior results in the instance trying to dhcp on the virtio interface, failing, and not getting any metadata as a result. |
I'm using pci-alias and a flavor referencing it to attach sr-iov VF interfaces to instances.
The instance gets the sr-iov device:
[ 1.521402] ixgbevf 0000:00:06.0 ens6: renamed from eth1
But it also gets an unwanted virtio device:
[ 1.544294] virtio_net virtio0 ens3: renamed from eth0
This virtio device is associated with the port created for the instance:
http://paste.ubuntu.com/p/VvdbvdWWDw/
instance:
http://paste.ubuntu.com/p/SSXCtgfDzx/
The desired behavior is for the instance to have only the sr-iov interface and for the port to be associated with it. The current behavior results in the instance trying to dhcp on the virtio interface, failing, and not getting any metadata as a result.
bundle: http://paste.ubuntu.com/p/WjySBgxpxh/
flavor: http://paste.ubuntu.com/p/54d2Dd2YVj/ |
|
| 2020-01-07 22:08:55 |
Jason Hobbs |
description |
I'm using pci-alias and a flavor referencing it to attach sr-iov VF interfaces to instances.
The instance gets the sr-iov device:
[ 1.521402] ixgbevf 0000:00:06.0 ens6: renamed from eth1
But it also gets an unwanted virtio device:
[ 1.544294] virtio_net virtio0 ens3: renamed from eth0
This virtio device is associated with the port created for the instance:
http://paste.ubuntu.com/p/VvdbvdWWDw/
instance:
http://paste.ubuntu.com/p/SSXCtgfDzx/
The desired behavior is for the instance to have only the sr-iov interface and for the port to be associated with it. The current behavior results in the instance trying to dhcp on the virtio interface, failing, and not getting any metadata as a result.
bundle: http://paste.ubuntu.com/p/WjySBgxpxh/
flavor: http://paste.ubuntu.com/p/54d2Dd2YVj/ |
I'm using pci-alias and a flavor referencing it to attach sr-iov VF interfaces to instances.
The instance gets the sr-iov device:
[ 1.521402] ixgbevf 0000:00:06.0 ens6: renamed from eth1
But it also gets an unwanted virtio device:
[ 1.544294] virtio_net virtio0 ens3: renamed from eth0
This virtio device is associated with the port created for the instance:
http://paste.ubuntu.com/p/VvdbvdWWDw/
instance:
http://paste.ubuntu.com/p/SSXCtgfDzx/
The desired behavior is for the instance to have only the sr-iov interface and for the port to be associated with it. The current behavior results in the instance trying to dhcp on the virtio interface, failing, and not getting any metadata as a result.
bundle: http://paste.ubuntu.com/p/WjySBgxpxh/
flavor: http://paste.ubuntu.com/p/54d2Dd2YVj/
crashdump: http://people.canonical.com/~jhobbs/juju-crashdump-openstack-2020-01-07-21.21.36.tar.gz |
|
| 2020-01-13 16:33:32 |
James Page |
charm-nova-compute: status |
New |
In Progress |
|
| 2020-01-13 16:33:35 |
James Page |
charm-nova-compute: assignee |
|
James Page (james-page) |
|
| 2020-01-14 12:13:14 |
James Page |
charm-nova-compute: status |
In Progress |
Incomplete |
|
