HIVE-3002: IBMCloud MachinePools: Snowflake FailureDomain matching#2825
Conversation
|
@2uasimojo: This pull request references HIVE-3002 which is a valid jira issue. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/hold for QE |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2825 +/- ##
==========================================
+ Coverage 50.40% 50.70% +0.30%
==========================================
Files 279 279
Lines 34194 34534 +340
==========================================
+ Hits 17236 17511 +275
- Misses 15597 15642 +45
- Partials 1361 1381 +20
🚀 New features to boost your workflow:
|
|
/test konflux |
|
@huangmingxia: The specified target(s) for Use DetailsIn 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-sigs/prow repository. |
|
/retest |
|
Caution There are some errors in your PipelineRun template.
|
We've been using cluster-control-plane-machineset-operator (CPMS) utilities to extract failure domains from MachineSets for comparison when matching up generated msets with remote ones. CPMS doesn't support IBMCloud, so we were quietly getting back a generic (empty) failure domain for all IBMCloud msets, resulting in false positive matches and bad controller behavior (namely deleting all but one of the remote MachineSets). Here we add local code to interpret the `Zone` from the providerSpec as the failure domain and match on it.
86596dd to
3f207cb
Compare
|
/test security |
|
/retest hive-mce-28 |
|
@2uasimojo: This pull request references HIVE-3002 which is a valid jira issue. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/test e2e |
|
/test hive-mce-26-on-pull-request |
|
/test verify |
|
@2uasimojo: Overrode contexts on behalf of 2uasimojo: Red Hat Konflux DetailsIn 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-sigs/prow repository. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 2uasimojo, dlom The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/override "Red Hat Konflux" ? |
|
@2uasimojo: all tests passed! 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. |
e33d703
into
openshift:master
We've been using cluster-control-plane-machineset-operator (CPMS) utilities to extract failure domains from MachineSets for comparison when matching up generated msets with remote ones. CPMS doesn't support IBMCloud, so we were quietly getting back a generic (empty) failure domain for all IBMCloud msets, resulting in false positive matches and bad controller behavior (namely deleting all but one of the remote MachineSets).
Here we add local code to interpret the
Zonefrom the providerSpec as the failure domain and match on it.