| 2019-10-28 22:20:08 |
Nikita Belov |
description |
I have an error with selinux at ansible script after deploy overcloud. I get this error:
2019-10-27 22:37:27,750 p=210 u=mistral | TASK [chrony : Force chronyd restart] ******************************************
2019-10-27 22:37:27,751 p=210 u=mistral | fatal: [overcloud-controller-no-ceph-2]: FAILED! => {"changed": false, "msg": "Unable to restart service chronyd: Job for chronyd.service failed because the control process exited with error code. See \"systemctl status chronyd.service\" and \"journalctl -xe\" for details.\n"}
2019-10-27 22:37:27,927 p=210 u=mistral | fatal: [overcloud-controller-no-ceph-0]: FAILED! => {"changed": false, "msg": "Unable to restart service chronyd: Job for chronyd.service failed because the control process exited with error code. See \"systemctl status chronyd.service\" and \"journalctl -xe\" for details.\n"}
2019-10-27 22:37:28,122 p=210 u=mistral | fatal: [overcloud-controller-no-ceph-1]: FAILED! => {"changed": false, "msg": "Unable to restart service chronyd: Job for chronyd.service failed because the control process exited with error code. See \"systemctl status chronyd.service\" and \"journalctl -xe\" for details.\n"}
After that I manually do sudo fixfiles -f relabel at all hosts, then rerun deploy with --config-download-only.
Release: train. |
I have an error with selinux at ansible script after deploy overcloud. I get this error:
2019-10-27 22:37:27,750 p=210 u=mistral | TASK [chrony : Force chronyd restart] ******************************************
2019-10-27 22:37:27,751 p=210 u=mistral | fatal: [overcloud-controller-no-ceph-2]: FAILED! => {"changed": false, "msg": "Unable to restart service chronyd: Job for chronyd.service failed because the control process exited with error code. See \"systemctl status chronyd.service\" and \"journalctl -xe\" for details.\n"}
2019-10-27 22:37:27,927 p=210 u=mistral | fatal: [overcloud-controller-no-ceph-0]: FAILED! => {"changed": false, "msg": "Unable to restart service chronyd: Job for chronyd.service failed because the control process exited with error code. See \"systemctl status chronyd.service\" and \"journalctl -xe\" for details.\n"}
2019-10-27 22:37:28,122 p=210 u=mistral | fatal: [overcloud-controller-no-ceph-1]: FAILED! => {"changed": false, "msg": "Unable to restart service chronyd: Job for chronyd.service failed because the control process exited with error code. See \"systemctl status chronyd.service\" and \"journalctl -xe\" for details.\n"}
At nodes:
Oct 28 00:08:13 overcloud-controller-no-ceph-0 chronyd[19217]: chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 +DEBUG)
Oct 28 00:08:13 overcloud-controller-no-ceph-0 chronyd[19217]: Frequency -15.088 +/- 0.379 ppm read from /var/lib/chrony/drift
Oct 28 00:08:13 overcloud-controller-no-ceph-0 chrony-helper[19219]: /usr/libexec/chrony-helper: line 144: /var/run/chrony-helper/lock: Permission denied
Oct 28 00:08:13 overcloud-controller-no-ceph-0 chrony-helper[19219]: flock: 100: Bad file descriptor
Oct 28 00:08:13 overcloud-controller-no-ceph-0 chrony-helper[19219]: Failed to lock /var/run/chrony-helper
Oct 28 00:08:13 overcloud-controller-no-ceph-0 systemd[1]: chronyd.service: control process exited, code=exited status=1
Oct 28 00:08:13 overcloud-controller-no-ceph-0 chronyd[19217]: chronyd exiting
Oct 28 00:08:13 overcloud-controller-no-ceph-0 systemd[1]: Failed to start NTP client/server.
Oct 28 00:08:13 overcloud-controller-no-ceph-0 systemd[1]: Unit chronyd.service entered failed state.
Oct 28 00:08:13 overcloud-controller-no-ceph-0 systemd[1]: chronyd.service failed.
After that I manually do sudo fixfiles -f relabel at all hosts, then rerun deploy with --config-download-only.
Release: train. |
|
