Bug 1718327 - The 'ntpstat' validation fails with an error 'Unable to talk to NTP daemon. Is it running'
Summary: The 'ntpstat' validation fails with an error 'Unable to talk to NTP daemon. ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-validations
Version: 15.0 (Stein)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: beta
: 15.0 (Stein)
Assignee: Gaël Chamoulaud
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-07 13:30 UTC by Gaël Chamoulaud
Modified: 2019-09-26 10:51 UTC (History)
6 users (show)

Fixed In Version: openstack-tripleo-validations-10.5.1-0.20190708110407.4bdb3b6.el8ost.noarch
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-21 11:22:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 667292 0 None None None 2019-06-25 09:04:39 UTC
OpenStack gerrit 667552 0 None None None 2019-06-26 08:43:27 UTC
Red Hat Product Errata RHEA-2019:2811 0 None None None 2019-09-21 11:23:10 UTC

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


Note You need to log in before you can comment on or make changes to this bug.