[Bug 1990585] Re: cloud-net fails when DHCP slow

Chad Smith 1990585 at bugs.launchpad.net
Wed Sep 28 18:45:09 UTC 2022


Thanks for filing this bug Greg and making cloud-init and subiquity
better. It looks to me reminiscent of LP: #1990149 which is that the
nocloud-net doesn't wait for the configured nocloud datasource to be
visible, nor retry if it is not yet there.

Greg, can you confirm that the autoinstall path you are providing to
your machine is nocloud-based?

It would be helpful to either attach the tar gz from running `cloud-init
collect-logs` or minimally provide /var/log/cloud-init.log from the
system on which things failed just so we can confirm it's the same
failure mode as the other bug linked.

I'm setting the bug status to 'Incomplete' and agree it's probably a
cloud-init problem, not subiquity but please set this bug status back to
'New' for cloud-init when you'd like to have us glance again at this
issue.

** Changed in: cloud-init (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1990585

Title:
  cloud-net fails when DHCP slow

Status in cloud-init package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  Invalid

Bug description:
  During a cloud-init autoinstall with Ubunutu Focal Server 20.04, the
  attempts to retrieve the meta-data file fail immediately with no
  timeout as indicated in the cloud-init.log.  According to the system
  logs, the network does not receive an IP address until after the
  attempt to retrieve the meta-data file.  The DHCP in the facility is
  known to be a little slow.

  It is possible to retrieve the file by switching to a second virtual
  terminal and downloading it with wget (after the failure of the cloud-
  init).  It appears that the url_helper.py function reporting the
  failure to retrieve the files does not wait for any timeout period
  when the network is not yet present.

  Possible solution?  Adding a check with a timeout of a few seconds for
  the network being available before moving to download the meta-data
  and user-data files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1990585/+subscriptions




More information about the foundations-bugs mailing list