Bug 1534311
| Summary: | [3.8]apiserver pod of service catalog in CrashLoopBackOff status after upgrading to v3.8 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Weihua Meng <wmeng> |
| Component: | Service Broker | Assignee: | Jeff Peeler <jpeeler> |
| Status: | CLOSED ERRATA | QA Contact: | Weihua Meng <wmeng> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.8.0 | CC: | aos-bugs, chezhang, dmoessne, jiazha, jmatthew, jokerman, mmccomas, pmorie, tsanders, wmeng |
| Target Milestone: | --- | ||
| Target Release: | 3.9.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | 1534275 | Environment: | |
| Last Closed: | 2018-06-27 18:01:30 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: | |||
| Bug Depends On: | 1534275 | ||
| Bug Blocks: | |||
|
Description
Weihua Meng
2018-01-15 01:34:44 UTC
How was the 3.7 based cluster installed? I was able (with a few workarounds unrelated to catalog) to get a 3.9 upgrade to have the service catalog pods functioning successfully at the end. From the error output, it looks like the api aggregator has not been configured properly which was only recently fixed for 3.7 upgrades. Thanks for the info, Jeff. May I know the PR which has the fix you mentioned? OCP 3.7 cluster is installed by openshift-ansible. ansible-playbook -i inventory openshift-ansible/playbooks/byo/config.yml Ok if you did a fresh install, the aggregator should have been turned on. Just want to double confirm that 3.7 wasn't upgraded from a previous install.
For reference, doing "oc get configmap -n kube-system extension-apiserver-authentication -o jsonpath='{.data.requestheader-client-ca-file}'" should return data if the aggregator is enabled.
The upgrade fix was made in bug 1523298, but if you did a fresh install I don't know that it'll help.
It was fresh install OCP 3.7 before upgrade, and service catalog is enabled by default and was working before upgrade. Now that bug 1534275 is verified, I believe this bug should be too since the fix was a 3.7 problem. Weihua, It's not proper to explicitly run the 3.8 upgrade playbooks when upgrading from 3.7 to 3.9. Customers will never install openshift-ansible-3.8 nor will they run 3.8 upgrade playbooks, we'll probably strip those out of the packaging just to make this clear. The proper way to upgrade from 3.7 to 3.9 is to call the 3.9 upgrade playbooks with both 3.8 and 3.9 repos enabled on your hosts. This will automatically upgrade the control plane from 3.7 to 3.8 to 3.9. During this upgrade only the API and Controllers are updated to 3.8, all other components remain at 3.7 and then after the control plane has been updated they should be upgraded directly to 3.9. Thanks, Scott So upgrade to 3.8 is not supposed to be called even for online devops, and we will not test it anymore. Fixed as the cause of the original bug, aggregator issue, was addressed. 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, 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/RHSA-2018:2013 |