virt-users] Network issues with oVirt 4.2 and cloud-init
Hello Sandy,
i had the same issue and the cause was cloud-init running again at
boot even if Run-Once hasn't been selected as boot option. The way i'm
using to solve the problem is to remove cloud-init after the first
run, si
Yes, I had the checkbox marked when I made the template.
From: Michael Burman [mailto:mbur...@redhat.com]
Sent: Tuesday, March 20, 2018 1:37 AM
To: Berger, Sandy
Cc: users@ovirt.org; Luca 'remix_tj' Lorenzetto
Subject: Re: [ovirt-users] Network issues with oVirt 4.2 and cloud-init
Hi Berger,
Have you sealed the template? if you didn't sealed the template on
creation, then your new VM has the same ifcfg-eth0 settings as your origin
VM.
In order to avoid this, you need to check the 'Seal Template (Linux only)'
checkbox in the New Template dialog.
Cheers)
On Mon, Mar 19, 201
Hello Sandy,
i had the same issue and the cause was cloud-init running again at
boot even if Run-Once hasn't been selected as boot option. The way i'm
using to solve the problem is to remove cloud-init after the first
run, since we don't need it anymore.
In case also disabling is enoug:
touch /e
We're using cloud-init to customize VMs built from a template. We're using
static IPV4 settings so we're specifying an IP address, subnet mask, and
gateway. There is apparently a bug in the current version of cloud-init
shipping as part of CentOS 7.4
(https://bugzilla.redhat.com/show_bug.cgi?id
5 matches
Mail list logo
