Description of problem: Only 2.fedora.pool.ntp.org is listed for the NTP servers ... if user leaves this alone and continues the install, then opens system-config-date after installing and rebooting, no NTP servers are listed Version-Release number of selected component (if applicable): Fedora 22 Mate Spin How reproducible: 100%
Also, after manually setting the system time, it appears that the next time the NTP client tries to update it is resetting my time to midnight tomorrow....
Please attach the log files from the installation, available in /var/log/anaconda in the installed system.
Created attachment 1033851 [details] anaconda.log
Created attachment 1033852 [details] ifcfg.log
Created attachment 1033855 [details] journal.log
Created attachment 1033856 [details] packaging.log
Created attachment 1033857 [details] program.log
Created attachment 1033858 [details] storage.log
I have attached the requested logs. The following additional files exist but are empty: ks-script-kPtnB3.log ks-script-lD4EgA.log ks-script-qOK0Su.log
It looks like everything is working as expected, mostly. Chrony, the NTP server, added a configuration directive for pools. So /etc/chrony.conf in the live environment just contains this: pool 2.fedora.pool.ntp.org iburst instead of three or four separate lines for servers. This config is copied over to the installed system, so the problem is just that system-config-date doesn't know what to do with pool directives. As for the time jumping to midnight tomorrow, is the time zone set correctly? If so, that might be a separate bug against chrony.
Prior versions of fedora listed the following servers: 0.fedora.pool.ntp.org 1.fedora.pool.ntp.org 2.fedora.pool.ntp.org 3.fedora.pool.ntp.org So it seems 2.fedora.pool.ntp.org works as both a "server" and as a "pool". I think it's rather confusing to list a seemingly arbitrary numbered pool this way? It looks like it belongs in a list, but it doesn't. Is there any better subdomain naming that could be used for this? As for the midnight issue, I am not able to reproduce at this time, so perhaps the issue was fixed, or perhaps I got something mixed up.
(In reply to April from comment #11) > I think it's rather confusing to list a seemingly arbitrary numbered pool > this way? It looks like it belongs in a list, but it doesn't. Is there any > better subdomain naming that could be used for this? That's a question for the chronyd maintainers. Anaconda is just the messenger in this.
The 2.fedora.pool.ntp.org name is used because it's currently the only name returning IPv6 addresses. This will likely change in the future. This is a duplicate of bug #1183624. There is a patch which adds some support for the pool directive, but it wasn't applied/reviewed yet.
*** This bug has been marked as a duplicate of bug 1183624 ***