-
Notifications
You must be signed in to change notification settings - Fork 118
OCPBUGS-62632: Do not report Progressing=True during cluster scaleup or node reboot #1447
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
base: main
Are you sure you want to change the base?
Conversation
…or node reboot
This change improves user's upgrade experience as outlined by
OCPSTRAT-2484 by fixing false alarms in ClusterOperator status.
The following new rule is adhered to:
* Operators should not report Progressing only because DaemonSets
owned by them are adjusting to a new node from cluster scaleup or a node
rebooting from cluster upgrade.
This is achieved by adding helper annotation
"tuned.openshift.io/stable-generation" to the tuned daemonset.
Other minor fixes:
* Minor logging fix (updateTunedProfileStatus())
* Update profile.Status also when profile.Status.ObservedGeneration != profile.Generation
* Removed non-functional code from the operator initializing ClusterOperator status
Resolves: OCPBUGS-62632
|
Skipping CI for Draft Pull Request. |
|
@jmencak: This pull request references Jira Issue OCPBUGS-62632, 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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jmencak 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 |
|
/jira refresh |
|
@jmencak: This pull request references Jira Issue OCPBUGS-62632, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (liqcui@redhat.com), skipping review request. 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. |
|
/test all |
|
/payload-job periodic-ci-openshift-release-master-ci-4.22-upgrade-from-stable-4.21-e2e-aws-ovn-upgrade |
|
@jmencak: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/7bda56e0-d9b5-11f0-8a9c-d6494fa18d6f-0 |
|
/test e2e-aws-ovn-techpreview |
Upgrade test looks good, no legacy-cvo-invariants test issues from |
|
@jmencak: 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. |
This change improves user's upgrade experience as outlined by OCPSTRAT-2484 by fixing false alarms in ClusterOperator status.
The following new rule is adhered to:
This is achieved by adding helper annotation
tuned.openshift.io/stable-generationto the tuned daemonset.Other minor fixes:
Resolves: OCPBUGS-62632