yahoo-eng-team team mailing list archive

[James Falcon <1724128@xxxxxxxxxxxxxxxxxx>]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3031

** Bug watch added: github.com/canonical/cloud-init/issues #3031
   https://github.com/canonical/cloud-init/issues/3031

** Changed in: cloud-init
       Status: Triaged => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1724128

Title:
  Need a Success / Failure notification mechanism when cloud-init
  finishes.

Status in cloud-init:
  Expired

Bug description:
  I discussed this issue during the 'cloud-init' summit that happened in
  August 2017. Logging a bug for tracking purposes. Today, there is no
  way for datasources to get notified about success / failure when
  cloud-init finishes executing.

  Following is an example:

  > From cloudinit/sources/DataSourceOVF.py

              # TODO: Need to set the status to DONE only when the
              # customization is done successfully.
              enable_nics(self._vmware_nics_to_enable)
              set_customization_status(
                  GuestCustStateEnum.GUESTCUST_STATE_DONE,
                  GuestCustErrorEnum.GUESTCUST_ERROR_SUCCESS)

  Ideally, the datasourceOVF wants to get notified when the cloud-init
  finally completes. Then, the datasource needs to send success /
  failure events to the underlying hypervisor. But today the mechanism /
  framework is not available. So, the datasourceOVF just blindly returns
  SUCCESS to the hypervisor without even waiting for the completion.

  We really really need a better framework / mechanism to handle
  situations like this. Please do let me know if any information is
  requried.

  Thanks
  Sankar.

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