| Summary: | changing NTP server and timezone says failure even though backend timings have been changed | ||
|---|---|---|---|
| Product: | [Retired] GlusterSP | Reporter: | Raghavendra Bhat <rabhat> |
| Component: | core | Assignee: | Balamurugan Arumugam <bala> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | unspecified | CC: | fharshav, platform, shireesh, webteam |
| Target Milestone: | 3.1.2 | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Raghavendra Bhat
2010-03-30 12:08:25 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 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. |