This is an unfortunate consequence of yaml parsing rather than a bug in
cloud-init. Since you're using plain unquoted strings, the quotes don't
carry any special meaning and the ' #' is interpreted as the beginning
of a comment.
This is specifically called out in the yaml spec at
Reviewed: https://review.opendev.org/c/openstack/neutron/+/842147
Committed:
https://opendev.org/openstack/neutron/commit/32e8303b3b21e047abcf365c3999cb7379467b0c
Submitter: "Zuul (22348)"
Branch:master
commit 32e8303b3b21e047abcf365c3999cb7379467b0c
Author: Rodolfo Alonso Hernandez
Date:
Public bug reported:
I've managed to reproduce using multipass and KVM on a local machine.
To reproduce this you just need to have echo command in runcmd section
of a cloud-init config file that have white space before any
alphanumeric characters.
For example the following runcmd stanza
Public bug reported:
Originally reported in IRC, there appears to be a bug in cloud detection
for VMware
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
Related Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2093739
For minimum bandwidth, the OVS agent is create a QoS policy assigned to
the physical bridge interface. Any new port with a min-bw QoS rule will
create a queue attached to this QoS policy. OVS creates the
Brian, thanks for looking. I have to apologize because it looks like
this was a mistake on my end, building with old code. I'm going to close
this out.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
6 matches
Mail list logo
