| 2024-07-05 00:07:42 |
Seyeong Kim |
bug |
|
|
added bug |
| 2024-07-05 00:07:50 |
Seyeong Kim |
tags |
|
sts |
|
| 2024-07-05 00:09:09 |
OpenStack Infra |
neutron: status |
New |
In Progress |
|
| 2024-07-05 02:06:12 |
Seyeong Kim |
neutron: assignee |
|
Seyeong Kim (seyeongkim) |
|
| 2024-07-05 07:12:01 |
Lajos Katona |
tags |
sts |
ovn sriov-pci-pt sts |
|
| 2024-07-05 07:24:17 |
Lajos Katona |
neutron: importance |
Undecided |
High |
|
| 2024-07-08 15:42:13 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
| 2024-07-10 13:39:09 |
Daniel Speichert |
bug |
|
|
added subscriber Daniel Speichert |
| 2024-08-12 09:16:33 |
OpenStack Infra |
tags |
ovn sriov-pci-pt sts |
in-unmaintained-zed ovn sriov-pci-pt sts |
|
| 2024-08-13 04:45:21 |
Seyeong Kim |
bug task added |
|
neutron (Ubuntu) |
|
| 2024-08-13 05:07:06 |
Seyeong Kim |
description |
Port status goes BUILD when migrating non-sriov instance in sriov setting.
Test
1. Deploy Antelope with juju ( upstream also has the same code )
2. Enable SRIOV
3. create a vm without sriov nic. (test)
4. migrate it to another host
- openstack server migrate --live-migration --os-compute-api-version 2.30 --host node-04.maas test
5. check port status
- https://paste.ubuntu.com/p/RKGnP76MvB/
nova-compute has neutron-sriov-nic-agent and neutron-ovn-metadata-agent
So far, I've checked that
ovn_monitor change it to ACTIVE but sriov-nic-agent change it back to BUILD by calling _get_new_status
./plugins/ml2/drivers/mech_sriov/agent/sriov_nic_agent.py
binding_activate
- get_device_details_from_port_id
- get_device_details
- _get_new_status < this makes status BUILD.
so as running order is not fixed, sometimes it goes ACTIVE, sometimes BUILD. |
[ Impact ]
Port status goes BUILD when migrating non-sriov instance in sriov setting.
[ Test Plan ]
1. Deploy Antelope with juju ( upstream also has the same code )
2. Enable SRIOV
3. create a vm without sriov nic. (test)
4. migrate it to another host
- openstack server migrate --live-migration --os-compute-api-version 2.30 --host node-04.maas test
5. check port status
- https://paste.ubuntu.com/p/RKGnP76MvB/
[ Where problems could occur ]
this patch is related to sriov agent. it adds checking if port is sriov or not. so it could be possible that sriov port can be handled inproperly.
[ Other Info ]
nova-compute has neutron-sriov-nic-agent and neutron-ovn-metadata-agent
So far, I've checked that
ovn_monitor change it to ACTIVE but sriov-nic-agent change it back to BUILD by calling _get_new_status
./plugins/ml2/drivers/mech_sriov/agent/sriov_nic_agent.py
binding_activate
- get_device_details_from_port_id
- get_device_details
- _get_new_status < this makes status BUILD.
so as running order is not fixed, sometimes it goes ACTIVE, sometimes BUILD. |
|
| 2024-08-13 05:07:47 |
Seyeong Kim |
nominated for series |
|
Ubuntu Focal |
|
| 2024-08-13 05:07:47 |
Seyeong Kim |
bug task added |
|
neutron (Ubuntu Focal) |
|
| 2024-08-13 05:07:47 |
Seyeong Kim |
nominated for series |
|
Ubuntu Noble |
|
| 2024-08-13 05:07:47 |
Seyeong Kim |
bug task added |
|
neutron (Ubuntu Noble) |
|
| 2024-08-13 05:07:47 |
Seyeong Kim |
nominated for series |
|
Ubuntu Jammy |
|
| 2024-08-13 05:07:47 |
Seyeong Kim |
bug task added |
|
neutron (Ubuntu Jammy) |
|
| 2024-08-13 05:07:47 |
Seyeong Kim |
nominated for series |
|
Ubuntu Oracular |
|
| 2024-08-13 05:07:47 |
Seyeong Kim |
bug task added |
|
neutron (Ubuntu Oracular) |
|
| 2024-08-13 07:18:54 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~seyeongkim/ubuntu/+source/neutron/+git/neutron/+merge/471128 |
|
| 2024-08-13 08:36:38 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~seyeongkim/ubuntu/+source/neutron/+git/neutron/+merge/471136 |
|
| 2024-08-19 06:46:28 |
Seyeong Kim |
neutron (Ubuntu Oracular): status |
New |
In Progress |
|
| 2024-08-19 06:46:34 |
Seyeong Kim |
neutron (Ubuntu Oracular): assignee |
|
Seyeong Kim (seyeongkim) |
|
| 2024-08-19 06:46:39 |
Seyeong Kim |
neutron (Ubuntu Focal): assignee |
|
Seyeong Kim (seyeongkim) |
|
| 2024-08-19 06:46:45 |
Seyeong Kim |
neutron (Ubuntu Jammy): assignee |
|
Seyeong Kim (seyeongkim) |
|
| 2024-08-19 06:51:13 |
Seyeong Kim |
neutron (Ubuntu Noble): assignee |
|
Seyeong Kim (seyeongkim) |
|
| 2024-08-20 05:57:31 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~seyeongkim/ubuntu/+source/neutron/+git/neutron/+merge/471583 |
|
| 2024-08-20 06:02:03 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~seyeongkim/ubuntu/+source/neutron/+git/neutron/+merge/471584 |
|
| 2024-08-20 06:02:31 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~seyeongkim/ubuntu/+source/neutron/+git/neutron/+merge/471585 |
|
| 2024-08-20 06:25:54 |
Seyeong Kim |
neutron (Ubuntu Noble): status |
New |
In Progress |
|
| 2024-08-20 06:25:57 |
Seyeong Kim |
neutron (Ubuntu Jammy): status |
New |
In Progress |
|
| 2024-08-20 09:56:00 |
James Page |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-08-20 09:56:17 |
James Page |
description |
[ Impact ]
Port status goes BUILD when migrating non-sriov instance in sriov setting.
[ Test Plan ]
1. Deploy Antelope with juju ( upstream also has the same code )
2. Enable SRIOV
3. create a vm without sriov nic. (test)
4. migrate it to another host
- openstack server migrate --live-migration --os-compute-api-version 2.30 --host node-04.maas test
5. check port status
- https://paste.ubuntu.com/p/RKGnP76MvB/
[ Where problems could occur ]
this patch is related to sriov agent. it adds checking if port is sriov or not. so it could be possible that sriov port can be handled inproperly.
[ Other Info ]
nova-compute has neutron-sriov-nic-agent and neutron-ovn-metadata-agent
So far, I've checked that
ovn_monitor change it to ACTIVE but sriov-nic-agent change it back to BUILD by calling _get_new_status
./plugins/ml2/drivers/mech_sriov/agent/sriov_nic_agent.py
binding_activate
- get_device_details_from_port_id
- get_device_details
- _get_new_status < this makes status BUILD.
so as running order is not fixed, sometimes it goes ACTIVE, sometimes BUILD. |
[ Impact ]
Port status goes BUILD when migrating non-sriov instance in sriov setting.
[ Test Plan ]
1. Deploy OpenStack using Juju & Charms ( upstream also has the same code )
2. Enable SRIOV
3. create a vm without sriov nic. (test)
4. migrate it to another host
- openstack server migrate --live-migration --os-compute-api-version 2.30 --host node-04.maas test
5. check port status
- https://paste.ubuntu.com/p/RKGnP76MvB/
[ Where problems could occur ]
this patch is related to sriov agent. it adds checking if port is sriov or not. so it could be possible that sriov port can be handled inproperly.
[ Other Info ]
nova-compute has neutron-sriov-nic-agent and neutron-ovn-metadata-agent
So far, I've checked that
ovn_monitor change it to ACTIVE but sriov-nic-agent change it back to BUILD by calling _get_new_status
./plugins/ml2/drivers/mech_sriov/agent/sriov_nic_agent.py
binding_activate
- get_device_details_from_port_id
- get_device_details
- _get_new_status < this makes status BUILD.
so as running order is not fixed, sometimes it goes ACTIVE, sometimes BUILD. |
|
