Remove cloud-init package
Bug #1445002 reported by
OpenStack Infra
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel Documentation Team |
Bug Description
https:/
commit f4a20cc84ebd40e
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:/
Change-Id: I1600a3538cf8b7
Closes-bug: #1442572
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 |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
tags: | added: area-docs |
To post a comment you must log in.
Found that on 8.0 cloud-init is installed again, because of this commit: /github. com/openstack/ fuel-library/ commit/ b78251b26984dda ca211f973ec4c2f 88eafe992b
https:/
On 7.0 it was apt/history. log
/var/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 apt/history. log
/var/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: d/21-cloudinit. conf d/Z99-cloud- locale- test.sh cloud-init- local.conf cloud-final. conf cloud-init. conf cloud-log- shutdown. conf cloud-init- nonet.conf cloud-config. conf cloud-init- container. conf
dpkg -L cloud-init
/etc
/etc/rsyslog.d
/etc/rsyslog.
/etc/profile.d
/etc/profile.
/etc/init
/etc/init/
/etc/init/
/etc/init/
/etc/init/
/etc/init/
/etc/init/
/etc/init/
...
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)