This bug is believed to be fixed in cloud-init in version 20.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 20.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 20.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
** 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/1853160
Title:
uptime code does not work on FreeBSD with python
Public bug reported:
== Release Notes ==
Cloud-init release 20.1 is now available
The 20.1 release:
* spanned about 9 weeks
* had 19 contributors from 19 domains
* fixed 13 Launchpad issues
Highlights:
- Python 2 support has been dropped
- A number of FreeBSD improvements landed
- Two
Public bug reported:
The default configuration should work for developers, and therefore
shouldn't assume write access to a directory that is (a) outside of the
cloud-init tree, and (b) generally requires root privs to create in the
first place.
The specific error:
2020-02-18 18:11:21,652 -
Public bug reported:
It should appear on
https://cloudinit.readthedocs.io/en/latest/topics/modules.html but it
doesn't.
If I run `tox -e doc` locally, it _is_ included, which suggests this is
an issue with our ReadTheDocs generation specifically, not the docs in
general.
** Affects: cloud-init
Hi Vasili,
>From a cloud-init perspective, there isn't anything we can do so I'm
going to move the upstream task to Invalid too. I'm afraid I don't
really have any advice on how to proceed, as this appears to be a
hypervisor or cloud issue.
Dan
** Changed in: cloud-init
Status: New =>
Hi Nicklas,
Thanks for the extra info! This sounds like an issue with blkid (and/or
your system), rather than a cloud-init bug. I've added a util-linux bug
task (which is the package that ships blkid), and I'm going to mark the
cloud-init bug task Invalid as I don't believe that there's
Hi!
I believe this is an issue with ifupdown, rather than cloud-init. As
such, I've added an ifupdown task and marked cloud-init's task as
Invalid. If it's determined that we won't fix this in ifupdown, then
please move the cloud-init task back to New and we can consider working
around this in
Hi! I don't think this is a bug with cloud-init, so I'm going to mark
this as Invalid. Please file a bug against Ubuntu generally if you
still are seeing this issue.
Thanks!
Dan
--
Google Translate / Traductor de google:
¡Hola! No creo que esto sea un error con cloud-init, así que voy a
*** This bug is a duplicate of bug 1834190 ***
https://bugs.launchpad.net/bugs/1834190
Hi Anisse,
Thanks for using cloud-init, and for taking the time to file a bug! I'm
going to mark this as a duplicate of bug 1834190, as the source of the
issue is snapd.seeded being unacceptably slow.
** Also affects: cloud-init (Ubuntu Eoan)
Importance: Critical
Assignee: Dan Watkins (daniel-thewatkins)
Status: In Progress
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Disco)
Importance: Undecided
Go team!
** 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/1722959
Title:
Implement Key-Value Pair Telemetry for
The lack of events is not the issue. We see all the events from the
kernel that we would expect to see during a resize, and we see the same
number (and type) of events on both the passing and the failing
instances.
The problem is that if udev processes the sda1 event first then, at
least some of
Public bug reported:
What does "across an instance" mean?
** Affects: cloud-init
Importance: Undecided
Assignee: Dan Watkins (daniel-thewatkins)
Status: New
** Changed in: cloud-init
Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)
--
You rece
This looks like an incorrect pylint warning to me. `schema` is in the
module namespace in test_snap.py, but `schema = schema` binds the value
of the module-level `schema` to `schema` on the test class. This is
required because self.assertSchemaValid refers to `self.schema`.
I'm going to look at
Hey Chris,
We're waiting for the debug information that Ryan requested in comment
#1 to be able to move this forward. I'm setting this back to
Incomplete, please move it to New once you have attached that
information.
Thanks!
Dan
** Changed in: cloud-init
Status: Expired => Incomplete
Hi Pedro,
Thanks for using cloud-init and for taking the time to file this bug!
Per the cloud-init docs[0], the cc_resolv_conf module is not supported
on Ubuntu, and it therefore doesn't run in the default configuration.
This is because systemd-resolved is used on Ubuntu systems, so
configuring
Public bug reported:
Its absence makes debugging issues with atomic file writes difficult
(for example, bug 1841182).
** Affects: cloud-init
Importance: Low
Status: Triaged
** Changed in: cloud-init
Status: New => Triaged
** Changed in: cloud-init
Importance: Undecided
Public bug reported:
With the introduction of DHCP classless static route parsing in our
ephemeral DHCP code, we've started seeing an additional traceback on
Oracle during DataSourceOpenStackLocal:
Traceback (most recent call last):
File
to be a systemd issue, I'm going to mark the cloud-
init task Invalid. Feel free to move it back to New if you believe this
is a mistake!)
** Changed in: cloud-init
Status: In Progress => Invalid
** Changed in: cloud-init
Assignee: Dan Watkins (daniel-thewatkins) => (unassigned)
--
You re
Based on IRC conversation, I don't believe this is a cloud-init bug.
Please set the task back to New if I'm mistaken!
** Changed in: cloud-init
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
YAML has native support for boolean values, and YAML has been around
long enough that it's reasonable to expect people to know how to write
it.
We should phase out accepting multiple string values ("yes", "1",
"true", "on" for True; "no", "0", "false", "off" for False) in
On Fri, Aug 09, 2019 at 02:14:32PM -, Scott Moser wrote:
> I know I've talked to Chad and Ryan before about this, but I kind of
> see the plethora of values that are accepted as bad design (my bad
> design).
> Ultimately, I'd rather deprecate and remove that functionality than
> extend it to
Public bug reported:
At the moment, there are some places where we do something along the
lines of `bool_thing = self.ds_cfg.get("cfg_option", False)`. This is
incorrect, because specifying anything other than the empty string in
configuration (such as "no" or "false") will result in a True-ish
Public bug reported:
There's no reason for it to continue rendering the old version when we
support v2.
(Once [0] lands, this will also require modifications to the Oracle data
source, which merges its own network configuration into the one
generated from the initramfs.)
[0]
Hi,
Thanks for using cloud-init and filing this bug report! This behaviour
is designed to protect users from a common mistake: capturing an
instance as an image and therefore ending up with the same SSH host keys
across multiple instances. For the vast majority of users, this is the
sensible
the actual behaviour; we set the given
password only on the default user.
(I'm going to fix this soon, just filing a bug because it came up mid-
code-review and I don't want to lose track of it.)
** Affects: cloud-init
Importance: Low
Assignee: Dan Watkins (daniel-thewatkins)
Status
Public bug reported:
Currently, cloud-init has support for generating network configuration
from the /run/net-* files that klibc writes out if it performs network
configuration in the initramfs. To better support iSCSI root for
distributions that use dracut for their initramfs, we should
-cpc/hooks.d/base/ovf/ubuntu-
ovf-v1-img.tmpl (and maybe elsewhere, but definitely at least there).
** Changed in: cloud-init
Status: In Progress => Triaged
** Changed in: cloud-init
Importance: Undecided => Low
** Changed in: cloud-init
Assignee: Dan Watkins (daniel-thew
** Summary changed:
- OVF references Scott Moser's private HTTP server
+ OVF property description references Scott Moser's private HTTP server
** Changed in: cloud-init
Status: New => In Progress
** Changed in: cloud-init
Assignee: (unassigned) => Dan Watkins (daniel-thew
Public bug reported:
When working through bug 1837927, I had to go read the header (and
actual source code) of ds-identify to determine what the correct
configuration to apply was. We should include the ds-identify
configuration options in the regular cloud-init documentation.
** Affects:
Hi Orestes,
To work around this problem, you'll need to configure ds-identify[0] to
change its defaults. You should be able to do this by creating a file
named /etc/cloud/ds-identify.cfg and putting this in there:
datasource: Ec2
This will configure ds-identify to disable its usual
** Changed in: cloud-init
Status: Fix Committed => Fix Released
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
Hi Amy et al,
I'm going to mark this Fix Released, as 19.1 has made its way in to
Ubuntu. Please let us know if you don't think this is fixed!
Dan
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
** 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.
Hi shine,
Thanks for the additional information. It looks to me like these keys
aren't valid; both of them are missing a leading "-" on their first
line, which causes gpg to not be able to operate on them. For example,
comparing the Rabbit key to the one provided upstream:
# diff their.gpg
** Changed in: cloud-init
Status: Expired => Triaged
--
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/1820360
Title:
seed location requires trailing slash
Status in cloud-init:
Public bug reported:
The eventual traceback:
2019-06-19 16:27:02,468 - util.py[DEBUG]: Failed fetching meta-data/ from url
http://169.254.169.254/latest/meta-data/
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/ec2_utils.py", line 178, in
Public bug reported:
Looking at the code, I believe the error is produced by the call to
`add-apt-repository` in download() in daily_deb.sh (from server-test-
scripts).
This could probably be improved by retrying the deb creation step a
couple of times, as this may have been caused by a
Thanks for the reminder!
** 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/1830739
Title:
user-data in CloudSigma VM's metadata
Public bug reported:
Once https://github.com/CanonicalLtd/ubuntu-advantage-client/issues/366
is implemented and released, if cloud-init is given an explicit list of
entitlements to enable then it should use that functionality to _only_
enable those entitlements (whereas currently we would enable
Thanks Gareth!
** 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/1821577
Title:
cloud-init identified possible
Public bug reported:
dpkg is only present on Debian derivatives; we should attempt to use
other package management tools during `cloud-init collect-logs` to
improve our chances of getting a useful version number in the collected
tarball.
** Affects: cloud-init
Importance: Low
Public bug reported:
Due to https://code.launchpad.net/~vkuznets/cloud-init/+git/cloud-
init/+merge/362024, cloud-init-per now gives:
/usr/bin/cloud-init-per: 41: /usr/bin/cloud-init-per: Bad substitution
when it runs, as it has a shebang pointing at /bin/sh.
** Affects: cloud-init
Public bug reported:
When building the latest cloud-init package, lintian reports:
W: cloud-init: package-installs-into-obsolete-dir etc/bash_completion.d/ :
^etc/bash_completion.d/ -> usr/share/bash-completion/completions Ensure new
filename matches stricter requirements (see
Public bug reported:
We would like to upload a new upstream snapshot of cloud-init to disco.
This includes a number of desirable bug fixes, in particular:
* clean: correctly determine the path for excluding seed directory (LP:
#1818571)
* azure: Filter list of ssh keys pulled from fabric
* EC2:
** No longer affects: cloud-init
--
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/1813667
Title:
Update netplan dependency package
Status in cloud-init package in Ubuntu:
Confirmed
Omnibus support was merged; if people want more methods, please open new
bugs.
** 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.
No clarification has been forthcoming; please set back to New if this is
still interesting.
** Changed in: cloud-init
Status: Incomplete => Won't Fix
--
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: 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/925145
Title:
Use ip instead of ifconfig and route
Status in
cloud-init does now support vendor-data.
** Changed in: cloud-init
Status: Triaged => Fix Released
** 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
# Still produces output
lxc exec reproducer -- dpkg -i /tmp/cloud-init_all.deb
lxc exec reproducer -- cloud-init clean --logs
lxc exec reproducer -- find /var/lib/cloud/seed # RUH ROH
```
** Affects: cloud-init
Importance: High
Assignee: Dan Watkins (daniel-thewatkins)
Status
We now have `cloud-init query`.
** 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/1037753
Title:
implement cloud-init
Added the cloud-images project to capture the image changes that will be
required to make this available as a transport by default.
** Also affects: cloud-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering
This doesn't sound like a cloud-init bug to me. If it's provided with
two sets of network configuration (in this case, on disk via curtin from
MAAS and from you via user-data), it's going to have to choose one. If
it had chosen the user-data one here, then it wouldn't have been able to
provision
** Changed in: cloud-init
Status: Incomplete => 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/1657446
Title:
Wrong timestamps in /var/log/cloud-init.log
Status
Hi Pieter,
Thanks for filing this bug! It looks to me from the above comments like
this is fixed in more recent releases of cloud-init. If you disagree,
please do set this bug back to New (with explanation, of course!).
Thanks!
Dan
** Changed in: cloud-init
Status: New => Incomplete
** Changed in: cloud-init
Status: Triaged => Fix Released
** Changed in: cloud-init
Milestone: 0.7.2 => None
--
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/1118815
Title:
** No longer affects: cloud-init
--
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/1712695
Title:
Curtin network-passthrough configures /e/n/i.d/50-cloud-init.cfg
instead of /e/n/i
** No longer affects: cloud-init
--
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/1708676
Title:
juju doesn't surface cloud-init failures
Status in juju:
Triaged
Bug description:
** Changed in: cloud-init
Status: New => 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/1704212
Title:
MAAS marks node 'Deployed' before sshd is up
Status in
Hi Joonas,
Thanks for filing this bug! It looks to me like this is fixed in more
recent releases of cloud-init. If you disagree, please do set this bug
back to New (with explanation, of course!).
Thanks!
Dan
** Changed in: cloud-init
Status: New => Fix Released
--
You received this
Thanks James!
** Changed in: cloud-init
Status: Incomplete => 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/1521489
Title:
Support interchangeable datasource
Thanks Roopak!
** Changed in: cloud-init
Status: Incomplete => 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/1448594
Title:
DuplicateError while parsing ifcfg-ethX
Thanks Fred!
** Changed in: cloud-init
Status: Incomplete => 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/1514095
Title:
Fails to assign IP addresses if several
Hi Albert,
Thanks for filing this bug! Having root's password locked is a sensible
default from a security POV, so we're unlikely to change this. If you
have a compelling reason that we should change this, please do reopen
this bug.
Thanks!
** Changed in: cloud-init
Status: New =>
** Changed in: cloud-init
Status: New => 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/1636308
Title:
unittests: <10% coverage of cc_disk_setup.py
Status in
** Changed in: cloud-init
Status: New => 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/1636311
Title:
unittests: <10% coverage of cc_set_passwords.py
Status in
** Changed in: cloud-init
Status: New => 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/1636312
Title:
unittests: <10% coverage of netinfo.py
Status in
Hi Larry,
Thanks for filing this bug. That image is indeed only intended to work
in Azure environments, so I'm going to mark this bug as Invalid.
Thanks!
** Changed in: cloud-images
Status: New => Invalid
** Changed in: cloud-init
Status: New => Invalid
--
You received this
** 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/1619420
Title:
snappy removal of dpkg-query breaks lsb_release --all
Status in
Hi Bert, Tomas,
This appears to be fixed in more recent versions of cloud-init. Please
reopen this bug if you're continuing to see problems.
Thanks!
** Changed in: cloud-init
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Thanks Evan!
** Changed in: cloud-init
Status: Incomplete => 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/1398094
Title:
cloud-init-0.7.4-2.el6.noarch requires
** No longer affects: cloud-init
--
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/1571822
Title:
Azure: cloud-init will not set password on existing user
Status in cloud-init package
** 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/1424549
Title:
enlisting of nodes: seed_random fails due to self signed
GCE's startup scripts are intended to be executed by Google's agents
running within instances. If cloud-init _also_ attempts to handle them,
they will be executed twice.
** Changed in: cloud-init
Status: New => Won't Fix
--
You received this bug notification because you are a member of
Dropping this from the cloud-init Ubuntu package so we're just tracking
it in one place.
** No longer affects: cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
Public bug reported:
When debugging instance launch failures, one trick we use is to mount
the disk of the failed instance to another instance, and investigate the
logs there. Most of the time, we can use chroot to run `cloud-init
collect-logs` in the failed instance's root. However, if we are
Public bug reported:
I run a lxd server in a cloud instance, and have that configured as my
default remote. The cloud-init test framework still launches its first
container ("cloud-test-ubuntu-bionic-image-modification-
oot8q3h1p4jup1jb8ce") locally, but then fails to use it properly. When
I
Public bug reported:
When building Ubuntu cloud images, we prefer to name the default user
"ubuntu" where possible, to maintain a consistent user experience
between substrates. Some clouds, however, like to have a consistent
user name across all of their various image offerings. This is an
As we have preseeded snaps in bionic, we'll want this SRU'd there (at
least).
** Also affects: cloud-init (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
OK, so I think the next step here is to create a test xenial image
without that datasource_list and confirm that it boots as expected.
This, however, will not help the situation for already-deployed
instances upgrading, so I guess we'll also need to look at having a
cloud-init postinst hook go
** Changed in: cloud-images
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/1755965
Title:
util.subp regression: no longer accept commands
I'm keeping an eye on the build system to ensure we get a good daily
out.
** Also affects: cloud-images
Importance: Undecided
Status: New
** Changed in: cloud-images
Status: New => In Progress
** Changed in: cloud-images
Assignee: (unassigned) => Dan Watkins (
Public bug reported:
If I pass in user data like so:
$ cat cfg
#!/bin/sh
touch /tmp/foobar
$ gcloud compute instances create aa-$(date +%y%m%d-%H%M) --image-family
ubuntu-1710 --image-project ubuntu-os-cloud-devel --metadata-from-file
user-data=cfg
...
Then in the instance:
$ ls /tmp/foobar
This bug is for _project-level_ SSH keys, bug 1693582 is for _instance-
level_ SSH keys.
** This bug is no longer a duplicate of bug 1693582
cloud-init uses a deprecated metadata path for GCE instance SSH keys
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
GCE supports the expiration of SSH keys. It does so by including the
expiry time in a JSON blob in the comment section of the SSH key. As
per [0], the format is:
ssh-rsa [KEY_VALUE] google-ssh
{"userName":"[USERNAME]","expireOn":"[EXPIRE_TIME]"}
Keys can remain in
Public bug reported:
It should be using project/attributes/ssh-keys.
** Affects: cloud-init
Importance: Undecided
Status: New
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Public bug reported:
GCE supports specifying SSH keys for an instance as a tuple of
(username, key). Currently, cloud-init will add all keys to the default
(ubuntu) user, regardless of the user specified in metadata.
This is problematic because there may be users in the metadata who are
not
Public bug reported:
The GCE data source will always include SSH keys from project metadata
in the default (ubuntu) user's authorized_keys file. If block-project-
ssh-keys is set in metadata, however, project-level SSH keys shouldn't
be included.
** Affects: cloud-init
Importance:
Public bug reported:
Per https://cloud.google.com/compute/docs/storing-retrieving-metadata,
the attribute is now instance/attributes/ssh-keys (not sshKeys).
** Affects: cloud-init
Importance: Undecided
Assignee: Dan Watkins (daniel-thewatkins)
Status: In Progress
** Affects
OK, I must have misread the source code; testing in lxd didn't occur to
me!
** Changed in: cloud-init
Status: Incomplete => Invalid
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering
As suggested to me by smoser in #cloud-init, this doesn't actually
reproduce on xenial and yakkety; I'll focus on fixing it in trusty.
** Changed in: cloud-init (Ubuntu Yakkety)
Status: Confirmed => Invalid
** Changed in: cloud-init (Ubuntu Xenial)
Status: Fix Committed => Invalid
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => Confirmed
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => In Progress
** Changed in: cloud-init
Assignee: (unassigned) => Dan Watkins (daniel-t
Thanks Wido, merged and pushed!
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Hi zero, Kenneth, Nick,
Thanks for reporting and confirming this bug! Could one of you include a
list of instructions to reliably reproduce this, please? That will make
it much easier for someone investigating the bug to be sure that they
are hitting the same issue that you are. :)
Thanks,
Dan
** 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/1506187
Title:
[SRU] Azure: cloud-init should use VM unique ID
** 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/1403617
Title:
gce datasource does not handle instance ssh keys
101 - 200 of 229 matches
Mail list logo
