This was resolved in upstream cloud-init in 23.3, which moved
Before=systemd-user-sessions.service from cloud-init.service to cloud-
config.service to resolve LP: #2013403. That change was temporarily
reverted on Ubuntu due to a snap-related performance regression. On
Noble and newer, the snap regression has been resolved, and with that
resolution the fix for this problem has been re-introduced.
Closing.
** Changed in: cloud-init (Ubuntu)
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/1633453
Title:
ssh is started before cloud-init completed
Status in cloud-init:
Expired
Status in cloud-init package in Ubuntu:
Fix Released
Bug description:
Hello,
Previously, ssh was only started after cloud-init finished configuring
the host. In Yakkety, it is quite easy to log into a machine with SSH
while cloud-init is still running. This enables to log as root or to
run apt-get update while cloud-init is still finishing to write system
configuration. This is annoying with automation.
With Xenial, this never happens, but with Yakkety, this happens all
the time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1633453/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
