Cloud-init fails if metadata local-hostname is null
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Undecided
|
Mark Goddard |
Bug Description
If I run cloud-init with a config drive containing a metadata file which has local-hostname set to null, I get the following traceback:
Traceback (most recent call last):
File "/usr/lib/
if s.get_data():
File "/usr/lib/
self.
File "/usr/lib/
'local-
File "/usr/lib/
if util.is_
File "/usr/lib/
toks = instr.split('.')
Tested on CentOS 7.7, cloud-init 18.5.
Changed in cloud-init: | |
assignee: | nobody → Mark Goddard (mgoddard) |
Changed in cloud-init: | |
status: | New → In Progress |
This bug is believed to be fixed in cloud-init in version 19.4. If this is still a problem for you, please make a comment and set the state back to New
Thank you.