yahoo-eng-team team mailing list archive

[Chad Smith <2008727@xxxxxxxxxxxxxxxxxx>]

Upstream commit landed to avoid this automatically suggesting that OpenStack datasource may be applicable by default on Bare metal. This is probably not the majority of cases for bare metal openstack detection for bare metal should only be active if it is explicitly set by either kernel cmdline by providing ci.ds=OpenStack parameter or in the image itself with a file in /etc/cloud/cloud.cfg.d/90-somename.cfg containing a explicitly:
datasource_list: [OpenStack].


Related upstream commit. https://github.com/canonical/cloud-init/commit/d1ffbea556a06105d1ade88b4143ad43f53692c4

This is released to Lunar now as 23.1.1 and will make it back to Bionic,
Focal, Jammy, Kinetic in our next SRU in a week or two.

** Summary changed:

- [Lunar/Desktop] 5 min boot delay due cloud-init-local.service
+ [Lunar/Desktop] 5 min boot delay on bare metal due cloud-init-local.service

** Changed in: cloud-init
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/2008727

Title:
  [Lunar/Desktop] 5 min boot delay on bare metal due cloud-init-
  local.service

Status in cloud-init:
  Fix Released

Bug description:
  I run lunar for a while now (upgraded from Jammy through `do-release-upgrade -d`) and since I do some Subiquity development often, I do have cloud-init setup, for a while as well.
  Friday 24th, after a regular `apt update && apt upgrade` my laptop boot time increased by surprising 5 min, at a first glance it appears to be due cloud-init-local.service waiting for network activity in the Ethernet port, which I rarely use.

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