| Summary: | Failed to upgrade ha environment if there are files in generated-configs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Anping Li <anli> | ||||
| Component: | Cluster Version Operator | Assignee: | Andrew Butcher <abutcher> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Anping Li <anli> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.1.0 | CC: | abutcher, aos-bugs, bleanhar, jokerman, mmccomas | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-01-29 20:58:09 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: | |||||
| Attachments: |
|
||||||
|
Description
Anping Li
2016-01-14 11:26:19 UTC
Created attachment 1114756 [details]
Upgrade output
When certificates are created as part of the upgrade, we hard link those into the generated-configs dir for all masters. In this case, we created master.proxy-client.{crt,key} on the first master and those files must have already existed in /etc/openshift/generated-configs/<master-hostname>/.
Another possibility is that something else caused the installer to think certificates were missing but, since the log fails on master.proxy-client.key, I think we generated them during this run.
Was this upgrade ran against a fresh 3.0.2.0 install that hadn't been upgraded previously?
(In reply to Andrew Butcher from comment #2) > When certificates are created as part of the upgrade, we hard link those > into the generated-configs dir for all masters. In this case, we created > master.proxy-client.{crt,key} on the first master and those files must have > already existed in /etc/openshift/generated-configs/<master-hostname>/. > > Another possibility is that something else caused the installer to think > certificates were missing but, since the log fails on > master.proxy-client.key, I think we generated them during this run. > > Was this upgrade ran against a fresh 3.0.2.0 install that hadn't been > upgraded previously? Yes, It is a fresh 3.0.2.0 installed by prior ansible playbook. Which only generated-configs on the master master. If we installed 3.0.2.0 with latest ansible playbook. generated-configs will be created on all masters/nodes. Proposed fix: https://github.com/openshift/openshift-ansible/pull/1245 Would you mind testing this from a checkout of the master branch of openshift-ansible? Verified and pass |