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
** Changed in: cloud-init
Status: Fix Committed => 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/1088101
Title:
Please add informations in /doc/README,
Status
** Changed in: cloud-init
Status: Fix Committed => 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/1799674
Title:
tools/build-on-freebsd is outdated and can be
** Changed in: cloud-init
Status: Fix Committed => 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/1839854
Title:
CloudStack provider cannot determine correct
** Changed in: cloud-init
Status: Fix Committed => 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/1889545
Title:
cc_users_groups docs should note that its
** Changed in: cloud-init
Status: Fix Committed => 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/1854863
Title:
Can't fork over SSH
Status in cloud-init:
Fix
** Changed in: cloud-init
Status: Fix Committed => 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/1962150
Title:
status symlink non-atomicity traceback with
** Changed in: cloud-init
Status: Fix Committed => 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/1740937
Title:
Support Ansible
Status in cloud-init:
Fix
Fix released in 20.1
** Changed in: cloud-init
Status: Fix Committed => 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/1785275
Title:
cloud-init pre-networking
** Changed in: cloud-init
Status: Fix Committed => 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/1845552
Title:
ssh_util: fails to parse sshd_config when config
Fixed in e10ad2d7854b87024b5d051db50166125fce2279
** Changed in: cloud-init
Status: Confirmed => 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/1720844
Title:
These targets no longer exist in the makefile, and these days we use tox
rather than the Makefile.
Closing
** Changed in: cloud-init
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
This was resolved in the aforementioned pull request with the addition
of writing deferred files.
** 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.
** Changed in: cloud-init
Status: Fix Committed => 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/1383510
Title:
Documentation improvements needed
Status in
** Changed in: cloud-init
Status: Fix Committed => 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/2003363
Title:
Systemd-networkd generated configuration is wrong
** Changed in: cloud-init
Status: Fix Committed => 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/2009746
Title:
dpkg-reconfigure cloud-init: yaml.load errors
** Changed in: cloud-init
Status: Incomplete => Invalid
** Changed in: subiquity
Status: New => Invalid
--
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/1988768
Title:
Public bug reported:
On boot, cloud-init is able to pass cloud-config via userdata_raw, a
useful feature when testing behavior on a datasource that doesn't have
its own way of retrieving userdata.
system_info:
datasource:
None:
userdata_raw: "#cloud-config\ngrub_dpkg:\n enabled:
NixOS is not supported by upstream cloud-init. Please contact your
distro maintainers for a fix.
Regarding ISC's client support, this is a real issue and plans for a
replacement are under way.
** Changed in: cloud-init
Status: New => Invalid
--
You received this bug notification because
Public bug reported:
A common way of distributing keys is by hosting them at a URL for
download. This is not currently supported by the apt configure module,
and would be a simple addition.
Example usage (note the suggested 'keyurl' key)
apt:
sources:
source1:
keyurl:
Public bug reported:
cloud-init has undocumented support for declaring datasources using the
kernel commandline. This proves valuable in edge case scenarios as a
workaround when ds-identify detection is broken.
This behavior is inconsistently supported across datasources, several of
which[1] do
Resetting machine-id at runtime would be a pretty big break from current
expectations, and correct implementation would require foreknowledge of
services using machine-id that are provided in an image. The potential
for bugs due to implementation complexity, potential for boot speed
regression
** Also affects: snapd
Importance: Undecided
Status: New
--
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/1988499
Title:
Snap prevents repartitioning Azure resource disk
> Separately we really ought to port networkd from dbus communication to
varlink such that it can be used safely on critical boot path. The rest
of the Systemd critical components are already using varlink.
+1
> did you mean to mark Ubuntu(Systemd) as affected?
Yes, I'll update that thanks.
Public bug reported:
Cloud-init is seeing intermittent failures while running `netplan
apply`, which appears to be caused by a missing resource at the time of
call.
The symptom in cloud-init logs looks like:
Running ['netplan', 'apply'] resulted in stderr output: Failed to
connect system bus:
Public bug reported:
Currently when duplicate mac addresses are detected, cloud-init dies.
While duplicate macs are typically corner cases, there are cases when
they can be valid[1].
Consider this example[2]. After bonding two interfaces, the interfaces
were left with duplicate mac addresses.
** Changed in: cloud-init
Status: Fix Released => Confirmed
--
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/1844191
Title:
azure advanced networking sometimes triggers
Hi Jens,
Thank you for reporting! I added the server autoinstaller project
(subiquity) to this bug, since it drives cloud-init configuration during
installs.
> Now to the real issue: Giving all the data includes hostname, user /
pass, ssh key. They will be set up correctly. However, when the
** Also affects: cloud-init
Importance: Undecided
Status: New
** Also affects: subiquity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
> This is only possible for autoinstall. This bugreport is partly about
why disabling grub_dpkg in user-data better be the default for both
manual- and auto-install.
Since the requested behavior change can be driven by different user-data
from subiquity, I think this doesn't require cloud-init
** Also affects: subiquity
Importance: Undecided
Status: New
--
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/1993503
Title:
grub_dpkg writes wrong device into debconf
Modern supported "EL" derivatives appear to have this flag (tested on
centos8-stream and centos9-stream).
If this is believed to still be an issue, please reopen.
** Changed in: cloud-init
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member
** Also affects: lxd
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Invalid
--
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/1991051
Title:
Since the issue has been narrowed down to casper-md5check, which is out
of scope of cloud-init, I'm marking the cloud-init side of this bug as
"Invalid", since there is nothing actionable to do to in cloud-init to
resolve this bug, and the plans to increase debugging transparency that
Chad
** Changed in: cloud-init
Status: Fix Released => Fix Committed
--
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/1988157
Title:
cloud-init crash on EC2 datasources when IMDS
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: New => Fix Released
--
You received this bug notification because you are a member of
Public bug reported:
Summary: Release 22.3
Further information:
== Release Notes ==
Cloud-init release 22.3 is now available
The 22.3 release:
* spanned about 3 months
* had 25 contributors from 27 domains
* fixed 18 Launchpad issues
Highlights:
== Changelog ==
- integration tests:
** 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/1799544
Title:
package-update-upgrade-install does not work on Gentoo
Public bug reported:
A bug[1] was filed downstream for this, and reported upstream in #cloud-
init IRC by Sam (Gentoo maintainer).
This causes build failure on Gentoo/OpenRC, which is carrying a
downstream workaround[2] for now.
It looks like the upstream installation method for init scripts
Public bug reported:
Originally reported in IRC, there appears to be a bug in cloud detection
for VMware
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of
Public bug reported:
Summary: Release 22.2
Further information:
== Release Notes ==
Cloud-init release 22.2 is now available
The 22.2 release:
* spanned about 3 months
* had 28 contributors from 31 domains
* fixed 1 Launchpad issues
Highlights:
== Changelog ==
- Fix test due to caplog
cloud-init.
Regards,
Brett Holman
** Changed in: cloud-init
Status: Incomplete => Invalid
--
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/1971105
Title:
cloud-init not initi
The statement is intended to claim that it is in widespread use and is
widely supported, which is true. "Industry standard" is vague and open
to interpretation (as you've demonstrated). In this case, and commonly
in English usage, "industry standard" does not imply the existence of a
standards
This bug is believed to be fixed in cloud-init in version 22.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of
This bug is believed to be fixed in cloud-init in version 22.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: In Progress => Fix Released
--
You received this bug notification because you are a member
This bug is believed to be fixed in cloud-init in version 22.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of
This bug is believed to be fixed in cloud-init in version 22.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 22.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: New => Fix Released
--
You received this bug notification because you are a member of
Public bug reported:
== Release Notes ==
Cloud-init release 22.1 is now available
The 22.1 release:
* spanned about 3 months
* had 27 contributors from 29 domains
* fixed 8 Launchpad issues
Highlights:
== Changelog ==
- sources/azure: report ready in local phase (#1265) [Chris
I just noticed the date on this, please disregard previous comments.
This showed up in the triage bug queue as NEW for some reason and I
failed to note the date.
It seems this was resolved in a previous release, please reopen if
further attention to this issue is required.
** Changed in:
I don't think this has anything to do with "_unquote()", which is used
for parsing the file.
The behavior you are seeing is due to shlex.quote()[1][2], which
produces POSIX shell tokens:
> shlex.quote(s)
>
> Return a shell-escaped version of the string s. The returned value is a
> string that
Thanks for the feedback. Since it sounds like there is already a
workable solution in place, I'm going to close this. If you think
further action is required please reopen and communicate what that would
be.
** Changed in: cloud-init
Status: New => Invalid
--
You received this bug
93 matches
Mail list logo
