Description of problem:
I believe we need to disable cloud-init service after we finish deployment via appliance, because it take additional 2 minutes on boot of OS(cloud-init trying to find configuration and failed after timeout)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Deploy hosted-engine via appliance
2. Wait for start of HE vm after deployment
Start of vm takes too much time(because cloud-init timeout)
Start of vm not take too much time
I believe running:
systemctl mask cloud-final.service
systemctl mask cloud-config.service
Should do the trick.
Is this a bug or a RFE?
I think it more like RFE, but if we want to reduce down time of the engine, it necessary to disable cloud-init service on start up.
(In reply to Artyom from comment #2)
> I think it more like RFE, but if we want to reduce down time of the engine,
> it necessary to disable cloud-init service on start up.
I fully agree - I think it's an important one to implement (and hopefully as easy as I've described above).
(BTW, perhaps there's a way to shorten the timeout for cloud-init - see bug 1039388 )
Yes, looks like fix for the bug 1039388, can help us, but I also see, that bug exist from 6.5 and it still has status new(
(In reply to Yaniv Kaul from comment #1)
> I believe running:
> systemctl mask cloud-final.service
> systemctl mask cloud-config.service
> Should do the trick.
Doing it via cloud-init itself is pretty easy but of-course it will be effective only if the user will decide to use cloud-init.
If not it will be up to him to stop it since it's enabled by default on the appliance.
Impacting downtime and boot performances, I think this should be addressed in 3.6.
Created attachment 1127945 [details]
Checked on ovirt-hosted-engine-setup-220.127.116.11-1.el7ev.noarch
I can see that cloud-init still enabled on startup(see screenshot).
I do not really sure that mask help to avoid cloud-init startup, why just do not send:
systemctl disable cloud-init
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Created attachment 1127946 [details]
(In reply to Artyom from comment #7)
> Created attachment 1127945 [details]
> Checked on ovirt-hosted-engine-setup-18.104.22.168-1.el7ev.noarch
> I can see that cloud-init still enabled on startup(see screenshot).
> I do not really sure that mask help to avoid cloud-init startup, why just do
> not send:
> systemctl disable cloud-init
mask is stronger than disable; was your appliance el7 or el6 based?
I believe you right.
OS on appliance RHEL6.7.
Verified on ovirt-hosted-engine-setup-22.214.171.124-1.el7ev.noarch