Description of problem: The default chrony config now uses a new pool directive to specify NTP servers. This allows chronyd to replace unreachable servers automatically. Instead of server 0.fedora.pool.ntp.org iburst server 1.fedora.pool.ntp.org iburst server 2.fedora.pool.ntp.org iburst server 3.fedora.pool.ntp.org iburst there is just one line pool 2.fedora.pool.ntp.org iburst I'm not sure what would be the best way to handle this in anaconda. For system-config-date I've proposed a patch that displays the pool server as four individual servers with the same name and when writing back to the config file identical server names are grouped to pool directives (bug #1183624). Or there could be a pool/server flag for each entry, which could be set in a checkbox, but we would probably want to avoid too many pool entries as each one will adds 4 servers.
The installer doesn't show any NTP servers configured as it ignores the pool line. This could be confusing to the users. Here is pull request for a patch adding support for pools: https://github.com/rhinstaller/anaconda/pull/75
Proposed as a Blocker for 22-final by Fedora user vpodzime using the blocker tracking app because: No criteria matching the issue AFAICT, but the problem is that installations report there are no NTP servers configured (because they are now pools in chrony.conf) and the default configuration (the pools) is not properly parsed. All that leading to a high risk of non-working/wrong NTP configuration of the installed system.
An ACKed pull request is already available. [1] [1] https://github.com/rhinstaller/anaconda/pull/75
We don't have any criteria that would cover NTP not working, and I think that's right, it doesn't seem like something that should block release...but I'd probably vote +1 FE.
Discussed at the 2015-05-04 blocker review meeting.[0] Voted as Freeze Exception. RejectedBlocker AcceptedFreezeException - this does not violate any criterion so far as we're aware, but we would be willing to accept a tested fix during the freeze. [0] http://meetbot.fedoraproject.org/meetbot/fedora-blocker-review/2015-05-04/f22-blocker-review.2015-05-04-16.00.log.txt
Clearing F22 accepted / nominated freeze exception status as F22 has shipped, per https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers . You may nominate as an Alpha, Beta or Final freeze exception for F23 if desired using the web application - https://qa.fedoraproject.org/blockerbugs/propose_bug (though it is not currently set up for F23) - or by marking the bug as blocking AlphaFreezeException, BetaFreezeException, or FinalFreezeException.
This is in F22