-
Notifications
You must be signed in to change notification settings - Fork 218
OCPBUGS-61508: IngressOperator not exposing some metrics for degraded… #1290
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
OCPBUGS-61508: IngressOperator not exposing some metrics for degraded… #1290
Conversation
|
@davidesalerno: This pull request references Jira Issue OCPBUGS-61508, which is invalid:
Comment 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. |
|
@davidesalerno: This pull request references Jira Issue OCPBUGS-61508, which is invalid:
Comment 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 |
|
/retest |
|
/assign @alebedev87 |
|
/assign @grzpiotrowski |
38d8184 to
8864da1
Compare
|
/jira refresh |
|
@davidesalerno: This pull request references Jira Issue OCPBUGS-61508, which is invalid:
Comment 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. |
|
/test okd-scos-e2e-aws-ovn |
|
/jira refresh |
|
@davidesalerno: This pull request references Jira Issue OCPBUGS-61508, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code change looks fine. Some comments about the testing.
8864da1 to
b90a8c4
Compare
alebedev87
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Second look.
b90a8c4 to
3896e07
Compare
|
[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
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/jira refresh |
|
@lihongan: This pull request references Jira Issue OCPBUGS-61508, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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 |
|
tested it with 4.21.0-0-2025-11-07-061132-test-ci-ln-z5rxwg2-latest |
|
/label qe-approved |
|
/retest |
|
/test okd-scos-e2e-aws-ovn |
|
/test e2e-aws-pre-release-ossm |
|
@rhamini3: This PR has been marked as verified by 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. |
|
/test e2e-aws-ovn-serial-1of2 |
|
/test e2e-aws-ovn |
|
/test e2e-gcp-operator |
|
@davidesalerno: 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. |
|
@davidesalerno: Jira Issue Verification Checks: Jira Issue OCPBUGS-61508 Jira Issue OCPBUGS-61508 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 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. |
|
/cherry-pick release-4.20 |
|
@davidesalerno: new pull request created: #1305 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 kubernetes-sigs/prow repository. |
|
/cherry-pick release-4.19 |
|
@davidesalerno: new pull request created: #1308 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 kubernetes-sigs/prow repository. |
|
Fix included in accepted release 4.21.0-0.nightly-2025-11-15-144034 |
… IngressController
This PR is fixing the issue we have got into the ingress controller that is not exposing
ingress_operator_conditionsmetrics for existing ingress controllers if the operator pod is restarted till the ingress controllers status don't change.We can achieve this simply moving the
SetIngressControllerConditionsMetricaway from the code block inside the if statement checking if the ingress status is changed or not.Added an e2e test that is verifying that the metrics are there before and after the operator pod restart. The e2e test can't be executed in parallel with other tests because it is restarting the ingress operator pod and so it could affect in a non predictable way their results.