Bug 1695461
| Summary: | Setting DEBUG_LOGLEVEL = 6 in /etc/origin/master/master.env causes controller manager of the service catalog to crash/restart | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Priyanka Kanthale <pkanthal> |
| Component: | Service Catalog | Assignee: | Jesus M. Rodriguez <jesusr> |
| Status: | CLOSED DUPLICATE | QA Contact: | Jian Zhang <jiazha> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.11.0 | CC: | aos-bugs, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | 3.11.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-07-10 16:01:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Compare https://bugzilla.redhat.com/show_bug.cgi?id=1689366 verified version After further investigation, I believe this bug is a duplicate of BZ #1689366 which was fixed in version 3.11.98 and released by an errata RHBA-2019:0636. The version in this bug as seen in comment #3 shows 3.11.43 which is older than 3.11.98. The version in BZ #1663501 is 3.11.51 which is also older than 3.11.98. Please apply the following errata. https://access.redhat.com/errata/RHBA-2019:0636 *** This bug has been marked as a duplicate of bug 1689366 *** |
Description of problem: Setting DEBUG_LOGLEVEL=6 in /etc/origin/master/master.env on all masters and then restarting the api and controllers made controller manager of the service catalog started to crash/restart. # oc get po -n kube-service-catalog NAME READY STATUS RESTARTS AGE apiserver-79vlx 1/1 Running 48 44d apiserver-fw77w 1/1 Running 70 114d apiserver-jb7w2 1/1 Running 47 44d controller-manager-5dxp4 0/1 CrashLoopBackOff 355 115d controller-manager-8q75n 0/1 CrashLoopBackOff 348 115d controller-manager-z59kt 0/1 CrashLoopBackOff 351 115d > Removing the change from /etc/origin/master/master.env the pods were running as expected. Actual results: controller manager of the service catalog restarting and goes in CrashLoopBackOff Expected results: controller-manager should be running. Additional info: