** Description changed:
=== Begin SRU Template ===
[Impact]
On systems deployed with MAAS xenial and yakkety systems would put a
warning on the login screen stating that the datasource was not found.
-
[Test Case]
The full test case involves
* deploying through MAAS
* enabling -proposed (without -proposed should show failure)
* setting curtin config to show:
system_upgrade: {enabled: True}}
[Regression Potential]
- The changes did
+ The changes that were done
a.) renamed some variables to make code more readable
b.) make searching for config less restrictive
due to 'a', there could be unintended bugs, but testing for
other datasources would likely have turned that up.
[Other Info]
=== End SRU Template ===
- in ds-identify, the dscheck_MAAS calls check_config incorrectly, and as a
result
- does not enable the MAAS datasource.
+ In ds-identify, the dscheck_MAAS calls check_config incorrectly, and as
+ a result does not enable the MAAS datasource.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1677710
Title:
ds-identify does not find maas datasource
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1677710/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
