Bug 1415057
| Summary: | [IntService_public_324]jks-cert-gen pod failed by FileNotFoundException for /etc/origin/logging/system.admin.jks | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Xia Zhao <xiazhao> | ||||||||
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Xia Zhao <xiazhao> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 3.5.0 | CC: | aos-bugs, ewolinet, juzhao, xiazhao | ||||||||
| Target Milestone: | --- | Keywords: | TestBlocker | ||||||||
| Target Release: | 3.5.z | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||||||
| Doc Text: |
undefined
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2017-10-25 13:00:48 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Xia Zhao
2017-01-20 06:27:35 UTC
WIP PR to fix: https://github.com/openshift/openshift-ansible/pull/3135 I believe this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1415056 Same root cause *** Bug 1415056 has been marked as a duplicate of this bug. *** Above PR has been merged in Tested according to xiazhao's step from my local desktop, error "Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!" throws out. and jks-cert pod can't be generated.
libselinux-python package already installed on both desktop and master.
<localhost> EXEC /bin/sh -c 'rm -f -r /root/.ansible/tmp/ansible-tmp-1485237195.37-77603840609488/ > /dev/null 2>&1 && sleep 0'
fatal: [ec2-52-204-85-177.compute-1.amazonaws.com -> localhost]: FAILED! => {
"changed": true,
"failed": true,
"invocation": {
"module_args": {
"backup": false,
"content": null,
"delimiter": null,
"dest": "/tmp/openshift-logging-ansible-QTRjW5/signing.conf",
"directory_mode": null,
"follow": true,
"force": true,
"group": null,
"mode": null,
"original_basename": "signing.conf.j2",
"owner": null,
"regexp": null,
"remote_src": null,
"selevel": null,
"serole": null,
"setype": null,
"seuser": null,
"src": "/root/.ansible/tmp/ansible-tmp-1485237195.37-77603840609488/source",
"unsafe_writes": null,
"validate": null
}
},
"msg": "Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!"
}
to retry, use: --limit @/home/fedora/openshift-ansible/playbooks/common/openshift-cluster/openshift_logging.retry
attached ansible log
Created attachment 1243830 [details]
ansible log -20170124
Isn't the proper solution to install libselinux-python per the instructions for using ansible? http://docs.ansible.com/ansible/intro_installation.html#managed-node-requirements checked libselinux-python on the master $ rpm -qa | grep libselinux-python libselinux-python-2.5-6.el7.x86_64 checked libselinux-python on my desktop $ rpm -qa | grep libselinux-python libselinux-python3-2.5-3.fc24.x86_64 libselinux-python and libselinux-python3 are different, so install libselinux-python on my desktop, and run the ansible script again, error "Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!" don't throw out. run the ansible again after installing libselinux-python on my desktop, and can find system.admin.jks. This bug is fixed, although there are other bugs need to be filed. Set it to VERIFIED and close it. # ls -al /etc/origin/logging/ total 140 drwxr-xr-x. 2 root root 4096 Jan 25 00:12 . drwx------. 7 root root 4096 Jan 24 21:57 .. -rw-r--r--. 1 root root 1196 Jan 24 21:59 02.pem -rw-r--r--. 1 root root 1196 Jan 24 21:59 03.pem -rw-r--r--. 1 root root 1196 Jan 24 22:00 04.pem -rw-r--r--. 1 root root 1184 Jan 24 22:00 05.pem -rw-r--r--. 1 root root 1050 Jan 24 21:57 ca.crt -rw-r--r--. 1 root root 0 Jan 24 21:59 ca.crt.srl -rw-r--r--. 1 root root 301 Jan 24 22:00 ca.db -rw-r--r--. 1 root root 20 Jan 24 22:00 ca.db.attr -rw-r--r--. 1 root root 20 Jan 24 22:00 ca.db.attr.old -rw-r--r--. 1 root root 233 Jan 24 22:00 ca.db.old -rw-------. 1 root root 1675 Jan 24 21:57 ca.key -rw-r--r--. 1 root root 3 Jan 24 22:00 ca.serial.txt -rw-r--r--. 1 root root 3 Jan 24 22:00 ca.serial.txt.old -rw-r--r--. 1 root root 3768 Jan 25 00:12 elasticsearch.jks -rw-r--r--. 1 root root 2242 Jan 24 21:58 kibana-internal.crt -rw-------. 1 root root 1679 Jan 24 21:58 kibana-internal.key -rw-r--r--. 1 root root 3979 Jan 25 00:12 logging-es.jks -rw-r--r--. 1 root root 321 Jan 24 21:58 server-tls.json -rw-r--r--. 1 root root 4263 Jan 24 21:57 signing.conf -rw-r--r--. 1 root root 1184 Jan 24 22:00 system.admin.crt -rw-r--r--. 1 root root 948 Jan 24 22:00 system.admin.csr -rw-r--r--. 1 root root 3701 Jan 25 00:12 system.admin.jks -rw-r--r--. 1 root root 1704 Jan 24 22:00 system.admin.key -rw-r--r--. 1 root root 1196 Jan 24 22:00 system.logging.curator.crt -rw-r--r--. 1 root root 960 Jan 24 22:00 system.logging.curator.csr -rw-r--r--. 1 root root 1704 Jan 24 22:00 system.logging.curator.key -rw-r--r--. 1 root root 1196 Jan 24 21:59 system.logging.fluentd.crt -rw-r--r--. 1 root root 960 Jan 24 21:59 system.logging.fluentd.csr -rw-r--r--. 1 root root 1704 Jan 24 21:59 system.logging.fluentd.key -rw-r--r--. 1 root root 1196 Jan 24 21:59 system.logging.kibana.crt -rw-r--r--. 1 root root 960 Jan 24 21:59 system.logging.kibana.csr -rw-r--r--. 1 root root 1708 Jan 24 21:59 system.logging.kibana.key -rw-r--r--. 1 root root 797 Jan 25 00:12 truststore.jks Created attachment 1244163 [details]
system.admin.jks is under /etc/origin/logging
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/RHBA-2017:3049 |