Bug 1718327

Summary: The 'ntpstat' validation fails with an error 'Unable to talk to NTP daemon. Is it running'
Product: Red Hat OpenStack Reporter: Gaël Chamoulaud <gchamoul>
Component: openstack-tripleo-validationsAssignee: Gaël Chamoulaud <gchamoul>
Status: CLOSED ERRATA QA Contact: Amit Ugol <augol>
Severity: high Docs Contact:
Priority: high    
Version: 15.0 (Stein)CC: beth.white, jjoyce, jrist, jschluet, slinaber, tvignaud
Target Milestone: betaKeywords: Triaged
Target Release: 15.0 (Stein)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-validations-10.5.1-0.20190708110407.4bdb3b6.el8ost.noarch Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-21 11:22:59 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:

Description Gaël Chamoulaud 2019-06-07 13:30:47 UTC
Now that we use chrony we have to update the ntpstat validation to work with both options as this
will currently fail saying that no NTP server is found. 


```
(undercloud) [stack@undercloud ~]$ /usr/bin/run-validations.sh --validation-name ntpstat
Task 'ntpstat : Run ntpstat' failed:
Host: overcloud-novacompute-0
Message: Command `ntpstat` exited with code: 2: non-zero return code

stderr:
    Unable to talk to NTP daemon. Is it running?

Task 'ntpstat : Run ntpstat' failed:
Host: overcloud-controller-0
Message: Command `ntpstat` exited with code: 2: non-zero return code

stderr:
    Unable to talk to NTP daemon. Is it running?

Failure! The validation failed for all hosts:
* overcloud-controller-0
* overcloud-novacompute-0
```

Comment 7 errata-xmlrpc 2019-09-21 11:22:59 UTC
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/RHEA-2019:2811