New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug 1852545: Add ResourcePoolPath to machines in vsphere #3863
Bug 1852545: Add ResourcePoolPath to machines in vsphere #3863
Conversation
Vcenter can have multiple datacenters and clusters. When a new cluster is created, the machine-api operator fails to find a default resource pool because there are multiple and there is ambiguity in choice. This will specify the exact path to reference the resources which will remove this ambiguity and will not cause failure in the installation process.
@rna-afk: This pull request references Bugzilla bug 1852545, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions 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/test-infra repository. |
/test e2e-vsphere |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cc @jcpowermac |
/test e2e-vsphere |
/test e2e-vsphere-upi |
UPI the compute nodes didn't come up |
/test e2e-vsphere |
1 similar comment
/test e2e-vsphere |
/test e2e-vsphere |
testing e2e-vsphere is blocked by openshift/cluster-etcd-operator#388 |
/test e2e-vsphere |
/lgtm
seems unrelated to this bug |
/retest Please review the full test history for this PR and help us cut down flakes. |
5 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
@rna-afk: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions 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/test-infra repository. I understand the commands that are listed here. |
@rna-afk: All pull requests linked via external trackers have merged: openshift/installer#3863. Bugzilla bug 1852545 has been moved to the MODIFIED state. In response to this:
Instructions 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/test-infra repository. |
/cherry-pick release-4.5 |
@abhinavdahiya: new pull request created: #4014 In response to this:
Instructions 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/test-infra repository. |
This has been resolved since July and is causing customer confusion. Removing bullet. See: openshift/installer#3863
This has been resolved since July and is causing customer confusion. Removing bullet. See: openshift/installer#3863
This has been resolved since July and is causing customer confusion. Removing bullet. See: openshift/installer#3863
This has been resolved since July and is causing customer confusion. Removing bullet. See: openshift/installer#3863
This has been resolved since July and is causing customer confusion. Removing bullet. See: openshift/installer#3863
In vsphere IPI installations, the VCenter can have multiple data centers and clusters.
When a new cluster is created, the machine-api operator fails to find a default resource
pool because there are multiple resource pools.
This will specify the exact path to reference the resources which will
remove this ambiguity and will not cause failure in the installation
process.