Bug 1310490
| Summary: | Network Time Servers set in anaconda do not appear under system-config-date after install | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jia Yuan Lo <jylo06g> |
| Component: | system-config-date | Assignee: | Nils Philippsen <nphilipp> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | g.kaviyarasu, jonathan, jylo06g, nphilipp, sheldon.corey, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-10-14 15:46:11 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: | |||
|
Description
Jia Yuan Lo
2016-02-22 01:48:28 UTC
I uses chrony, hence does not care about or fail out on lack of ntp. Hmm... I must have miss the point that chrony is now default daemon for syncing time. Ok, maybe the bug's focus need to be change a little (or maybe closed). The thing is that I notice that configuration that was made in anaconda such as adding an ntp server other than fedora.pool.ntp.org and after install it will not end up at system-config-date. Ok I will change the title to reflect the change of focus from missing ntp package to anaconda improper configuration of network time syncing... (In reply to Jia Yuan Lo from comment #2) > Hmm... I must have miss the point that chrony is now default daemon for > syncing time. That was five years ago. https://fedoraproject.org/wiki/Features/ChronyDefaultNTP > Ok I will change the title to reflect the change of focus from missing ntp > package to anaconda improper configuration of network time syncing... Anaconda is configuring chrony just fine, in chrony.conf. Ok I can confirm anaconda does add the network time servers to /etc/Chrony.conf But system-config-date do not show the added servers... /.\ I think I getting very exhausting right now. So this is system-config-date fault or is the default by design (not showing network time servers from anaconda)? Sorry for the late reply. System-config-date should detect chrony and use /etc/chrony.conf if present. Do you still have this issue? Can you run it from the command line and see if there are any error messages? ah yes, I also forget about this... anyway back then is somewhat confusing but what I am trying to say is this line pool 2.fedora.pool.ntp.org iburst inside default /etc/chrony.conf is not showing up in system-config-date... For example, only servers added later on in system-config-date will show up themselves in the form of server sg.pool.ntp.org I am not implying the sync is not working, just that 2.fedora.pool.ntp.org configured by anaconda seems to be ignored by system-config-date but syncing still works... Hi! I don't actively develop system-config-date anymore, i.e. I don't have the time to work on this feature myself. I've announced this on the Fedora devel list a couple of weeks ago(*) but so far nobody has come forth who'd pick up this package. Accordingly, I'll close this bug as a duplicate of the feature request to support pool directives. (*): https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/BIV6Z2LN2LCO4I6LE636PPWOINUETV3S/ *** This bug has been marked as a duplicate of bug 1377121 *** |