OCPBUGS-63237: There should be no role ARN field as token-auth-aws/azure/gcp=false in csv annotations
Before:
After
@cajieh: This pull request references Jira Issue OCPBUGS-63237, which is invalid:
- expected the bug to target the "4.21.0" version, but no target version was set
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
/hold Need to verify this change on AWS STS enabled cluster
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.
[!IMPORTANT]
Review skipped
Auto reviews are limited based on label configuration.
:no_entry_sign: Review skipped — only excluded labels are configured. (1)
- do-not-merge/work-in-progress
Please check the settings in the CodeRabbit UI or the
.coderabbit.yamlfile in this repository. To trigger a single review, invoke the@coderabbitai reviewcommand.You can disable this status message by setting the
reviews.review_statustofalsein the CodeRabbit configuration file.
✨ Finishing touches
🧪 Generate unit tests (beta)
- [ ] Create PR with unit tests
- [ ] Post copyable unit tests in a comment
Comment @coderabbitai help to get the list of available commands and usage tips.
Checked on sts cluster with the pr code, when operator annotations containing token-auth-aws/azure/gcp=false, on operator install page, there is not cloud credential related required field.
before:
after:
/verified by yanpzhan
@yanpzhan: This PR has been marked as verified by yanpzhan.
In response to this:
Checked on sts cluster with the pr code, when operator annotations containing token-auth-aws/azure/gcp=false, on operator install page, there is not cloud credential related required field. before:
after:
/verified by yanpzhan
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-required
@cajieh: This pull request references Jira Issue OCPBUGS-63237, which is invalid:
- expected the bug to target the "4.21.0" version, but no target version was set
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
Before:
![]()
After
![]()
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 backend
/retest-required
/test e2e-gcp-console
/jira refresh
@cajieh: This pull request references Jira Issue OCPBUGS-63237, which is valid. The bug has been moved to the POST state.
3 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.22.0) matches configured target version for branch (4.22.0)
- bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
Requesting review from QA contact: /cc @yapei
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
/jira refresh
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.
/verified later @yanpzhan /label acknowledge-critical-fixes-only
@cajieh: This PR has been marked to be verified later by @yanpzhan.
In response to this:
/verified later @yanpzhan /label acknowledge-critical-fixes-only
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-gcp-console
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cajieh, jhadvig
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~frontend/OWNERS~~ [cajieh,jhadvig]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/unhold
/retest
/retest-required
Remaining retests: 0 against base HEAD 19b01f06cb8106dfe21ca3cc12dd5376a5935e39 and 2 for PR HEAD ed4d16dd870019afc355158f551e5ac8637d9e99 in total
/retest
/test okd-scos-images
/test okd-scos-images
/test okd-scos-images
/retest-required
Remaining retests: 0 against base HEAD 9ac9e36e6bca30bd2b7f84752cc588f4cb842b44 and 1 for PR HEAD ed4d16dd870019afc355158f551e5ac8637d9e99 in total
/retest-required
Remaining retests: 0 against base HEAD d3b540a070b976f490eb3259f963703f4c33200d and 0 for PR HEAD ed4d16dd870019afc355158f551e5ac8637d9e99 in total
@cajieh: 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-sigs/prow repository. I understand the commands that are listed here.
@cajieh: Jira Issue OCPBUGS-63237: All pull requests linked via external trackers have merged:
This pull request has the verified-later tag and will need to be manually moved to VERIFIED after testing. Jira Issue OCPBUGS-63237 has been moved to the MODIFIED state.
In response to this:
Before:
![]()
After
![]()
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.
@cajieh: new pull request created: #15869
In response to this:
/cherry-pick release-4.20
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.
/cherry-pick release-4.21
@cajieh: new pull request created: #15870
In response to this:
/cherry-pick release-4.21
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.