This is *not* fixed in cloud-init 21.2 as reported.
It was fixed at https://github.com/canonical/cloud-init/pull/721
under commit 74fa008bfcd3263eb691cc0b3f7a055b17569f8b.
but then reverted under https://github.com/canonical/cloud-init/pull/887 .
So... marking this Triaged.
** Changed in:
This is fix-released in 0.32.
** Changed in: cloud-utils
Status: In Progress => 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/1799953
Title:
growpart does not
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Assignee: (unassigned) => Markus Schade (lp-markusschade)
--
You
Well, this was good. To recap:
1. I put up a pull request to support Vultr as a "known" EC2 clone.
https://github.com/canonical/cloud-init/pull/628
2. github users eb3095 (https://github.com/eb3095) and
ddymko (https://github.com/ddymko)
are associated with Vultr and are expecting to
Public bug reported:
The ntp (client) service file installed by the centos 7 'ntp' package is named
'ntpd' (note the d), but cloud-init's cc_ntp module identifies that
'service_name' as 'ntp'.
See below on centos 7. For centos 8, there is no 'ntp' package that I see,
it seems to have been
t; Fix Released
** Changed in: cloud-initramfs-tools (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
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/1890803
Title:
Gro
@Steven,
For such things to "just work", the platform needs to identify itself.
Without a platform identifying itself, cloud-init (or any other
software) cannot take platform-specific behavior.
The workaround is to configure the datasource_list to contain only OpenStack.
So
datasource_list:
** 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/1876139
Title:
Groovy cloud-images failing during growpart
Status in
https://code.launchpad.net/~smoser/cloud-utils/+git/cloud-utils/+merge/383431
Merge proposal to upstream cloud-utils ^
** Also affects: cloud-utils
Importance: Undecided
Status: New
** Changed in: cloud-utils
Status: New => Confirmed
** Changed in: cloud-utils
Importance:
independent of how sfdisk gets into a cloud-image, cloud-utils should identify
its dependency.
Something like https://paste.ubuntu.com/p/Fzwkm2PgqF/
** Also affects: cloud-utils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
** Merge proposal linked:
https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/+merge/379177
** Changed in: cloud-utils
Status: New => Fix Committed
** Also affects: cloud-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-utils (Ubuntu)
The first question/easiest answer is:
Why is your mirror misbehaving / Fix your mirror.
You can pass apt options to cloud-init via apt_configure module
https://cloudinit.readthedocs.io/en/latest/topics/modules.html#apt-configure
The apt flag that you're requesting
** This bug is no longer a duplicate of bug 1821102
Cloud-init should not setup ephemeral ipv4 if apply_network_config is False
for OpenStack
--
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: Expired => Triaged
** Changed in: cloud-init
Importance: Undecided => Low
--
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/1696476
Title:
** Also affects: cloud-utils
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/1834875
Title:
cloud-init growpart race with udev
Status in
output of recreate:
$ sh /tmp/recreate.sh
Read input format 'yaml' from 'bond-mtu-v1.yaml'.
Wrote output format 'sysconfig' to 'centos/sysconfig/from-v1/'
Read input format 'yaml' from 'bond-mtu-v2.yaml'.
Wrote output format 'sysconfig' to 'centos/sysconfig/from-v2/'
--- centos/sysconfig
Public bug reported:
sysconfig rendering currently just does not pay attention to the vlan
device's name. Instead it attempts to set the name to the backing
device with .* stripped from the end.
Here is an example of current master output.
The 'PHYSDEV' entry should be 'eth0', not 'infra'.
$
this is marked fix-committed in 2016. it just never got fix released.
** Changed in: cloud-init
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
Public bug reported:
cloud-init OVF datasource currently supports the OVF "ISO" transport (attached
cdrom).
It should be updated to also support the com.vmware.guestInfo transport.
In this transport the ovf environment file can be read with:
vmtoolsd "--cmd=info-get guestinfo.ovfEnv"
Things
Public bug reported:
As currently implemented, cloud-init will read either OVF CDrom *or* the
vmware IMC data.
That means if user-data is provided in the OVF environment file then it
will not be consumed at all by cloud-init.
It seems we need to either:
a.) support reading and merging these
The same basic issue is in cloud-init
and had a MP proposed at
https://code.launchpad.net/~adobrawy/cloud-init/+git/cloud-init/+merge/354680
** Merge proposal linked:
https://code.launchpad.net/~adobrawy/cloud-init/+git/cloud-init/+merge/354680
** Also affects: cloud-init
Importance:
I've marked as Invalid. Please feel free to set it back to New if you
think there is more we could do.
** 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.
I'm marking this fix-released for bionic and xenial.
The fix is available in bionic-updates and xenial-updates
and was SRU'd under bug 1795953.
If you are experiencing this problem still, re-open the bug.
Thank you.
** Changed in: cloud-init (Ubuntu Xenial)
Status: Confirmed => Fix
Hi,
I recreated the issue using the Ubuntu upstream kernel builds at
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
After launching a 18.04 instance, and then installing those kernels
and rebooting (generic_4.20.0-999.201811252100) I saw the issue.
I noticed that cloud-init's
Hi.
I added a 'linux' package task here. It seems that in bug 1551419 patches were
added
to the ubuntu kernel to do the right thing. Possibly those patches were
inadvertantly
dropped? Either way, it seems like the [Ubuntu] kernel should promise this
consistently
so that multiple consumers do
Hi,
I've moved this over to cloud-init.
I'm interested in knowing what environment you're running this in.
1. How did you build/get this image? It looks like there is a NoCloud seed
(run/result.json)
2. Where are you running the image?
3. What changes are made to /etc/cloud/cloud.cfg or
** Changed in: cloud-init
Status: Incomplete => Invalid
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
Hi,
I *do* want to fix cloud-init to accept your specific configuration
of openstack datasource. The plan is to fix that under bug 1788487.
I think you're suggesting that you are running nova-lxd as your
platform. Is that correct?
We have a couple options then to fix this:
a.) cloud-init fix
marking this as 'fix-released' on xenial, it is not a problem there as
there is a 'zfs' (virtual) package
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status: New => Confirmed
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Public bug reported:
Similar to bug 1491148, growpart does not support growing a lvm device.
It would be good if growpart in conjunction with cloud-init could
recognize that the filesystem was on a volume and grow the underlying
partition or volume group.
Related bugs:
bug 1491148: growpart
Public bug reported:
== Short summary ==
In lxd containers launched by juju,
/var/lib/cloud/seed/nocloud-net/network-config has:
has:
network:
config: disabled
That is invalid content. Cloud-init assumes content in 'network-config'
is already namespaced to 'network'. The correct content
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
** Changed in: cloud-init
Assignee: (unassigned) => Scott Moser (smoser)
** Changed in: cloud-init
Status: Confirmed => In Progress
** Changed in: apt-setup (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: apt-setup (Ubuntu Bionic)
Importance: Undecided
Public bug reported:
some changes to the jinja rendering left older versions of jinja (2.2.1, as
found in centos 6) broken.
this meant that any place we use jinja was busted, and that includes
./packages/brpm.
** Affects: cloud-init
Importance: High
Status: Confirmed
** Merge
This is fixed in Ubuntu 18.10.
cloud-init (18.3-46-gbb60f61b-0ubuntu1) cosmic; urgency=medium
* New upstream snapshot.
- ds-identify: doc string cleanup.
- OpenStack: Support setting mac address on bond. [Fabian Wiesel]
-- Ryan Harper Fri, 14 Sep 2018 16:13:19
-0500
** Also
This bug was fixed in
This bug was fixed in the package cloud-init - 18.4-0ubuntu1
---
cloud-init (18.4-0ubuntu1) cosmic; urgency=medium
* New upstream release.
- release 18.4 (LP: #1795741)
- tests: allow skipping an entire cloud_test without running.
- tests:
This bug is fixed in 18.10
This bug was fixed in the package cloud-init - 18.4-0ubuntu1
---
cloud-init (18.4-0ubuntu1) cosmic; urgency=medium
* New upstream release.
- release 18.4 (LP: #1795741)
- tests: allow skipping an entire cloud_test without running.
-
This is fixed in Ubuntu 18.10.
This bug was fixed in the package cloud-init - 18.4-0ubuntu1
---
cloud-init (18.4-0ubuntu1) cosmic; urgency=medium
* New upstream release.
- release 18.4 (LP: #1795741)
- tests: allow skipping an entire cloud_test without running.
-
This bug was fixed in the package cloud-init - 18.4-0ubuntu1
---
cloud-init (18.4-0ubuntu1) cosmic; urgency=medium
* New upstream release.
- release 18.4 (LP: #1795741)
- tests: allow skipping an entire cloud_test without running.
- tests: disable lxd tests on
This bug was fixed in the package cloud-init - 18.4-0ubuntu1
---
cloud-init (18.4-0ubuntu1) cosmic; urgency=medium
* New upstream release.
- release 18.4 (LP: #1795741)
- tests: allow skipping an entire cloud_test without running.
- tests: disable lxd tests on
This bug is believed to be fixed in cloud-init in version 18.4. 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 18.4. 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 18.4. 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 18.4. 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 18.4. 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 18.4. 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 18.4. 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 18.4. 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 18.4. 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 18.4. 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 18.4. 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 18.4. 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 18.4. 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 18.4. 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 18.4. 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 18.4. 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 18.4. 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
** Changed in: cloud-init
Status: In Progress => 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/1795741
Title:
Release 18.4
Status in cloud-init:
Fix Released
Public bug reported:
== Release Notes ==
Cloud-init 18.4 is now available.
The 18.4 release:
* Spanned just over 3 months.
* Had 17 contributors from 13 domains.
* Fixed 18 bugs.
== ChangeLog ==
- add rtd example docs about new standardized keys
- use ds._crawled_metadata instance
wont fix upstream.
based on Robert's aggrement.
** 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 cloud-init.
https://bugs.launchpad.net/bugs/1793193
Title:
A
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
** 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/1731619
Title:
Support chrony as a client for ntp
Status in
** Changed in: cloud-init (Ubuntu)
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/1784713
Title:
cloud-init profile.d files use bash-specific
** Changed in: cloud-init (Ubuntu Bionic)
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/1766401
Title:
full config file wiped after
** Changed in: cloud-init (Ubuntu Bionic)
Importance: Undecided => Low
** Changed in: cloud-init (Ubuntu Bionic)
Status: New => 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 (Ubuntu)
Status: Confirmed => Fix Committed
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Public bug reported:
Part of "make OVH work right" was brought up by Tobias in
https://code.launchpad.net/~tobijk/cloud-init/+git/cloud-init/+merge/354752
After that, though we still see some warnings in the logs that is
attached.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package:
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Importance: Undecided => Medium
** Also affects: cloud-init (Ubuntu Cosmic)
Importance: Medium
Assignee: Pengpeng Sun
There is not really anything more I can do on this bug. Essentially it
is fallout of a decision made by digitalocean to configure cloud-init in
a certain way that limited your ability to move that image to GCE or
another cloud platform.
I do not mean to imply that Digital Ocean's change was
Public bug reported:
cloud-init (ds-identify) cannot positively identify a vmware cloud
environment where customization data will be present. In order to avoid
false positive, it requires the user to set
'disable_vmware_customization: false' in a config file.
That is a very bad user experience,
Public bug reported:
When a datasource is instantiated it is passed in Init.cfg as the 'sys_cfg'.
But then when 'distro' property is referenced, it has the side effect
of:
system_config = self._extract_cfg('system')
if self.datasource is not NULL_DATA_SOURCE:
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Importance: Undecided => Low
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Assignee: (unassigned) => Scott Moser (smoser)
--
You
fixed in cosmic at 18.3-18-g3cee0bf8-0ubuntu1
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug
x/citest/lib/python3.5/site-packages/pylxd/client.py",
line 103, in _assert_response
raise exceptions.NotFound(response)
** Affects: cloud-init
Importance: Medium
Assignee: Scott Moser (smoser)
Status: Confirmed
** Changed in: cloud-init
Status: New => Confirmed
** Changed
** Changed in: cloud-init (Ubuntu Zesty)
Status: Confirmed => Won't Fix
** Changed in: cloud-init (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Invalid
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
marking invalid. it seems like you figured out it was bad user-data.
re-open and explain if that is not the case.
** 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
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Released
** Changed in: cloud-init
Importance: Undecided => Low
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in:
Public bug reported:
The last successful copr build was 18.3+7.g802c1d51-1.el7
18.3+9.g2e62cb8a-1.el7 is currently failing for
https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/build/775930/
epel-6-i386
epel-6-x86_64
fedora-rawhide-i386
fedora-rawhide-x86_64
Public bug reported:
I couldn't figure out how to login to launchpad staging, so i'm using
this.
** 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 cloud-init.
Public bug reported:
cloud-init-integration-lxd-b test 200 failed.
Looking at the console log at [1] shows
boot instance encountered error: ssh: after 120s instance is not reachable
at 2018-06-26 11:23:47,693 which was indeed 120 seconds after starting the
salt minion test.
The summary of the
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in cloud-init in version 18.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 18.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 18.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 18.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 18.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 18.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 18.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 18.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 18.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 18.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 18.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 18.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 18.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 18.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 18.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 18.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 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix
This bug is believed to be fixed in cloud-init in version 18.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
1 - 100 of 930 matches
Mail list logo
