Remove cloud-init package

Bug #1445002 reported by OpenStack Infra on 2015-04-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Medium
Fuel Documentation Team

Bug Description

https://review.openstack.org/172370
commit f4a20cc84ebd40e75b65030f8131d7964c5b1dde
Author: Stanislav Makar <email address hidden>
Date: Fri Apr 10 10:42:07 2015 +0000

    Remove cloud-init package

    Cloud-init package is already present if IBP is used and we do not use it at all.
    It just lead that during reboot node is waiting 120 seconds.

    DocImpact: Please mention that we remove cloud-init after first reboot
       https://review.openstack.org/#/c/147675/

    Change-Id: I1600a3538cf8b758a098e0f770db176539192976
    Closes-bug: #1442572

Dmitry Pyzhov (dpyzhov) on 2015-04-16
tags: added: docs
removed: fuel-library
Changed in fuel:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Fuel Documentation Team (fuel-docs)
milestone: none → 6.1
Changed in fuel:
milestone: 6.1 → 7.0
Igor Shishkin (teran) on 2015-10-08
Changed in fuel:
milestone: 7.0 → 8.0
Dmitry Pyzhov (dpyzhov) on 2015-10-22
tags: added: area-docs

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)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers