MCO-1736: Promote ImageModeStatusReporting feature gate to default#2738
MCO-1736: Promote ImageModeStatusReporting feature gate to default#2738isabella-janssen wants to merge 1 commit into
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
@isabella-janssen: This pull request references MCO-1736 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. 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. |
|
Skipping CI for Draft Pull Request. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthrough
Suggested reviewers: 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 Checkov (3.3.8)payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yamlTraceback (most recent call last): payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yamlTraceback (most recent call last): payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-Default.yamlTraceback (most recent call last):
🔧 golangci-lint (2.12.2)Error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented Comment |
|
Hello @isabella-janssen! Some important instructions when contributing to openshift/api: |
|
/test verify-feature-promotion |
|
PR-Agent: could not fine a component named |
|
[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 |
|
/test verify-feature-promotion |
|
PR-Agent: could not fine a component named |
|
/test verify-feature-promotion |
|
PR-Agent: could not fine a component named |
|
/test verify-feature-promotion |
|
PR-Agent: could not fine a component named |
|
/test verify-feature-promotion |
|
PR-Agent: could not fine a component named |
|
/test verify-feature-promotion |
|
PR-Agent: could not fine a component named |
|
/test verify-feature-promotion |
|
PR-Agent: could not fine a component named |
|
/test verify-feature-promotion |
|
PR-Agent: could not fine a component named |
|
/test verify-feature-promotion |
1 similar comment
|
/test verify-feature-promotion |
|
/test verify-feature-promotion |
1 similar comment
|
/test verify-feature-promotion |
|
/test verify-feature-promotion |
1 similar comment
|
/test verify-feature-promotion |
7de5fb2 to
e86e7bf
Compare
|
/test verify-feature-promotion |
2 similar comments
|
/test verify-feature-promotion |
|
/test verify-feature-promotion |
|
/testwith openshift/api/master/verify-feature-promotion #2782 |
|
/test verify-feature-promotion |
e86e7bf to
5eac8d2
Compare
|
/test verify-feature-promotion |
5 similar comments
|
/test verify-feature-promotion |
|
/test verify-feature-promotion |
|
/test verify-feature-promotion |
|
/test verify-feature-promotion |
|
/test verify-feature-promotion |
|
/testwith openshift/api/master/verify-feature-promotion #2789 |
5eac8d2 to
472571c
Compare
|
/test verify-feature-promotion |
|
PR-Agent: could not fine a component named |
|
/test verify-feature-promotion |
|
PR-Agent: could not fine a component named |
472571c to
28becb2
Compare
|
/test verify-feature-promotion |
|
@isabella-janssen: The following test 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. |
Opening as a draft to monitor component readiness score.