hostname is set incorrectly if localhostname is fully qualified
Bug #1647910 reported by
Lars Kellogg-Stedman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Medium
|
Unassigned | ||
cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Unassigned | ||
Yakkety |
Fix Released
|
Medium
|
Unassigned |
Bug Description
If no data source is available and the local hostname is set to "localhost.
127.0.0.1 localhost localhost.
Then in sources/__init__.py in get_hostname:
- util.get_hostname() will return 'localhost.
- util.get_
- 'toks' will be set to [ 'localhost.
And ultimately the system hostname will be set to 'localhost.
Also reported in:
Related branches
~larsks/cloud-init:bug/1647910
- Scott Moser: Pending requested
-
Diff: 13 lines (+2/-0)1 file modifiedcloudinit/sources/__init__.py (+2/-0)
Changed in cloud-init (Ubuntu): | |
status: | New → Fix Released |
Changed in cloud-init (Ubuntu Yakkety): | |
status: | New → Confirmed |
Changed in cloud-init: | |
importance: | Undecided → Medium |
Changed in cloud-init (Ubuntu): | |
importance: | Undecided → Medium |
Changed in cloud-init (Ubuntu Xenial): | |
importance: | Undecided → Medium |
Changed in cloud-init (Ubuntu Yakkety): | |
importance: | Undecided → Medium |
To post a comment you must log in.
This is fixed in cloud-init 0.7.9.