Restart chronyd execution is skipped on overcloud-novacompute-0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
This problem was initially raised in https:/
Looking at an OVB overcloud_
2019-03-19 15:54:10 | RUNNING HANDLER [chrony : Restart chronyd] *******
2019-03-19 15:54:10 | Tuesday 19 March 2019 15:53:40 +0000 (0:00:00.327) 0:04:12.296 *********
2019-03-19 15:54:10 | skipping: [overcloud-
2019-03-19 15:54:10 | "changed": false,
2019-03-19 15:54:10 | "skip_reason": "Conditional result was False"
Skipping the restart causes the overcloud deployment on baremetal (an internal system) to fail because if the restart is skipped the custom servers in the configuration are never picked up and the default servers are blocked from internal systems.
See the logs copied below (from OVB - the deploy passes here):
Runs on controller nodes:
https:/
Is skipped on novacompute node:
https:/
On baremetal, the failure is shown (note that multiple ntp servers and dns servers are passed to this overcloud deployment)
https:/
Since the restart is called via a handler from an included role:
https:/
https:/
possibly, this is the result on an ansible bug in the version used:
[zuul@undercloud ~]$ ansible --version
ansible 2.6.14
config file = /etc/ansible/
configured module search path = [u'/home/
ansible python module location = /usr/lib/
executable location = /usr/bin/ansible
python version = 2.7.5 (default, Oct 30 2018, 23:45:53) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
as per the following reports:
https:/
https:/
Unsure of what importance to mark here as OVB is currently passing and baremetal - which shows a consistent error - is not yet in an pipeline.