RabbitMQ server dosn't support option set_policy ha-all on stable/4.1

Bug #1312047 reported by Nastya Urlapova
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Critical
Roman Vyalov

Bug Description

{
build_id: "2014-04-24_04-17-26",
mirantis: "yes",
build_number: "288",
nailgun_sha: "93a01d7f5e58328f2ea53a10b266dfcc61df343d",
ostf_sha: "3690709d95c1f42506b6d955b44221910cec8527",
fuelmain_sha: "3b872b132c22f9014b82862b492ae2889226ae2f",
astute_sha: "55df06b2e84fa5d71a1cc0e78dbccab5db29d968",
release: "4.1B",
fuellib_sha: "73939a65c98f04842a50ec02d5ec3fc06ef702b8"
}

/etc/init.d/rabbitmq-server start
Starting rabbitmq-server: RabbitMQ is going to make 3 attempts to find master node and start.
3 attempts left to start RabbitMQ Server before consider start failed.
SUCCESS
Error: invalid command 'set_policy ha-all . {"ha-mode":"all", "ha-sync-mode":"automatic"}'
Usage:
rabbitmqctl [-n <node>] [-q] <command> [<command options>]

Options:
    -n node
    -q

Default node is "rabbit@server", where server is the local host. On a host
named "server.example.com", the node name of the RabbitMQ Erlang node will
usually be rabbit@server (unless RABBITMQ_NODENAME has been set to some
non-default value at broker startup time). The output of hostname -s is usually
the correct suffix to use after the "@" sign. See rabbitmq-server(1) for
details of configuring the RabbitMQ broker.

Quiet output mode is selected with the "-q" flag. Informational messages are
suppressed when quiet mode is in effect.

Tags: rabbit
Revision history for this message
Nastya Urlapova (aurlapova) wrote :
Revision history for this message
Nastya Urlapova (aurlapova) wrote :
Changed in fuel:
assignee: nobody → Dmitry Borodaenko (dborodaenko)
Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

there are two ways to fix this bug:

1) merge RabbitMQ 3.x packages into 4.1 repository and corresponding updated init script
2) revert this patch, that uses rabbitmq 3.x

I think, preferrable is #1, but we need to make sure that corresponding astute patch will also be merged into stable/4.1 branch

Changed in fuel:
status: New → Confirmed
Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix proposed to fuel-main (stable/4.1)

Fix proposed to branch: stable/4.1
Review: https://review.openstack.org/90091

Changed in fuel:
status: Confirmed → In Progress
assignee: Dmitry Borodaenko (dborodaenko) → Roman Vyalov (r0mikiam)
Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

Agreed on RabbitMQ upgrade being the preferrable solution:
https://bugs.launchpad.net/fuel/+bug/1278336

Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix merged to fuel-main (stable/4.1)

Reviewed: https://review.openstack.org/90091
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=595fc380caa60bdfcc63072d15485a499e09c07a
Submitter: Jenkins
Branch: stable/4.1

commit 595fc380caa60bdfcc63072d15485a499e09c07a
Author: Roman Vyalov <email address hidden>
Date: Thu Apr 24 18:15:57 2014 +0400

    Remove hardcode verion in requirelments.rpm

    Remove verison for rabbitmq and qemu

    Change-Id: I247cf2625484c397be49a65806b887c275cfc71f
    Closes-bug: #1312047

Roman Vyalov (r0mikiam)
Changed in fuel:
status: In Progress → Fix Committed
Changed in fuel:
status: Fix Committed → Fix Released
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.