Red Hat Bugzilla – Bug 836269
systemd timeout on cloud-init scripts
Last modified: 2012-09-26 05:03:39 EDT
If the init script takes longer than 90 seconds to finish (e.g. package installation & provisioning on slow network), it gets killed by systemd.
Adding `TimeoutSec=0` to cloud-final.service seems to fix the problem.
Version-Release number of selected component (if applicable):
Version : 0.6.3
Release : 0.2.bzr532.fc17
This happens both on Fedora 16 and 17.
cloud-init-0.6.3-0.5.bzr532.fc16 has been submitted as an update for Fedora 16.
cloud-init-0.6.3-0.5.bzr532.fc17 has been submitted as an update for Fedora 17.
cloud-init-0.6.3-0.5.bzr532.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing cloud-init-0.6.3-0.5.bzr532.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
cloud-init-0.6.3-0.5.bzr532.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
cloud-init-0.6.3-0.5.bzr532.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
cloud-init-0.6.3-0.5.bzr532.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.