On Tue, Sep 15, 2015 at 3:53 AM, Dimiter Naydenov <
<email address hidden>> wrote:
> ** Changed in: juju-core
> Status: Triaged => In Progress
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1492066
>
> Title:
> cloud-init fails when deploying CentOS with Juju.
>
> Status in juju-core:
> In Progress
> Status in juju-core 1.25 series:
> In Progress
>
> 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/authorized_keys'
> + 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/cloud/instance/scripts/runcmd [5]
> 2015-09-03 22:21:48,931 - cc_scripts_user.py[WARNING]: Failed to run
> module scripts-user (scripts in /var/lib/cloud/instance/scripts)
> 2015-09-03 22:21:48,931 - util.py[WARNING]: Running scripts-user
> (<module 'cloudinit.config.cc_scripts_user' from
> '/usr/lib/python2.7/site-packages/cloudinit/config/cc_scripts_user.pyc'>)
> failed
>
> 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-7-x86_64-GenericCloud-1503
>
> Is it possible to check for this service before trying to stop it?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1492066/+subscriptions
>
Hello Dimiter,
Thanks for working on this!
- Matt Bruzek <email address hidden>
On Tue, Sep 15, 2015 at 3:53 AM, Dimiter Naydenov <
<email address hidden>> wrote:
> ** Changed in: juju-core /bugs.launchpad .net/bugs/ 1492066 authorized_ keys' cloud/instance/ scripts/ runcmd [5] user.py[ WARNING] : Failed to run cloud/instance/ scripts) config. cc_scripts_ user' from python2. 7/site- packages/ cloudinit/ config/ cc_scripts_ user.pyc' >) 7-x86_64- GenericCloud- 1503 /bugs.launchpad .net/juju- core/+bug/ 1492066/ +subscriptions
> Status: Triaged => In Progress
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> cloud-init fails when deploying CentOS with Juju.
>
> Status in juju-core:
> In Progress
> Status in juju-core 1.25 series:
> In Progress
>
> 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_
> module scripts-user (scripts in /var/lib/
> 2015-09-03 22:21:48,931 - util.py[WARNING]: Running scripts-user
> (<module 'cloudinit.
> '/usr/lib/
> failed
>
> 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?
>
> To manage notifications about this bug go to:
> https:/
>