Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1925233

Summary:	Secondary ports of masters and workers created differently
Product:	OpenShift Container Platform	Reporter:	Michał Dulko <mdulko>
Component:	Installer	Assignee:	Adolfo Duarte <adduarte>
Installer sub component:	OpenShift on OpenStack	QA Contact:	Jon Uriarte <juriarte>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	low
Priority:	medium	CC:	m.andre, pprinett
Version:	4.7	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.8.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-04-14 15:07:36 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 Michał Dulko 2021-02-04 16:20:45 UTC

Version: 

That's a 4.7 nightly.

Platform:

openstack

Please specify:
* IPI

What happened?

There's an inconsistency in how secondary network ports are created for masters and workers. For workers the ports on secondary network will be tagged and have a trunk created. For masters none of those will happen.

What did you expect to happen?

I'd expect consistent behavior here. I don't have a strong opinion on tagging but I do on trunk ports - trunks are only created for Kuryr to function correctly, so they're not necessary on secondary interfaces.

How to reproduce it (as minimally and precisely as possible)?

1. Run installation with additionalNetworkIDs for masters and workers.
2. Inspect ports of masters and workers created for additional networks.

Anything else we need to know?

https://bugzilla.redhat.com/show_bug.cgi?id=1924917 - that happens due to this behavior. We'll work it around in Kuryr anyway.