[Expired for cloud-init (Ubuntu) because there has been no activity for
60 days.]
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have Setup the cloud-init as the customization engine, based on this
KB [2] instead which is similar to above mentioned KB [1] but it with
two extra steps Item 3 and 4. i also made sure i have removed the
After=Dbus.service
[2] https://kb.vmware.com/s/article/54986
The result is i see
Thanks Joshua .. thats pretty much it yes
So if i need to use Cloud Config / User data to execute scripts i must
use cloud-init as well to do the customizization instead of using Perl (
VMware Customization ) baed on the provided KB [1]. The problem is when
i do that i have no network, no IP, no
Thanks Joshua .. thats pretty much it.
so at all times if i need to use Cloud Config / User data i must use
cloud-init as well to do the customize instead of Perl . the problem is
when i do that i have no network, no IP, no updated hostname update and
of course no connectivity for anything to
Maher,
Thanks for the various attempts and options that you have given this. At
this time it is obvious that trying to do both VMware and cloud-init
customization is broken. We worked with VMware to produce a KB [1] to
state that and give the options of using one or the other. In the mean
time we
Just tested Ubuntu 18.04 ( same issue ) logs attached
Behaviour for deploying Ubuntu 18 VMs using Static IP from Automation tool
Automation tool maps an image iso to pass cloud-init user data
Template work done
--
Deploy Ubuntu 18.04 from iso
sudo apt-get udpate && sudo apt-get
Folks like so far until someone says otherwise there using a static IP
when provisioning a VM on vSphere from a template that includes cloud-
init just doesn't work.. is anyone open to have a WebEx/zoom session to
look into maybe understanding why this is still an issue.
i have tried
Hi Ryan
Can you please check the logs for this.. this a rising issue that is
happen quite often from customers i have dealt with.
Configuration
===
VMs to be provisioned on vSphere 6.7 U2
template is Ubuntu 16.04.6 LTS with Cloud-init 19.1 and Open-vm-tools 10304
(10.2.0)
sudo
This isn't going anywhere, nor getting any help .. please close the bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833623
Title:
VMware Guest OS Customization Fail for Ubuntu 16.04 with
I have been spending so many cycle on this, here are the Testing Tasks around
Ubuntu 16.04 Customization with Cloud-init on vSphere
and its expected behaviour
-
- Create an Ubuntu 16.04 Virtual Machine on vSphere 6.7 U2.
- Apply the latest updates and upgrades -> sudo apt-get update && sudo
Anyone i can work with live via a WebEx / zoom session on this,
dedicated a couple of hours please email me at maheralas...@gmail.com
and i ll send you an invite .. i just think this way its much a faster
way to troubleshoot this and get to a resolution
--
You received this bug notification
Test 14 Using DHCP
1- Install a fresh Ubuntu 16.04 Server
2- run sudo apt update && sudo apt upgrade
3- install Cloud init
4- if any delete /var/log/cloud-ini* from the VM before shutting it down and
converting it to a template
5- run dpkg-reconfigure cloud-init and only select OVF only.
6- run
Anyone can take a look .. if there was a training class for cloud-init
online i would take it. documentation also doesn't talk about the
process flow or show end to end examples. just cloud config syntax
example. its like here the code go figure it out!! very frustrating.
--
You received this
Another approach i followed. is https://kb.vmware.com/s/article/59557
where i m disabling guest customization with cloud-init
- Ubuntu 16.04 provisioned
- Network connected
- Ip provided from DHCP
- Hostname was updated this time
- Cloud config code wasn't deployed <--- Problem
logs attached.
Any Luck on the 2nd log collection based on what i followed in Step #9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833623
Title:
VMware Guest OS Customization Fail for Ubuntu 16.04 with
Hi Ryan
With the automation tool we are using we are passing the cloud config
user data information via an attached ISO via the vm CD-ROM .. should
using dpkg-reconfigure cloud-init command to select only OVF as a data
source should be enough in this case since we are only provision to
VMware
Hi Ryan
Based on the https://bugs.launchpad.net/ubuntu/+source/open-vm-
tools/+bug/1793715 which is really was around Ubuntu 18.04
i did the following after installing a new ubuntu 16.04 and turning into
a template
1- Install a fresh Ubuntu 16.04 Server
2- run sudo apt update && sudo apt
Hi Ryan
Based on the https://bugs.launchpad.net/ubuntu/+source/open-vm-
tools/+bug/1793715 which is really was around Ubuntu 18.04
i did the following after installing a new ubuntu 16.04 and turning into
a template
1- Install a fresh Ubuntu 16.04 Server
2- run sudo apt update && sudo apt
I think you'll want to run:
cloud-init clean --logs
After doing your changes to the images; this will remove most cloud-init
state.
--
cloud-init will always run on each boot that it detects that it has data to
process. So on VMWare, if an OVF iso is provided, or the vmdata is set in the
i guessing based on
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1793715
i can't really disable cloud-init cause i need to execute the cloud config code
that I'm pushing when i m provisioning the VM.. this leaves me that i need to
set cloud-init to do the customization here .
hi Ryan . thank you for taking the time.
this is a VMware Ubuntu 16.04 VM that later used as a template where we
installed cloud-init top . as we prepare the template we do reboot the
VM after .. i normally delete the cloud-init* logs from /var/log and
maybe i didn't here... unless there is a
Hrm, something looks a bit odd. In the collect logs, I can see that
cloud-init found an OVF attached to the instance, however in the cloud-
init.log there appears to be an existing boot of cloud-init already
present:
2019-06-21 15:33:41,226 - main.py[DEBUG]: Execution continuing, no previous run
Anyone else can help with this we are trying to make cloud-init work
when provisioning a ubuntu 16 on a sphere.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833623
Title:
VMware Guest OS
Sure thing! Attached
thank you for looking into this
this is a two machine deployment of Wordpress from an ubuntu 16.04
templated. Web and DB VMs . the tar ball is from the DB machine using a
static IP Range for connectivity and the setting mentioned in the
https://kb.vmware.com/s/article/56409
** Description changed:
Hello,
- I yet to find an answer and i know there has many bugs reported in the
- past and i really need to know what we need to do to get this to work.
+ I yet to find an answer and i know there has been many bugs reported in
+ the past and i really need to know what
Hi,
Could you run:
cloud-init collect-logs
and attach the tarball it creates?
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
Hello,
I yet to find an answer and i know there has many bugs reported in the
past and i really need to know what we need to do to get this to work.
Situation
An automation tool is used to provision Ubuntu 16 VMs to vSphere/ESXi
6.7 U2
- Steps I
27 matches
Mail list logo
