Inject cluster ID to vSphere UPI compute and control plane nodes #10197
Conversation
When there are same compute names in the DC it's causing some issues described here: https://issues.redhat.com/browse/OCPBUGS-64930 To have unique name of cluster in the name seems help to avoid this issue. I have tried such change to do in our ocs-ci framework: red-hat-storage/ocs-ci#13587 Where I am altering this terraform file and when I am using this change we are not hitting the issue. Signed-off-by: Petr Balogh <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@petr-balogh: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
@petr-balogh terraform for upi has not been used in many releases, it was left behind as an example. PowerCli/PowerShell is the automation tool for UPI now. cc: @vr4manta /hold |
openshift-ci
bot
added
the
do-not-merge/hold
2 participants
When there are same compute names in the DC it's causing some issues described here:
https://issues.redhat.com/browse/OCPBUGS-64930
To have unique name of cluster in the name seems help to avoid this issue.
I have tried such change to do in our ocs-ci framework: red-hat-storage/ocs-ci#13587
Where I am altering this terraform file and when I am using this change we are not hitting the issue.