Bug 2193014

Summary:	RHOSP 16.2.4 - even shutdown the compute OS physical port, attached ports on this physnet (VFs) still seems active.
Product:	Red Hat OpenStack	Reporter:	XinhuaLi <xili>
Component:	openstack-neutron	Assignee:	Rodolfo Alonso <ralonsoh>
Status:	CLOSED NOTABUG	QA Contact:	Eran Kuris <ekuris>
Severity:	high	Docs Contact:
Priority:	medium
Version:	16.2 (Train)	CC:	chrisw, fpiccion, jlibosva, mlavalle, scohen
Target Milestone:	---	Flags:	ralonsoh: needinfo? (fpiccion)
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-04 16:30:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description XinhuaLi 2023-05-04 02:11:25 UTC

Description of problem:
On our SRIOV nodes, even we shutdown the compute OS physical port, attached ports on this physnet (VFs) still seems active.
On application this is a problem because if they cannot informed about port down, their VM level bonding not works as required.

Customer follow "https://access.redhat.com/solutions/5193451" and add this "NeutronPluginExtensions: "uplink_status_propagation"" to template and then deploy.

However, it does not work as expected and the issue is still there.

Version-Release number of selected component (if applicable):
RHOSP 16.2.4

How reproducible:
On our SRIOV nodes, even we shutdown the compute OS physical port, attached ports on this physnet (VFs) still seems active.

Steps to Reproduce:
1.
2.
3.

Actual results:
On our SRIOV nodes, even we shutdown the compute OS physical port, attached ports on this physnet (VFs) still seems active.

Expected results:
we shutdown the compute OS physical port, attached ports on this physnet (VFs) still be the inactive.

Additional info: