OCPBUGS-29868: Apply hypershift cluster-profile for ibm-cloud-managed #1037
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@openshift-art-build-bot: This pull request references Jira Issue OCPBUGS-29868, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci-robot
added
the
jira/valid-bug
|
/assign @ashwindasr |
|
/test e2e-hypershift |
|
I have verified the yaml file of both admin-acks and admin-gates, they all have the new addition. For details, please see my comment on https://issues.redhat.com/browse/OCPBUGS-29868, if this is the correct test strategy, I will tag qe-approve here. thanks. |
|
@JianLi-RH I think your testing is enough |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: openshift-art-build-bot, petr-muller 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 |
openshift-ci
bot
added
the
approved
|
/label qe-approved |
openshift-ci
bot
added
the
qe-approved
|
@openshift-art-build-bot: This pull request references Jira Issue OCPBUGS-29868, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (jianl@redhat.com), skipping review request. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/retest |
1 similar comment
|
/retest |
|
/retest Although it is really weird that one single job has four failures in a row, I have investigated the results and found no indication that the installation failures are related to this PR. |
|
@openshift-art-build-bot: all tests passed! 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. |
|
/label acknowledge-critical-fixes-only This PR does not seem to be risky to payloads |
openshift-ci
bot
added
the
acknowledge-critical-fixes-only
|
@openshift-art-build-bot: Jira Issue OCPBUGS-29868: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-29868 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 openshift-eng/jira-lifecycle-plugin repository. |
|
[ART PR BUILD NOTIFIER] This PR has been included in build cluster-version-operator-container-v4.16.0-202403180813.p0.g8f4a120.assembly.stream.el9 for distgit cluster-version-operator. |
|
Fix included in accepted release 4.16.0-0.nightly-2024-03-21-152650 |
Since HyperShift / Hosted Control Plane have adopted
include.release.openshift.io/ibm-cloud-managed, to tailor the resources of clusters running in the ROKS IBM environment, theinclude.release.openshift.io/hypershiftaddition will allow Hypershift to express different profile choices than ROKS