Bug 1878007
| Summary: | Clean up invalid operator/v1 (Operator)LogLevels for all operators and tighten validation | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Venkata Siva Teja Areti <vareti> |
| Component: | config-operator | Assignee: | Venkata Siva Teja Areti <vareti> |
| Status: | CLOSED ERRATA | QA Contact: | Xingxing Xia <xxia> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.5 | CC: | aos-bugs, bparees, jsafrane, markmc, piqin, sttts, xxia |
| Target Milestone: | --- | ||
| Target Release: | 4.5.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1877408 | Environment: | |
| Last Closed: | 2020-11-10 14:53:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1877408 | ||
| Bug Blocks: | 1866791 | ||
Latest payload 4.5.0-0.nightly-2020-10-29-070117 still does not yet include the PR. Thus, per DPTP-660's requirement "a nightly build containing the fix is marked as accepted" for "bugs will be moved to verified", will wait more time to until such a build is there. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.5.18 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4425 |
I'm following the issue DPTP-660 to do the pre-merge verifying for QE pre-merge verification goal of issue OCPQE-815. Below are steps: Use the bot to launch cluster including the still open but approved PR(s). Then run: $ oc patch openshiftapiserver cluster -p '{"spec": {"operatorLogLevel": "oastest111"}}' --type merge $ oc patch openshiftapiserver cluster -p '{"spec": {"logLevel": "oastest222"}}' --type merge $ oc get openshiftapiserver cluster -o=jsonpath='{.spec.operatorLogLevel}{"; "}{.spec.logLevel}{"\n"}' oastest111; oastest222 $ while true; do date; oc get openshiftapiserver cluster -o=jsonpath='{.spec.operatorLogLevel}{"; "}{.spec.logLevel}{"\n"}'; sleep 10; done Mon Oct 26 14:45:00 CST 2020 ... Mon Oct 26 14:48:40 CST 2020 Normal; Normal ^C $ oc get event -n openshift-config-operator ... 4m39s Normal OperatorLogLevelChange deployment/openshift-config-operator "spec.operatorLogLevel" changed from "oastest111" to "Normal" 4m39s Normal OperatorLogLevelChange deployment/openshift-config-operator "spec.logLevel" changed from "oastest222" to "Normal" The invalid log levels are normalized, expected by the PR. Notes, per comment 0, 4.5 fix only normalizes, not validates. So the bug is pre-merge verified. After the PR gets merged, the bug will be moved to VERIFIED by the bot automatically or, if not working, by me manually.