cloud-init raises an exception when it sees more than 3 nameservers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Medium
|
Lars Kellogg-Stedman | ||
cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Unassigned | ||
Yakkety |
Fix Released
|
Medium
|
Unassigned | ||
Zesty |
Fix Released
|
Medium
|
Unassigned |
Bug Description
=== Begin SRU Template ===
[Impact]
When rendering sysconfig (redhat/centos) output there was a bug
where cloud-init would error if provided with more than 3 nameservers.
That was changed to a warning.
[Test Case]
This can't really be tested on Ubuntu, as ubuntu does not render
sysconfig network information.
[Regression Potential]
Low everywhere (change ValueError to a WARN) and lower on Ubuntu,
where the code is not in the run path.
[Other Info]
Upstream commit:
https:/
=== End SRU Template ===
When running in an environment that provides more than 3 nameservers, cloud-init will raise a ValueError exception:
Mar 04 18:03:01 localhost.
While that is a legitimate complaint, raising an exception seems like the wrong response, because this results in *no* nameserver configuration, which can have a substantial operational impact on the system. Cloud-init should probably just log a warning in this case, and ignore any nameservers received after the first three.
Related branches
- Server Team CI bot: Needs Fixing (continuous-integration)
- Scott Moser: Pending requested
-
Diff: 44 lines (+8/-5)2 files modifiedcloudinit/distros/parsers/resolv_conf.py (+7/-4)
tests/unittests/test_distros/test_resolv.py (+1/-1)
Changed in cloud-init: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Lars Kellogg-Stedman (larsks) |
Changed in cloud-init (Ubuntu): | |
status: | New → Fix Released |
importance: | Undecided → Medium |
Changed in cloud-init (Ubuntu Xenial): | |
status: | New → Confirmed |
Changed in cloud-init (Ubuntu Yakkety): | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in cloud-init (Ubuntu Xenial): | |
importance: | Undecided → Medium |
description: | updated |
Changed in cloud-init: | |
status: | Confirmed → Fix Committed |
status: | Fix Committed → Confirmed |
status: | Confirmed → Fix Committed |
(BTW, we're seeing this in an environment running both ipv6 and ipv4, so the system receives two ipv4 nameserver addresses and two ipv6 nameserver addresses.)