cloud-init service still persists after deployment

Bug #1553733 reported by Sergey Kolekonov
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Medium
Sergey Kolekonov
8.0.x
Fix Released
Medium
Sergii Rizvan

Bug Description

9.0 ISO #54

cloud-init service persists after cluster deployment because its package is removed instead of being purged. It leads to long rebooting of all nodes (3+ minutes) as cloud-init service still tries to get configuration (a screenshot is attached)

Revision history for this message
Sergey Kolekonov (skolekonov) wrote :
Changed in fuel:
assignee: nobody → Sergey Kolekonov (skolekonov)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (master)

Fix proposed to branch: master
Review: https://review.openstack.org/289019

Changed in fuel:
status: New → In Progress
Changed in fuel:
milestone: none → 9.0
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (master)

Reviewed: https://review.openstack.org/289019
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=afadfa9ee1f3e1a7fbd23b6c5b7fd8383c21d769
Submitter: Jenkins
Branch: master

commit afadfa9ee1f3e1a7fbd23b6c5b7fd8383c21d769
Author: Sergey Kolekonov <email address hidden>
Date: Sun Mar 6 17:12:58 2016 +0300

    Disable cloud-init services after provisioning

    cloud-init services should be disabled after provisioning, otherwise they will
    try to get configuration on each reboot and increase booting time to ~2 minutes

    Change-Id: I3a0d811b0cee007d23a2bc85c62fa6b2bb54b45f
    Closes-bug: #1553733

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
Alexander Bozhenko (alexbozhenko) wrote :

Found that on 8.0 cloud-init is installed again, because of this commit:
https://github.com/openstack/fuel-library/commit/b78251b26984ddaca211f973ec4c2f88eafe992b

On 7.0 it was
/var/log/apt/history.log
Start-Date: 2015-10-05 22:24:32
Commandline: /usr/bin/apt-get -y -q remove --purge cloud-init
Purge: cloud-init:amd64 (0.7.5-0ubuntu1.12)
End-Date: 2015-10-05 22:24:32

On 8.0
/var/log/apt/history.log
Start-Date: 2016-03-16 13:59:51
Commandline: /usr/bin/apt-get -y -q remove cloud-init
Remove: cloud-init:amd64 (0.7.5-0ubuntu1.17)
End-Date: 2016-03-16 13:59:52

So on 8.0 cloud-init is actually present:
dpkg -L cloud-init
/etc
/etc/rsyslog.d
/etc/rsyslog.d/21-cloudinit.conf
/etc/profile.d
/etc/profile.d/Z99-cloud-locale-test.sh
/etc/init
/etc/init/cloud-init-local.conf
/etc/init/cloud-final.conf
/etc/init/cloud-init.conf
/etc/init/cloud-log-shutdown.conf
/etc/init/cloud-init-nonet.conf
/etc/init/cloud-config.conf
/etc/init/cloud-init-container.conf
...

And nodes are waiting for it on reboot... And if there is a metadata server in the network it may response with the script and, e.g. wipe disks on the node)

tags: added: on-verification
Revision history for this message
Kristina Berezovskaia (kkuznetsova) wrote :

Verify on
cat /etc/fuel_build_id:
 134
cat /etc/fuel_build_number:
 134
cat /etc/fuel_release:
 9.0
cat /etc/fuel_openstack_version:
 liberty-9.0
rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':
 fuel-library9.0-9.0.0-1.mos8223.noarch
 fuel-agent-9.0.0-1.mos270.noarch
 nailgun-mcagents-9.0.0-1.mos730.noarch
 python-packetary-9.0.0-1.mos128.noarch
 fuel-provisioning-scripts-9.0.0-1.mos8597.noarch
 network-checker-9.0.0-1.mos72.x86_64
 fuel-mirror-9.0.0-1.mos128.noarch
 fuel-openstack-metadata-9.0.0-1.mos8597.noarch
 fuel-notify-9.0.0-1.mos8223.noarch
 fuel-setup-9.0.0-1.mos6321.noarch
 python-fuelclient-9.0.0-1.mos299.noarch
 fuelmenu-9.0.0-1.mos263.noarch
 fuel-9.0.0-1.mos6321.noarch
 fuel-utils-9.0.0-1.mos8223.noarch
 fuel-nailgun-9.0.0-1.mos8597.noarch
 fuel-ostf-9.0.0-1.mos919.noarch
 fuel-release-9.0.0-1.mos6321.noarch
 rubygem-astute-9.0.0-1.mos730.noarch
 shotgun-9.0.0-1.mos85.noarch
 fuel-ui-9.0.0-1.mos2626.noarch
 fuel-migrate-9.0.0-1.mos8223.noarch
 fuel-misc-9.0.0-1.mos8223.noarch
 fuel-bootstrap-cli-9.0.0-1.mos270.noarch

Changed in fuel:
status: Fix Committed → Fix Released
tags: removed: on-verification
Revision history for this message
Alex Schultz (alex-schultz) wrote :

This affects 8.0 as well, see Bug #1597369

tags: added: customer-found support
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (stable/8.0)

Fix proposed to branch: stable/8.0
Review: https://review.openstack.org/347901

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (stable/8.0)

Reviewed: https://review.openstack.org/347901
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=120f60472b62247c2ecbb44bdf34d70fa3d2c345
Submitter: Jenkins
Branch: stable/8.0

commit 120f60472b62247c2ecbb44bdf34d70fa3d2c345
Author: Sergey Kolekonov <email address hidden>
Date: Sun Mar 6 17:12:58 2016 +0300

    Disable cloud-init services after provisioning

    cloud-init services should be disabled after provisioning, otherwise they will
    try to get configuration on each reboot and increase booting time to ~2 minutes

    Change-Id: I3a0d811b0cee007d23a2bc85c62fa6b2bb54b45f
    Closes-bug: #1553733
    (cherry picked from commit afadfa9ee1f3e1a7fbd23b6c5b7fd8383c21d769)

tags: added: on-verification
Revision history for this message
TatyanaGladysheva (tgladysheva) wrote :

Verified on MOS 8.0 + MU3 updates.

Steps to verify:
1. Reboot node and observe logs for this node in VNC.

Before updates:
During reboot 'cloud-init-nonet' increases booting time to 120 sec (as in comment #1).

After updates:
During reboot 'cloud-init-nonet' was not started. Reboot takes 120 sec less time.

tags: removed: on-verification
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.