Bug 1955969 - Workers cannot be deployed attached to multiple networks.
Summary: Workers cannot be deployed attached to multiple networks.
Keywords:
Status: ON_QA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.8
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: 4.8.0
Assignee: Adolfo Duarte
QA Contact: Udi Shkalim
URL:
Whiteboard:
: 1956251 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-01 20:06 UTC by Adolfo Duarte
Modified: 2021-05-11 11:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-api-provider-openstack pull 181 0 None open Bug 1955969: - Makes port names unique. 2021-05-07 03:58:00 UTC

Comment 3 egarcia 2021-05-05 15:37:51 UTC
*** Bug 1956251 has been marked as a duplicate of this bug. ***

Comment 4 Adolfo Duarte 2021-05-05 15:57:59 UTC
In this section of the code [1] ports are created with the name of the node, which when two or more ports are created will cause a match in this part of the code [2] which could cause problems because the second port with the same name would not be created instead the first port created with that name will be returned instead

So it seems that the problem seems to be related to ports with same names. 

This was also supported by the fact that when using the "port" entry in the machineset twice, without providing a namesuffix here [3] causes the similar errors. 

which take the form of: 

" oslo_db.exception.DBDuplicateEntry: (pymysql.err.IntegrityError) (1062, "Duplicate entry 'fa:16:3e:14:5e:07/8effd769-18b5-443b-9c8c-bd4210b1d909-0' for key 'uniq_virtual_interfaces0address0deleted'")
[SQL: INSERT INTO virtual_interfaces (created_at, updated_at, deleted_at, deleted, address, network_id, instance_uuid, uuid, tag) VALUES (%(created_at)s, %(updated_at)s, %(deleted_at)s, %(deleted)s, %(address)s, %(network_id)s, %(instance_uuid)s, %(uuid)s, %(tag)s)]
"

[1] https://github.com/openshift/cluster-api-provider-openstack/blob/master/pkg/cloud/openstack/clients/machineservice.go#L337
[2] https://github.com/openshift/cluster-api-provider-openstack/blob/master/pkg/cloud/openstack/clients/machineservice.go#L330
[3] https://github.com/openshift/cluster-api-provider-openstack/blob/master/pkg/cloud/openstack/clients/machineservice.go#L619

Comment 5 Adolfo Duarte 2021-05-07 01:03:48 UTC
Patch is ready for this: https://github.com/openshift/cluster-api-provider-openstack/pull/181

Comment 7 Pierre Prinetti 2021-05-07 14:52:37 UTC
Is there a plan to modify the way Terraform names the Control Plane ports at install time, to match what would be done by CAPO in day 2?


Note You need to log in before you can comment on or make changes to this bug.