Bug 1552024 - Add NTP configuration to gluster-colonizer
Summary: Add NTP configuration to gluster-colonizer
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-colonizer
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.3.1 Async
Assignee: Ramakrishna Reddy Yekulla
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On:
Blocks: 1542835
TreeView+ depends on / blocked
 
Reported: 2018-03-06 10:59 UTC by Ramakrishna Reddy Yekulla
Modified: 2018-04-05 07:28 UTC (History)
6 users (show)

Fixed In Version: gluster-colonizer-1.0.4-2.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-12 12:07:19 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0477 0 normal SHIPPED_LIVE RHEA: new package: gluster-colonizer 2018-03-12 18:12:47 UTC

Description Ramakrishna Reddy Yekulla 2018-03-06 10:59:55 UTC 
Description of problem:

Add NTP configuration to gluster-colonizer 


Version-Release number of selected component (if applicable):

1.0.4-1

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

ntpd service needs to be running in the colonizer nodes.

Expected results:


Additional info:
Comment 2 Dustin Black 2018-03-06 21:01:18 UTC 
Upstream merge commit includes logic to collect NTP server info from user and configure the chronyd service appropriately.

https://github.com/gluster/gluster-colonizer/commit/b78b284af5b1cf23a5d62d00050d30568dc0d36d
Comment 5 Nag Pavan Chilakam 2018-03-07 19:21:15 UTC 
ntp is being configured now with 1.0.4-2 
(see screenshots)

hence moving to verified
Comment 6 Nag Pavan Chilakam 2018-03-07 19:33:33 UTC 
logs at https://drive.google.com/open?id=11OcTp8pUA9VgsYlgEgAhceyPUjIKKqrq
Comment 9 errata-xmlrpc 2018-03-12 12:07:19 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-2018:0477
Note You need to log in before you can comment on or make changes to this bug.