yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #90411
[Bug 1996781] Re: text/plain encoding for write_files unsupported?
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!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1996781
Title:
text/plain encoding for write_files unsupported?
Status in cloud-init:
Fix Released
Bug description:
OpenStack RockyLinux 8 instance failed to boot properly. Console log
showed:
```
[ 103.927922] cloud-init[852]: Cloud-init v. 22.1-5.el8 running 'init' at Wed, 16 Nov 2022 14:45:47 +0000. Up 103.64 seconds.
<snip>
[ 103.974747] cloud-init[852]: 2022-11-16 14:45:47,803 - schema.py[WARNING]: Invalid cloud-config provided:
[ 103.978215] cloud-init[852]: write_files.0.encoding: 'text/plain' is not one of ['gz', 'gzip', 'gz+base64', 'gzip+base64', 'gz+b64', 'gzip+b64', 'b64', 'base64']
[ 103.982366] cloud-init[852]: write_files.0.encoding: 'text/plain' is not one of ['gz', 'gzip', 'gz+base64', 'gzip+base64', 'gz+b64', 'gzip+b64', 'b64', 'base64']
```
But the
[docs](https://cloudinit.readthedocs.io/en/22.1_a/topics/modules.html#write-
files) for this version so that text/plain IS an accepted encoding.
This worked before the release of RockyLinux 8.7 so I'm assuming this
is a newer version of cloud-init and there's a regression?
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1996781/+subscriptions
References