Bug 2215624

Summary: Port edits through Horizon silently (re)set the port port binding profile to 'binding:vif_type': 'vrouter' at least for 'vhostuser' ports
Product: Red Hat OpenStack Reporter: Jacob Ansari <jansari>
Component: python-django-horizonAssignee: OSP Team <rhos-maint>
Status: NEW --- QA Contact: Ashish Gupta <ashigupt>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.2 (Train)CC: eprado, jansari, jjoyce, jschluet, rdopiera, skhandav, slinaber, tvignaud
Target Milestone: z6Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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 Jacob Ansari 2023-06-16 19:12:45 UTC 
Description of problem:

"Port edits through Horizon (re)set the port port binding profile to 'binding:vif_type': 'vrouter' when it is set to 'binding:vif_type': 'vhostuser' .  No option to override this is available in Horizon. Same port edit done through CLI preserves 'binding:vif_type': 'vhostuser' ".
The same change made throught OSP CLI does not present this issue.


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


How reproducible:
100%

Steps to Reproduce:
1. In Horizon, edit a port with 'binding:vif_type': 'vhostuser' and save changes

Actual results:
Changes in edit take affect, BUT 'binding:vif_type' gets reset to 'vrouter'

Expected results:
Changes in edit take affect, AND 'binding:vif_type' remains 'vhostuser'

Additional info:

This is BZ a narrower scoped on based on https://bugzilla.redhat.com/show_bug.cgi?id=2184815 which was opened as an RFE . Regardless of the path the RFE takes, there is  appears to be a concrete issue here in how 'binding:vif_type' is handled in horizon vs the CLI .
Comment 3 Radomir Dopieralski 2023-07-26 12:14:10 UTC 
*** Bug 2184815 has been marked as a duplicate of this bug. ***