cloud-init fails when deploying CentOS with Juju.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Dimiter Naydenov | ||
1.24 |
Won't Fix
|
Low
|
Unassigned | ||
1.25 |
Fix Released
|
Critical
|
Dimiter Naydenov |
Bug Description
I was working with deploying a CentOS image on canonistack and I noticed that cloud-init failed and the juju agent was not installed.
Looking at the cloud-init.log file it appears a systemctl command in runcmd failed:
+ su ubuntu -c 'printf "%s\n" "$authorized_keys" >> ~/.ssh/
+ systemctl stop firewalld
Failed to issue method call: Unit firewalld.service not loaded.
2015-09-03 22:21:48,911 - util.py[WARNING]: Failed running /var/lib/
2015-09-03 22:21:48,931 - cc_scripts_
2015-09-03 22:21:48,931 - util.py[WARNING]: Running scripts-user (<module 'cloudinit.
It does not appear the firewalld service is loaded on this image
# systemctl status firewalld
firewalld.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
The image I was using is: CentOS-
Is it possible to check for this service before trying to stop it?
Changed in juju-core: | |
milestone: | none → 1.26-alpha1 |
importance: | Undecided → Critical |
status: | New → Triaged |
Changed in juju-core: | |
assignee: | nobody → Dimiter Naydenov (dimitern) |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
importance: | Critical → High |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Fix for 1.25 proposed: http:// reviews. vapour. ws/r/2637/