puppet-tripleo rabbitmq profile assumes rabbitmq is running at step1 during stack-update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
James Slagle |
Bug Description
puppet-
if $step >= 1 {
<snip>
# In case of HA, starting of rabbitmq-server is managed by pacemaker, because of which, a dependency
# to Service[
if $stack_action == 'UPDATE' {
# Required for changing password on update scenario. Password will be changed only when
# called explicity, if the rabbitmq service is already running.
rabbitmq_user { $rabbitmq_user :
password => $rabbitmq_pass,
provider => 'rabbitmqctl',
admin => true,
}
}
That assumes that rabbitmq is running at step1 on stack-update since the rabbitmq_user resource will use rabbitmqctl to check if the user exists.
The issue is that if you are updating a failed stack that never made it to step2, then rabbitmq won't be running, since it is not started until step2.
The stack-update then fails with:
Error: /Stage[
Changed in tripleo: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → James Slagle (james-slagle) |
milestone: | none → pike-1 |
Fix proposed to branch: master /review. openstack. org/448803
Review: https:/