Xenial installer hangs for a long time with "Setting up the clock" message on IPv6-only systems

[Frode Nordahl]

When installing on a IPv6-only system the installer hangs for a long time on "Setting up the clock" step with "Getting the time from a network time server...". Hitting "Cancel" have no effect.

Eventually the installer continues, I would guess after a hard timeout.

This is a regression and it has surfaced during the last few days.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Saverio Proto (zioproto)]

I confirm. I noticed that opening an alternate shell and giving commands will unlock immediately the operation.

Even if it makes no sense I can reproduce it.

The installation is blocked at "getting the time from a network time server " and typing return on the cancel button has no effect.

I do CTRL+ALT+F2. I click enter to activate a new console. As soon as I type a command there like "ps" or "ls" the installation immediately continues on the F1 console.

Note that my system is dual stack IPv4 and IPv6

[PSalazar (ubuntu-5-psalazar)]

Same here, the installer freezes at "Setting up the clock" with dual stack ipv4 / ipv6.
Activating a second console also seems to persuade the installer to resume the process.

[Julian (digitalsy)]

Confirmed here, having the same issue trying to build a VM from ubuntu-16.04.2-server-amd64.iso via cobbler.

Hangs at "setting up clock from network time server". Switching to an alternate console also magically unblocks this. Do we have a timeline for fixing this? This is preventing automation from working at my job.

[rogue780 (shawn-haggard)]

I'm also experiencing the same issue. Unfortunately, it's presenting during unattended preseed installations, which makes is more difficult to deal with.

[Andreas Ntaflos (daff)]

Definitely still a problem with 16.04, especially with unattended installs.

[Steve Heckman (steve-heckman)]

Confirmed here as well on unattended installs.

[Andreas Ntaflos (daff)]

We work around this problem by disabling the clock setup during installation:

d-i clock-setup/utc boolean true
d-i time/zone string Europe/Vienna
d-i clock-setup/ntp boolean false
d-i clock-setup/ntp-server string pool.ntp.org

And after installation Puppet ensures chrony or ntpd are running.