Bug 1571345

Summary: [scale lab] nova should update port with SG specified while spawning VM
Product: Red Hat OpenStack Reporter: Janki <jchhatba>
Component: opendaylightAssignee: lpeer <lpeer>
Status: CLOSED NOTABUG QA Contact: Itzik Brown <itbrown>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13.0 (Queens)CC: aadam, mkolesni, nyechiel, smalleni
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: scale_lab
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-29 06:55:56 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 Janki 2018-04-24 14:58:12 UTC
Description of problem:
Create a port. Create a VM attached to this port with customised SG. SG associated with the port should be updated to include the SG specified in VM creation.

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

How reproducible:
Always

Steps to Reproduce:
1. Create port
2. Create VM attached to this port with custom SG
3. See SGs associated with both VMs and port

Actual results:
Custom SG does not apply to port.

Expected results:
Custom SG should be applied to port.

Additional info:

Comment 2 Janki 2018-04-24 15:02:15 UTC
There is a workaround.

Manually update the security group of the port by running

openstack port update --security-group SG1_ID --security-group SG2_ID PORT_ID

We need to specify this workaround in our docs specially for VLAN aware VM use cases.