|Summary:||Disable cloud-init service after appliance deployment|
|Product:||[oVirt] ovirt-hosted-engine-setup||Reporter:||Artyom <alukiano>|
|Component:||General||Assignee:||Simone Tiraboschi <stirabos>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||Artyom <alukiano>|
|Version:||22.214.171.124||CC:||alukiano, bugs, dfediuck, didi, lveyde, mavital, rmartins, sabose, sbonazzo, stirabos, tlitovsk, ylavi|
|Target Milestone:||ovirt-3.6.3||Keywords:||Improvement, Performance, Triaged|
|Fixed In Version:||Doc Type:||Enhancement|
cloud-init services are now disabled on the engine-appliance after the initial deployment in order to speed up subsequent boots.
|Last Closed:||2016-03-11 07:23:34 UTC||Type:||Bug|
|oVirt Team:||Integration||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
|Bug Blocks:||1258386, 1305885|
Description Artyom 2016-01-17 10:17:45 UTC
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): ovirt-hosted-engine-setup-126.96.36.199-2.el7ev.noarch How reproducible: Always Steps to Reproduce: 1. Deploy hosted-engine via appliance 2. Wait for start of HE vm after deployment 3. Actual results: Start of vm takes too much time(because cloud-init timeout) Expected results: Start of vm not take too much time Additional info:
Comment 1 Yaniv Kaul 2016-01-17 10:31:14 UTC
I believe running: systemctl mask cloud-final.service and systemctl mask cloud-config.service Should do the trick. Is this a bug or a RFE?
Comment 2 Artyom 2016-01-17 11:53:54 UTC
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.
Comment 3 Yaniv Kaul 2016-01-17 11:59:47 UTC
(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 )
Comment 4 Artyom 2016-01-17 13:54:41 UTC
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(
Comment 5 Simone Tiraboschi 2016-01-19 16:04:20 UTC
(In reply to Yaniv Kaul from comment #1) > I believe running: > systemctl mask cloud-final.service > and > 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.
Comment 6 Sandro Bonazzola 2016-01-19 21:01:33 UTC
Impacting downtime and boot performances, I think this should be addressed in 3.6.
Comment 7 Artyom 2016-02-17 13:31:04 UTC
Created attachment 1127945 [details] screenshot Checked on ovirt-hosted-engine-setup-188.8.131.52-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
Comment 8 Red Hat Bugzilla Rules Engine 2016-02-17 13:31:26 UTC
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.
Comment 10 Simone Tiraboschi 2016-02-22 10:29:40 UTC
(In reply to Artyom from comment #7) > Created attachment 1127945 [details] > screenshot > > Checked on ovirt-hosted-engine-setup-184.108.40.206-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?
Comment 11 Artyom 2016-02-22 11:28:03 UTC
I believe you right. OS on appliance RHEL6.7.
Comment 14 Artyom 2016-02-25 11:54:26 UTC
Verified on ovirt-hosted-engine-setup-220.127.116.11-1.el7ev.noarch