bug 2037665: Check policy name field independently of the configmap change#403
Conversation
openshift-ci
Bot
added
bugzilla/severity-high
|
@ingvagabund: This pull request references Bugzilla bug 2037665, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 6 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 kubernetes/test-infra repository. |
openshift-ci
Bot
added
the
approved
From the logs:
```
I0125 06:13:50.166765 1 status_controller.go:211] clusteroperator/kube-scheduler diff {"status":{"conditions":[{"lastTransitionTime":"2022-01-25T05:43:31Z","message":"NodeControllerDegraded: All master nodes are ready","reason":"AsExpected","status":"False","type":"Degraded"},{"lastTransitionTime":"2022-01-25T06:13:50Z","message":"NodeInstallerProgressing: 3 nodes are at revision 8; 0 nodes have achieved new revision 9","reason":"NodeInstaller","status":"True","type":"Progressing"},{"lastTransitionTime":"2022-01-25T05:45:45Z","message":"StaticPodsAvailable: 3 nodes are active; 3 nodes are at revision 8; 0 nodes have achieved new revision 9","reason":"AsExpected","status":"True","type":"Available"},{"lastTransitionTime":"2022-01-25T06:13:42Z","message":"PolicyUpgradeable: deprecated scheduler.policy field is set, and it is to be removed in the next release","reason":"Policy_PolicyFieldSpecified","status":"False","type":"Upgradeable"}]}}
...
I0125 06:13:50.953915 1 event.go:282] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-kube-scheduler-operator", Name:"openshift-kube-scheduler-operator", UID:"825f8035-2ba7-4136-bb5a-88d64e25298e", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'ConfigMapCreated' Created ConfigMap/config-10 -n openshift-kube-scheduler because it was missing
I0125 06:13:51.366266 1 status_controller.go:211] clusteroperator/kube-scheduler diff {"status":{"conditions":[{"lastTransitionTime":"2022-01-25T05:43:31Z","message":"NodeControllerDegraded: All master nodes are ready","reason":"AsExpected","status":"False","type":"Degraded"},{"lastTransitionTime":"2022-01-25T06:13:50Z","message":"NodeInstallerProgressing: 3 nodes are at revision 8; 0 nodes have achieved new revision 9","reason":"NodeInstaller","status":"True","type":"Progressing"},{"lastTransitionTime":"2022-01-25T05:45:45Z","message":"StaticPodsAvailable: 3 nodes are active; 3 nodes are at revision 8; 0 nodes have achieved new revision 9","reason":"AsExpected","status":"True","type":"Available"},{"lastTransitionTime":"2022-01-25T06:13:51Z","message":"All is well","reason":"AsExpected","status":"True","type":"Upgradeable"}]}}
```
The current deprecatedPolicy condition depends on whether the kube-scheduler-pod CM was updated or not.
Which is unrelated to whether the policy.name field is set or not.
Causing the PolicyUpgradeable condition to be cleared (deprecatedPolicy
to be unset) when the CM is not updated.
ingvagabund
force-pushed
the
check-policy-name-field-independent-of-cm-changes
branch
from
f032041 to
2f01603
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ingvagabund, soltysh 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 backport-risk-assessed |
openshift-ci
Bot
added
the
backport-risk-assessed
|
/label cherry-pick-approved |
openshift-ci
Bot
added
the
cherry-pick-approved
|
@ingvagabund: 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/test-infra repository. I understand the commands that are listed here. |
|
@ingvagabund: All pull requests linked via external trackers have merged:
Bugzilla bug 2037665 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 kubernetes/test-infra repository. |
ingvagabund
deleted the
check-policy-name-field-independent-of-cm-changes
branch
Following up on 430e536 (A prerequsite for 4.9 to 4.10 upgrades has been identified, 2022-01-20, openshift#1401), now that 4.9.19 has been named, includes [1], and [2] has been VERIFIED. [1]: openshift/cluster-kube-scheduler-operator#403 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=2037665
Following up on 430e536 (A prerequsite for 4.9 to 4.10 upgrades has been identified, 2022-01-20, openshift#1401), now that 4.9.19 has been named, includes [1], and [2] has been VERIFIED. [1]: openshift/cluster-kube-scheduler-operator#403 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=2037665
4 participants
From the logs:
The current deprecatedPolicy condition depends on whether the kube-scheduler-pod CM was updated or not.
Which is unrelated to whether the policy.name field is set or not.
Causing the PolicyUpgradeable condition to be cleared (deprecatedPolicy
to be unset) when the CM is not updated.