Puppet does not start automatically after it is first installed via apt causing the script to fail

Bug #759183 reported by Kevin Bringard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nova-deployment-tool
Opinion
Undecided
Shigetoshi Yokoyama

Bug Description

When installing puppet from apt, /etc/default/puppet has START=no by default. This causes puppet not to start and the rest of the deploy script fails to run.

I believe adding exec_cmd("sed -i 's/START=no/START=yes/' /etc/default/puppet && service puppet restart") after puppet is installed should resolve the issue, as it will set START=yes and then attempt to restart the puppet daemon.

Changed in nova-deployment-tool:
assignee: nobody → Shigetoshi Yokoyama (yoko)
Revision history for this message
Shigetoshi Yokoyama (yoko) wrote :

It is correct that puppet wasn't started automatically after it was
installed. It isn't the cause of the installation failure.

Puppet should not be lrun automatically, because the installation
sequence of nova components has to be managed by deploy.py.

Revision history for this message
Kevin Bringard (kbringard) wrote :

My apologies, I was filing the bug on behalf of someone else and that appeared to be their problem.

I meant to reference this in the original report, but here is the original question with the output from the script:

https://answers.launchpad.net/nova-deployment-tool/+question/152576

Changed in nova-deployment-tool:
status: New → Opinion
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.