fuel-agent: unicode handling in cloud-init templates
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Low
|
Fuel Sustaining |
Bug Description
Apparently, fuel-agent uses `write-
this tool doesn't have abitlity to specify non-default charset, thus it will be always producing 'us-ascii' plain text files. that wasn't an issue when all input data was limited to ASCII values (which is still purely compatible with UTF-8).
even if any of partial cloud-init payload contains non-ascii characters, it will use 'us-ascii' charset in the resulting multipart file due to [2]:
# Note: we should handle calculating the charset
msg = MIMEText(fp.read(), _subtype=subtype)
MIMEText supports specifying of the output charset [3]. However, `write-
[1] https:/
[2] http://
[3] https:/
Changed in fuel: | |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
status: | New → Confirmed |