-
Bug
-
Resolution: Done
-
Normal
-
4.12.z
-
None
Description of problem:
On the Machinesets, we configured the Azure tags, that should be assigned to the newly created nodes. VMs and disks have that tags assigned, while NICs - don't have configured Azsure tags assigned to them.
Version-Release number of selected component (if applicable):
OCP 4.11
How reproducible:
It can be reproducible
Steps to Reproduce:
1. We need to acquire Azure tags
2. Create machine set configs with Azure tags configured
3. Create VMs through the machine set
Actual results:
NICs, created by the Machinesets don't have Azure tags, configured on the Machineset.
Expected results:
NiCs should automatically pick up these tags.
Additional info:
As in Azure NICs can be treated as separate resources. there is a possibility if we assign the tags for the NICs in the main machine config file. it may work.
- clones
-
OCPBUGS-14012 NICs, created by the Machinesets doesn't have Azure tags.
- Closed
- depends on
-
OCPBUGS-17222 NICs, created by the Machinesets doesn't have Azure tags.
- Closed
- is cloned by
-
OCPBUGS-17222 NICs, created by the Machinesets doesn't have Azure tags.
- Closed
- is depended on by
-
OCPBUGS-14012 NICs, created by the Machinesets doesn't have Azure tags.
- Closed
- links to