Bug 1826317

Summary:	Creating MachineSet on OpenStack is failing if port tags are not supported on OpenStack
Product:	OpenShift Container Platform	Reporter:	Simon Reber <sreber>
Component:	Cloud Compute	Assignee:	Pierre Prinetti <pprinett>
Cloud Compute sub component:	OpenStack Provider	QA Contact:	David Sanz <dsanzmor>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	adduarte, egarcia, m.andre, mfedosin, pprinett
Version:	4.3.z
Target Milestone:	---
Target Release:	4.5.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	This is a documentation change. The documentation now mentions "OpenStack resource tagging" as a prerequisite for installing OpenShift.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:29:42 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 Simon Reber 2020-04-21 12:35:43 UTC

Description of problem:

Creating of MachineSets respectively Machines via MachineSet is failing on OpenStack when port tags are not supported.

The error reported is as below and seems to be related to a upstream issue discussed in the openstack cloud-provider:

"OpenStack instance cannot be created: error creating Openstack instance: tagging port for server err: Resource not found"

This issue seems discussed upstream in https://github.com/kubernetes-sigs/cluster-api-provider-openstack/issues/543 and question is, as tags don't appear to be used, can we get rid of those to make the give use-case work.

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

 - 4.3.10

How reproducible:

 - Only at the customer (non Red Hat OpenStack)

Steps to Reproduce:
1. N/A

Actual results:

 - OpenStack instance cannot be created: error creating Openstack instance: tagging port for server err: Resource not found

Expected results:

 - Machine being created based on MachineSet configuration

Additional info:

Comment 5 David Sanz 2020-04-29 12:16:42 UTC

Verified as Fix is on docs

Comment 7 errata-xmlrpc 2020-07-13 17:29:42 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409