yahoo-eng-team team mailing list archive

[Pengpeng Sun <1835205@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Currently DatasourceOVF does not check the instance id to determine if
current instance is a new instance or not, so that every booting, cloud-
init will go through entire datasource list.

This leads an issue:
When a VM's network is customized to static IP by cloud-init DatasourceOVF and then the VM is rebooted, the VM's network will be changed to DHCP after rebooting since this time no customization config file will be found. cloud-init uses DatasourceNone which change network to "default" configuration.

The expected behaviors are:
1. cloud-init checks the instance id to know if this instance is "iid-vmware-xxxxxx" which means it's a VMware VM. If yes, it should always use datasourceOVF.
2. When there has customization config file, datasourceOVF parse the configures and enable nics as usual.
3. When there is no customization config file, datasourceOVF wait for it until timeout and then cloud-init does NOT apply other datasources.

** Affects: cloud-init
     Importance: Undecided
         Status: New

-- 
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/1835205

Title:
  OVF datasource should check if instant id is still on VMware Platform

Status in cloud-init:
  New

Bug description:
  Currently DatasourceOVF does not check the instance id to determine if
  current instance is a new instance or not, so that every booting,
  cloud-init will go through entire datasource list.

  This leads an issue:
  When a VM's network is customized to static IP by cloud-init DatasourceOVF and then the VM is rebooted, the VM's network will be changed to DHCP after rebooting since this time no customization config file will be found. cloud-init uses DatasourceNone which change network to "default" configuration.

  The expected behaviors are:
  1. cloud-init checks the instance id to know if this instance is "iid-vmware-xxxxxx" which means it's a VMware VM. If yes, it should always use datasourceOVF.
  2. When there has customization config file, datasourceOVF parse the configures and enable nics as usual.
  3. When there is no customization config file, datasourceOVF wait for it until timeout and then cloud-init does NOT apply other datasources.

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