yahoo-eng-team team mailing list archive

[Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>]

I'm marking this fix-released for bionic and xenial.
The fix is available in bionic-updates and xenial-updates
and was SRU'd under bug 1795953.

If you are experiencing this problem still, re-open the bug.

Thank you.


** Changed in: cloud-init (Ubuntu Xenial)
       Status: Confirmed => Fix Released

** Changed in: cloud-init (Ubuntu Bionic)
       Status: Confirmed => Fix Released

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

Title:
  network customization with cloud-init does not work on Ubuntu18.04
  Beta2 Server

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 Bionic:
  Fix Released
Status in cloud-init source package in Cosmic:
  Fix Released

Bug description:
  This issue does NOT exist on Ubuntu18.04 Beta2 Desktop, it only
  reproduces on Ubuntu18.04 Beta2 Server

  Ubuntu18.04 Beta2 Server is installed on a VMware VM.

  VMware customization Config File was copied to /var/run/vmware-imc/cust.cfg correctly.
  Check cloud-init.log, it parsed the cust.cfg, but VM network is not customized correctly according to cust.cfg.

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