Bug 1562966
| Summary: | Fresh OCP 3.7 on AWS install fails with "msg": "file not found: /etc/origin/logging/ca.crl.srl" | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | emahoney |
| Component: | Installer | Assignee: | Anping Li <anli> |
| Status: | CLOSED ERRATA | QA Contact: | Qiaoling Tang <qitang> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.7.1 | CC: | anli, aos-bugs, jcantril, jokerman, jrosenta, mmccomas, oarribas, rmeggins, rspazzol, sdodson |
| Target Milestone: | --- | ||
| Target Release: | 3.7.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: | 2018-04-29 14:36:36 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: | |||
@sdodson why was this moved from Installer to Logging? It is definitely a problem in openshift-ansible (in the logging role). I thought that's what we were to do for logging issue. I can leave it in component installer and assign to Eric for triage if that'd preferable. (In reply to Scott Dodson from comment #6) > I thought that's what we were to do for logging issue. I can leave it in > component installer and assign to Eric for triage if that'd preferable. Yeah - it is confusing - the _team_ working on it will be the logging team, but the _component_ containing the released fix will be openshift-ansible - I don't think the bz Component captures that. Maybe not related but shouldn't we be advising users of openshift-ansible to use a specific version of ansible. I don't recall 2.4.x.y being available when we released openshift-ansible for 3.7 Jeff, Yes, we advise that they use the version that ships in our channels, but ansible ended up in the RHEL 7 extras repo temporarily so it became likely that we'd get 2.4 unless the admin deliberately ensures that won't happen. https://github.com/openshift/openshift-ansible/pull/7764 proposed fix from the community 3.7 cherrypick https://github.com/openshift/openshift-ansible/pull/7815 I am seeing the same issue with a fresh 3.9 install. I suggest the affected release to be updated to 3.9 too. This seems to be blocking. is there a workaround? @raffaele This was the 3.9 cherry pick https://github.com/openshift/openshift-ansible/pull/7814 The /etc/origin/logging/ca.crl.srl can be found when deploy logging with openshift3/ose-ansible/images/v3.7.44-3 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:1231 |
Description of problem: A fresh installation of OCP 3.7 on AWS fails with the error message below: "msg": "file not found: /etc/origin/logging/ca.crl.srl" After the failed deploy, we noted that the ca.crl.srl file does not exist (there is a ca.crt.srl though!). After doing a 'touch ca.crl.srl' in that directory and re-running the playbook, the install is successful. We also noted that the variable 'openshift_master_overwrite_named_certificates=true' was not set in the inventory. Although that might be a red-herring. Version-Release number of selected component (if applicable): 3.7 latest How reproducible: Have not been able to reproduce. Steps to Reproduce: 1. 2. 3. Actual results: Install fails with "msg": "file not found: /etc/origin/logging/ca.crl.srl" Expected results: Successful install Additional info: Description of problem: Version-Release number of the following components: rpm -q openshift-ansible rpm -q ansible ansible --version How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Please include the entire output from the last TASK line through the end of output if an error is generated Expected results: Additional info: Please attach logs from ansible-playbook with the -vvv flag