Bug 762523 (GLUSTER-791) - changing NTP server and timezone says failure even though backend timings have been changed
Summary: changing NTP server and timezone says failure even though backend timings hav...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-791
Product: GlusterSP
Classification: Retired
Component: core
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: 3.1.2
Assignee: Balamurugan Arumugam
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-30 12:08 UTC by Raghavendra Bhat
Modified: 2010-11-29 10:36 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Raghavendra Bhat 2010-03-30 12:08:25 UTC 
In server manager goto time settings. Change the NTP server from pool.ntp.org to some other address(In my case I changed it to www.gluster.org). Change the timezone and save. It will show NTP server synchronization failed in the UI, whereas in the backend servers the timings have been changed.
Comment 1 Balamurugan Arumugam 2010-03-31 03:38:11 UTC 
Did the server use pool.ntp.org before changing into www.gluster.org?  If yes, the server time was already set by pool.ntp.org and changing into www.gluster.org will do nothing other than show error because of no valid ntp server is running in www.gluster.org
Comment 2 Harshavardhana 2010-03-31 10:44:44 UTC 
This looks simple enough, i guess we still copy the zone file information even if the ntp fails, this needs to be fixed so that we shouldn't touch the timezone unless ntp is succeeded. In the sense even if ntp fails the date is changed.
Note You need to log in before you can comment on or make changes to this bug.