group.of.nepali.translators team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: cloud-init
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1677710

Title:
  ds-identify does not find maas datasource

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  On Ubuntu core systems deployed with MAAS xenial and yakkety systems
  would put a warning on the login screen stating that the datasource was
  not found.

  The issue only occurred on Ubuntu core.  Ubuntu systems were not affected
  as recent maas versions preseed cloud-init with 'datasource_list: [MAAS]'
  which results in ds-identify just accepting the single entry as defined.

  [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 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1677710/+subscriptions