** Changed in: cloud-init (Ubuntu)
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/1767166
Title:
IBMCloud datasource does not recognize pr
This bug is believed to be fixed in cloud-init in version 23.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 membe
This bug is believed to be fixed in cloud-init in version 23.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 membe
This bug is believed to be fixed in cloud-init in version 23.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 membe
This bug is believed to be fixed in cloud-init in version 23.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 membe
Sorry for delay here, this is fix released and published to schema-
store.org as of this upstream commit https://github.com/canonical/cloud-
init/commit/53e1ccf83ca737f80f98300cf00d5c026bd9464d
** Changed in: cloud-init
Status: In Progress => Fix Released
--
You received this bug notifica
Closing the cloud-init task here as invalid because we have livecd-
rootfs overlay config files allow for cloud-init.service to get ordered
After=NetworkManager.service which solves the immediate DNS issues in
early boot. Long-term cloud-init will need to spec out options to prefer
ordering after N
Public bug reported:
In Ubuntu packaging of systemd cloud-init.service file, cloud-
init.service declares ordering as After=systemd-networkd-wait-
online.target[1] and Before=sysinit.target[2].
The desktop live installer ISO prefers using NetworkManager as the primary
network backend and cloud-
Marking invalid for cloud-init as this cloud-init task was added during
triage to inform the project of external config changes in place in
livecd-rootfs related to cloud-init behavior on Desktop live installer
images.
** Changed in: cloud-init
Status: New => Invalid
--
You received this
Public bug reported:
Seen on live desktop isos build date:
Desktop live installer prefers NetworkManager backend for network config due to
a netplan config file /etc/netplan/01-network-manager.yaml which contains:
network:
version: 2
renderer: NetworkManager
livecd-rootfs configures clou
Thanks for noting this inconsistency, I've updated branding logo now to
align w/ RTD
** 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.n
AS, until we got an
explicit non-zero exit code.
References:
[1] Pyyaml 6.0.1 commit sync'd to lunar
https://git.launchpad.net/ubuntu/+source/pyyaml/commit/?id=5308dbefbe5dc7ce4a19adbfdb4c4e08a798217d
[2] yaml.load failure on Lunar:
https://github.com/canonical/cloud-init/blob/ubuntu/de
journalctl on a failed laptop is showwing a lot of throttling logs from
NetworkManager such as :
stat change: unavilable -> disconnected (reason 'carrier changed',
sys-iface-state: 'managed')
This makes be believe that networkd and NetworkManager are attempting to
grab management of the NIC mul
Upstream commit landed to avoid this automatically suggesting that OpenStack
datasource may be applicable by default on Bare metal. This is probably not the
majority of cases for bare metal openstack detection for bare metal should only
be active if it is explicitly set by either kernel cmdline
Marking invalid as it seems this is unrelated to cloud-init. Please re-
open if this surfaces again.
** Changed in: cloud-init
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://b
Hiya windowsguy,
One thing we hope to see here with your attached tar/zipped logs from
`cloud-init collect-logs` is whether cloud-init is actually making a
call to passwd -l or usermod --lock in logs.
I'll mark this bug as 'Incomplete' status. Please set it back to 'New'
when you have had a chang
The dbus race that is happening here is due to `networkctl reconfigure`[1]
being run by netplan apply, failing to talk to dbus, and restarting
systemd_networkd[2] at that point in time when systemd_network may actually be
coming up and is in an indeterminate state.
[1] https://github.com/cano
work in progress pull request which will resolve this problem. Needs unit tests
and then cloud-init can support jammy launches from LXD 4.0 hosts.
https://github.com/canonical/cloud-init/pull/1948
** Changed in: cloud-init
Status: Triaged => Won't Fix
** Changed in: cloud-init
Stat
Public bug reported:
cloud-init 22.4.2
On Azure, datasource details change across reboot cloud-init incorrectly
removes /run/cloud-init/cloud-id-azure symlink.
2022-12-07 04:14:17,920 - util.py[DEBUG]: Creating symbolic link from
'/run/cloud-init/cloud-id' => '/run/cloud-init/cloud-id-azure'
2
Upstream PR landed with a fix for this issue allowing cloud-init to ignore
duplicate macs as seen on mellanox subordinate devices.
https://github.com/canonical/cloud-init/pull/1853.
We have also released this into Ubuntu Lunar 23.04 as cloud-init version
22.4-0ubuntu4.
Our plan is also to queu
Marking this as Fix released as I think it should already be in official
22.2 releases. If it still persists in 22.2 or later please feel free to
reopen the bug.
** Changed in: cloud-init
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Thanks for the detailed discussions here @danielky.
I think I agree with your last statement in comment #3
> Detecting the raid-setup and the right disks might be out of scope for
> cc_grub_dpkg, so why not just skip setting the "grub-pc/install_devices" item
> if it is already set in debconf
This was fixed as of 0.7.6-444-g41900b72f
** 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/1488891
Title:
WALinuxAg
Public bug reported:
cloud-init 22.3 reporting configuration doesn't report paired
start/finish event_types for all of cloud-init's boot stages.
Expected behavior:
cloud-init boot stages (init-local, init-network, config-modules and
config-final) to emit both event_type start and finish to re
Public bug reported:
Per https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1991261
there is confusion about the impact of dsmode=net vs local on cloud-init
runtime.
This is a request for improved/conspicous general datasoiurce documentation of
dsmode settings and the impact to cloud-ini
Thanks for filing a bug against cloud-init. Please update the report
with details which describe what feature you would like to see.
** Changed in: cloud-init
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscri
Fix released into Ubuntu Kinetic 22.10 as cloud-init version
22.3-13-g70ce6442-0ubuntu1~22.10.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.
htt
Please set the bug status back to "New" when further comments have been
added to make sure our team gets alerted about the updated comments so
we can respond more quickly.
** Also affects: subiquity
Importance: Undecided
Status: New
** Changed in: subiquity
Status: New => Incompl
Public bug reported:
Intermittent failure found during jenkins test runs:
We probably want a couple quick retries if lock is held.
https://github.com/canonical/cloud-init/blob/main/cloudinit/config/cc_grub_dpkg.py#L155
'2022-08-18 06:54:21,464 - handlers.py[DEBUG]: start: '
'modules-config/co
Public bug reported:
cloud-init has two interactions with network backplanes
1. to write (or render) network configuration to the approapriate config
files for the network system: systemd, netplan, network-manager, ENI,
freebsd, netbsd, openbsd. This is done via cloudinit.net.renderers
discovery[
Alternative solution to this could be if netplan.io grows a new root-
only directory option that defines a schema for storing sensitive
information like credentials. Not sure if this is something netplan.io
would plan to grow or not. Tagging netplan.io on this bug as an FYI
`wishlist` in case futur
I believe this bug/feature has been fixed in cloud-init as of cloud-init
version 18.1
Azure specifically sets hostname during init-local timeframe based on this
commit
https://github.com/canonical/cloud-
init/commit/133ad2cb327ad17b7b81319fac8f9f14577c04df
which addressed this related bug http
Public bug reported:
https://netplan.io/reference/ supports wifi password and auto client-
key-password keys which should generally not be world-readable.
But, when rendering passthrough V2 network configuration, cloud-init emits a
single /etc/netplan/50-cloud-init.yaml file that is world reada
Public bug reported:
Changes to /etc/cloud/cloud.cfg system_info: paths: cloud_dir setting is
not honored globally in cloud-init. Some paths continue to hardcode
/var/lib/cloud paths to certain operations.
Affects cloud-init version 22.2
[Test Plan]
cat > 95-custom-cloud-dir.cfg < '../../var/
** Changed in: cloud-init
Status: New => Fix Released
** Changed in: cloud-init
Assignee: (unassigned) => Brett Holman (holmanb)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bu
Public bug reported:
In minimal cloud images without openssh-server, cloud-init will get the
following traceback.
2022-04-19 20:42:32,593 - stages.py[DEBUG]: Running module set-passwords
() with
frequency once-per-instance
2022-04-19 20:42:32,593 - handlers.py[DEBUG]: start:
modules-config/co
Public bug reported:
Update "read the docs" content at
doc/rtd/topics/datasources/altcloud.rst
Ensure it correctly represents behavior and configuration options as used in:
cloudinit/sources/DataSourceAltCloud.py
Example format/style should be something like:
doc/rtd/topics/datasources/ec2.rst
Dropping cc_emit_upstart config module due to no longer having Ubuntu
Trusty support in cloud-init upstream. Marking WONTFIX
** Changed in: cloud-init
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribe
Upstream fix committed in
https://github.com/canonical/cloud-init/commit/af7eb1deab12c7208853c5d18b55228e0ba29c4d
published as cloud-init 22.1
** Changed in: cloud-init
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering T
Upstream fix committed in
https://github.com/canonical/cloud-init/commit/af7eb1deab12c7208853c5d18b55228e0ba29c4d
published as cloud-init 22.1
** Changed in: cloud-init
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Te
Upstream fix committed in
https://github.com/canonical/cloud-init/commit/af7eb1deab12c7208853c5d18b55228e0ba29c4d
published as cloud-init 22.1
** Changed in: cloud-init
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Te
Upstream fix committed in
https://github.com/canonical/cloud-init/commit/af7eb1deab12c7208853c5d18b55228e0ba29c4d
published as cloud-init 22.1
** Changed in: cloud-init
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Te
Upstream fix committed in
https://github.com/canonical/cloud-init/commit/af7eb1deab12c7208853c5d18b55228e0ba29c4d
published as cloud-init 22.1
** Changed in: cloud-init
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Te
upstream commit added that resolves this issue.
https://github.com/canonical/cloud-init/commit/4ba6fd283674df1ef25300d91c6d2061910744be
fix published in version 21.4
** Changed in: cloud-init
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of
Fix released to Jammy [ubuntu/jammy-proposed] cloud-init
22.1-14-g2e17a0d6-0ubuntu1~22.04.4 (Accepted)
** Changed in: cloud-init (Ubuntu Jammy)
Status: In Progress => Fix Released
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notificatio
** Also affects: cloud-init (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Jammy)
Importance: High
Status: Triaged
** Also affects: cloud-init (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu
This fix in Jammy 22.1-14-g2e17a0d6-0ubuntu1~22.04.1 also had an unintended
side-effect where network would not get rendered due and newly launched
instnaces on Jammy were unreachable due to
cloud-init networking being configured as disabled in Oracle images
/etc/cloud/cloud.cfg.d/99-disable-ne
** 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/1779386
Title:
test smoser bug for lp-attach [please ignore]
Status in cloud-in
I'll make this bug as invalid for now because this is cloud-init working
as desired and I expect the only thing you were missing was a subsequent
call to `cloud-init init` to see write-files run.
If this is closed in error, please feel free to set state back to 'New'
above.
** Changed in: cloud-i
Public bug reported:
If any files are root read-only in /etc/cloud/cloud.cfg.d cloud-init query
tracebacks for non-root user
cloud-init version: 21.4
Reproducible on Jammy Desktop installer images
csmith@csmith-Standard-PC-i440FX-PIIX-1996:~$ cloud-init query --all
Traceback (most recent call l
Thank you for filing a bug and making Ubuntu and cloud-init better.
The reason you are unable to login as jpcozar is because the default
behavior of cloud-init is to lock password logins and prefer key-based
login for ssh.
What you'll need is to both allow password-based ssh logins with
"ssh_pwau
Public bug reported:
https://cloudinit.readthedocs.io/en/latest/topics/modules.html#users-
and-groups should have a more visible note explaing the affect of
omitting "- default" as this is a fairly frequent accidental side-effect
for user-config containing "users:" directives.
** Affects: cloud-i
** Also affects: cloud-init (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Impish)
Importance: Critical
Status: Fix Committed
** Also affects: cloud-
** Changed in: centos
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/1936229
Title:
selinux cloud-init-hotplugd.socket not having permissions to fifo
s
** Also affects: centos
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/1936229
Title:
selinux cloud-init-hotplugd.socket not having permiss
Public bug reported:
Initial cloud-init-hotplugd.socket has some undesirable interactions
with an enforcing SElinux system when trying to listen on a FIFO socket.
Deploying on rocky linux 8.4 we can see SELinux errors preventing the
cloud-init-hotplugd.socket from starting
from journalctl -b
Public bug reported:
cloud-init 21.2
User-specific Match sections can be provided in /etc/ssh/sshd_config to
override global ssh config default settings such as AuthorizedKeysFile.
cloud-init's parsing of sshd_config in ssh_util[1] is simplistic and treats
each line in the sshd_config file as
** 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/1732522
Title:
[2.3] Ephemeral boot environment does not renew DHCP lease
** Changed in: cloud-init (Ubuntu Hirsute)
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/1910835
Title:
Azure IMDS publicKeys contain \r\n which pr
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xen
Public bug reported:
cloud-init 20.4 or later will incorrectly add Azure publicKeys to
.ssh/authorized_keys preventing ssh access for cloud-generated keys.
To reproduce: launch an ubuntu VM from the portal.azure.com choosing to
generate new ssh key.
When the instance is launched you can see th
This bug is believed to be fixed in cloud-init in version 20.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 membe
This bug is believed to be fixed in cloud-init in version 20.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 membe
This bug is believed to be fixed in cloud-init in version 20.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: Confirmed => 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.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 membe
This bug is believed to be fixed in cloud-init in version 20.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 membe
This bug is believed to be fixed in cloud-init in version 20.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: 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 20.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 membe
This bug is believed to be fixed in cloud-init in version 20.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: 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 20.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: 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 20.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 membe
This bug is believed to be fixed in cloud-init in version 20.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 membe
This bug is believed to be fixed in cloud-init in version 20.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: 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 20.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: In Progress => Fix Released
--
You received this bug notification because you are a member
Public bug reported:
sudo cloud-init query --all fails on juju deployed units with the
following trace:
On some platforms (juju deployed instances and various openstack platforms),
user-data is compressed when provided to the instance.
When deploying juju units in ec2 regions, user-data provi
Public bug reported:
Annotate doesn't handle r-value dicts that begin on the same line as the
l-value key.
Given the following example invalid cloudconfig (providing an int for a
string value in chef), we get a traceback when trying to annotate the
invalid user-data.
cat > invalid-chef-traceback
Thank you for the bug Asaf and making cloud-init better.
It seems like your nocloud network-config YAML file exposed to your vm in the
file
"Read 120 bytes from /run/cloud-init/tmp/tmpb_430skf//network-config"
... represents the mac_address value as an integer.
2020-06-10 06:56:30,126 - stage
This bug is believed to be fixed in cloud-init in version 20.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 membe
This bug is believed to be fixed in cloud-init in version 20.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 membe
This bug is believed to be fixed in cloud-init in version 20.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 membe
This bug is believed to be fixed in cloud-init in version 20.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 membe
This bug is believed to be fixed in cloud-init in version 20.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 membe
This bug is believed to be fixed in cloud-init in version 20.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 membe
This bug is believed to be fixed in cloud-init in version 20.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 membe
This bug is believed to be fixed in cloud-init in version 20.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 membe
Public bug reported:
We have 47-ish documentation examples of useful cloud-config in
doc/examples/*txt.
We need to ensure each cloud-config example contains the necessary
#cloud-config header and
add a unit tests which will run
cloudinit.config.schema:validate_cloudconfig_schema over all thos
Public bug reported:
As we implement jsonschema definitions in cloud config modules
(cloudinit.config.cc_*.py) we need a unittest which will automatically
run schema validation on cc_*.py modules.
Add a unittest to tests/unittests/test_handler/test_schema.py that will
discover all config modules
Public bug reported:
== Release Notes ==
Cloud-init release 20.2 is now available
The 20.2 release:
* spanned about 9 weeks
* had 20 contributors from 20 domains
* fixed 14 Launchpad issues
Highlights:
== Changelog ==
- doc/format: reference make-mime.py instead of an inline script (#33
** Changed in: cloud-init
Status: In Progress => Fix Committed
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Committed
** Also affects: cloud-init (Ubuntu Focal)
Importance: Undecided
Public bug reported:
cloud-init 20.1 currently renders only local ip address information in
the network configuration emitted for attached NICs.
Ec2 instances can be launched and configured with multiple public IP
addresses
https://aws.amazon.com/blogs/aws/multiple-ip-addresses-for-ec2
-instance
A version of cloud-init containing this fix was published to Ubuntu
Focal (20.04) cloud-init 20.1-9-g1f860e5a-0ubuntu1.
If this is still a problem for you, please re-open this bug or submit a
new bug with related context.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
A version of cloud-init containing this fix was published to Ubuntu
Focal (20.04) cloud-init 20.1-9-g1f860e5a-0ubuntu1.
If this is still a problem for you, please re-open this bug or submit a new bug
with related context.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
-
maybe github squashed it and attributed to me due to the last commit on
the branch having the reference
Test provided by: Chad Smith
I'll make sure if I see top-most commits with other attributions that we also
place a trailing
Authored-by: footer on the commit message to inform gith
Public bug reported:
The Ec2 IMDSv2 latest/api/token route can be set as disabled and return
a 403 indefinitely for an instance.
When receiving any HTTP status codes >= 400 from IMDSv2 on AWS' Ec2
cloud, 2 minutes or retries on the api/token route will not result in a
successful Ec2 datasource de
*** This bug is a security vulnerability ***
Private security bug reported:
Cloud-init persists world-readable instance metadata in /run/cloud-init
/instance-data.json and a read-only root /run/cloud-init/instance-data-
sensitive.json.
Any sensitive metadata provided by a cloud platform's metada
, 19b) after 1
attempts
2020-03-03 13:27:48,869 - DataSourceEc2.py[DEBUG]: Using metadata source:
'http://169.254.169.254'
2020-03-03 13:27:48,869 - DataSourceEc2.py[DEBUG]: Refreshing Ec2 metadata API
token
** Affects: cloud-init
Importance: High
Assignee: Chad Smith (ch
Confirmed proper ssh module docs are now present and live
https://cloudinit.readthedocs.io/en/latest/topics/modules.html#ssh
** 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
Public bug reported:
Add initial jsonschema definition for validation of cloud-config
user data to cloudinit/config/cc_set_hostname.py.
Add a schema dictionary to the cc_*.py module which describes allowed
cloud-config properties which are honored by the module.
jsonschema support for a cloud-c
Public bug reported:
Add initial jsonschema definition for validation of cloud-config
user data to cloudinit/config/cc_scripts_user.py.
Add a schema dictionary to the cc_*.py module which describes allowed
cloud-config properties which are honored by the module.
jsonschema support for a cloud-c
Public bug reported:
Add initial jsonschema definition for validation of cloud-config
user data to cloudinit/config/cc_update_hostname.py.
Add a schema dictionary to the cc_*.py module which describes allowed
cloud-config properties which are honored by the module.
jsonschema support for a clou
1 - 100 of 346 matches
Mail list logo
