** 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 cloud-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:
** 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
St
** 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:
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: 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 i
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
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 Team,
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 qu
# 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: In
** 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-ini
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 c
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.
https://bugs.
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.
https://bugs.launchpad.net
** 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
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:
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 https://bugs.debi
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
Importa
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
Status
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 datasources
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 w
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 f
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 temporary
** 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
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
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: 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 inte
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
Status
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 metadata
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!
Engineerin
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
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
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
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 cloud-
201 - 234 of 234 matches
Mail list logo
