-
Notifications
You must be signed in to change notification settings - Fork 220
[release-4.12] OCPBUGS-34110: Avoid spurious updates for scope in IngressClass #1056
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
[release-4.12] OCPBUGS-34110: Avoid spurious updates for scope in IngressClass #1056
Conversation
Specify spec.parameters.scope on ingressclasses that the operator creates. Before this commit, the update logic would try to revert the default value that the API set for an ingressclass's scope field. * pkg/operator/controller/ingressclass/ingressclass.go (desiredIngressClass): Specify spec.parameters.scope with the default value: "Cluster". * pkg/operator/controller/ingressclass/ingressclass_test.go (Test_desiredIngressClass): Update test to expect spec.parameters.scope to be set.
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-6701 has been cloned as Jira Issue OCPBUGS-34110. Will retitle bug to link to clone. 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. |
|
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-34110, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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. |
|
/assign @alebedev87 |
|
Seeing a perma issue with machine-config operator:
/test e2e-aws-operator |
|
Root cause of e2e-aws-operator failures seems to be:
Need the fix in #1037 to be backported to 4.12. |
|
#1037 has been backported to 4.12. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alebedev87 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 |
|
/label qe-approved verified by pre-merge test, no "updated IngressClass" in CIO log |
|
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-34110, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
Requesting review from QA contact: 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. |
|
/label cherry-pick-approved |
|
/label backport-risk-assessed |
|
@knobunc: Can not set label backport-risk-assessed: Must be member in one of these teams: [] 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. |
|
/tide refresh |
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-34110: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-34110 has been moved to the MODIFIED state. 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. |
|
@openshift-cherrypick-robot: 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. |
|
[ART PR BUILD NOTIFIER] This PR has been included in build ose-cluster-ingress-operator-container-v4.12.0-202405311907.p0.g0473ff0.assembly.stream.el8 for distgit ose-cluster-ingress-operator. |
|
Fix included in accepted release 4.12.0-0.nightly-2024-06-06-104737 |
This is an automated cherry-pick of #879
/assign candita