Bug 2034189

Summary:	Validation if NTP/Chrony is configured during at initial stage of deployment procedure
Product:	Red Hat OpenStack	Reporter:	Shailesh Chhabdiya <schhabdi>
Component:	openstack-tripleo-heat-templates	Assignee:	OSP Team <rhos-maint>
Status:	CLOSED ERRATA	QA Contact:	David Rosenfeld <drosenfe>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.2 (Train)	CC:	apevec, jamsmith, lhh, mburns, tkajinam
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-11.6.1-2.20220116004909.64b2e88.el8ost	Doc Type:	Bug Fix
Doc Text:	This update adds an NTP validation step to deployments. To include the validation step in your deployment, include the argument `--ntp-server <ntp_server_name>` in the `openstack deploy` command. Replace <ntp_server_name> with the name of a valid, reachable NTP server. + If director cannot reach the specified NTP server, the deployment fails. This validation prevents synchronization failures from occurring later in the deployment.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-23 22:30:16 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:
Bug Depends On:
Bug Blocks:	2034095

Description Shailesh Chhabdiya 2021-12-20 11:14:02 UTC

Description of problem:
Requesting for a validation to make sure NTP/chrony is set and working during initial stage of deployment

Version-Release number of selected component (if applicable):
RHOSP16.1/16.2

Actual results:
NTP/Chrony is ignored if not reachable 

Expected results:
NTP/Chrony should be reachable and must be validated in initial stage of deployment

Comment 2 Alex Schultz 2021-12-21 23:41:31 UTC

This was a regression from OSP13 and is not an RFE. We expect the deployment to fail if NTP servers are unavailable at deployment time because time synchronization is a requirement.

Comment 6 David Rosenfeld 2022-02-02 19:58:10 UTC

Deployed an overcloud that included --ntp-server {unreachable ntp server} in the deploy command. The deploy failed with this in log:

2022-02-02 19:27:38.751438 | 52540028-c26d-19ee-966f-000000001a62 |      FATAL | Ensure system is NTP time synced | controller-0 | error={"changed": true, "cmd": ["chronyc", "waitsync", "30"], "delta": "0:04:50.292591", "end": "2022-02-02 14:27:38.720697", "msg": "non-zero return code", "rc": 1, "start": "2022-02-02 14:22:48.428106", "stderr": "", "stderr_lines": [], "stdout": "try: 1, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 2, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 3, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 4, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 5, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 6, refid: 00000000, correction: 0.000000000, skew: 0.000\

above shows that chronyc waitsync has been added for unreachable ntp servers.

Comment 12 Alex Schultz 2022-03-07 05:31:33 UTC

I (alex.g.schultz) am not the same person as aschultz was and should not have been tagged for "needinfo".

Best Regards,
A different Alex Schultz

Comment 18 errata-xmlrpc 2022-03-23 22:30:16 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 (Moderate: Red Hat OpenStack Platform 16.2 (openstack-tripleo-heat-templates) security update), 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/RHSA-2022:0995