-
Bug
-
Resolution: Won't Do
-
Minor
-
None
-
4.12.0
-
+
-
Low
-
No
-
ShiftStack Sprint 233, ShiftStack Sprint 234, ShiftStack Sprint 235, ShiftStack Sprint 236
-
4
-
False
-
-
In the OpenStack Machine ProviderSpec, the TenantID property of the machine's "networks" could be ignored. With this change, when a ProjectID is not set and TenantID is set, TenantID is used.
-
Bug Fix
This is a clone of issue OCPBUGS-2153. The following is the description of the original issue:
—
When ProjectID is not set, TenantID might be ignored in MAPO.
Context: When setting additional networks in Machine templates, networks can be identified by the means of a filter. The network filter has both TenantID and ProjectID as fields. TenantID was ignored.
Steps to reproduce:
Create a Machine or a MachineSet with a template containing a Network filter that sets a TenantID.
```
networks:
- filter:
id: 'the-network-id'
tenantId: '123-123-123'
```
One cheap way of testing this could be to pass a valid network ID and set a bogus tenantID. If the machine gets associated with the network, then tenantID has been ignored and the bug is present. If instead MAPO errors, then in means that it has taken tenantID into consideration.
- blocks
-
OCPBUGS-10607 TenantID is ignored in some cases
- Closed
- clones
-
OCPBUGS-2153 TenantID is ignored in some cases
- Closed
- is blocked by
-
OCPBUGS-2153 TenantID is ignored in some cases
- Closed
- is cloned by
-
OCPBUGS-10607 TenantID is ignored in some cases
- Closed
- links to