Comment 14 for bug 1263934

This is still an issue for me on latest ISO #180, "nailgun_sha": "f786786894acc331a4b53b31f33e373ef95ccdfc".

I configure only Network Setup, and PXE Setup, and leave all other values by default. My expectation, as a user, is simple - if I finally click save and quit, I can be notified that NTP servers unreachable at the moment. And fuelmenu asks me what to do - go back and modify settings, or proceed further with quiting and installation of the rest, as network might not be configured yet.

Current behavior is to show error which refers to NTP/DNS issues (and it's true, I don't have connectivity yet). So I go to NTP settings, and the only option I could find is to disable NTP. I have no clue that there is a special hack in DNS submenu to prevent something on NTP side.

Finally, with NTP set to disabled, Fuel master node was deployed with ntpd service running.

Is it possible to implement the scenario I put here in second paragraph or there are some other technical issues which make this impossible or very hard to do?