The rabbitmq.config parameters heartbeat, handshake_timeout aren't specified

Bug #1560687 reported by Dmitry Dmitriev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Michael Polenchuk

Bug Description

Detailed bug description:

 File /etc/rabbitmq/rabbitmq.config doesn't include parameters heartbeat, handshake_timeout.
 There is no ways to specify they values.

Steps to reproduce:

 1. Create new cluster with default parameters.
 2. Choose one node for controller role, one node for compute.
 3. Perform deployment.
 4. SSH to controller node.
 5. Cat /etc/rabbitmq/rabbitmq.config

Expected results:

 File rabbimq.config contains parameters heartbeat, handshake_timeout with specified values.

Actual result:

 There are no parameters heartbeat, handshake_timeout in rabbitmq.config file

Reproducibility:

  Every time during cloud deployment.

Workaround:

 No workaround.

Impact:

 Customer can't deploy clouds with important parameters. Deployment without specified parameters is not acceptable so this has to be addressed as soon as possible.

Description of the environment:

 Versions of components: {"release": "9.0", "auth_required": true, "api": "1", "openstack_version": "liberty-9.0", "feature_groups": []}
 Operation system: Ubuntu 14.04.4
 Reference architecture: HA and non-HA
 Network model: Neutron+Contrail
 Related projects installed:

Additional information:

summary: - The rabbimq.config parameters heartbeat, handshake_timeout aren't
+ The rabbitmq.config parameters heartbeat, handshake_timeout aren't
specified
description: updated
Changed in fuel:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Fuel Library Team (fuel-library)
milestone: none → 9.0
tags: added: customer-found
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Michael Polenchuk (mpolenchuk)
tags: added: area-library rabbitmq
Revision history for this message
Michael Polenchuk (mpolenchuk) wrote :

This is actually not true.
All rabbit.* config options could be handled by 'rabbit_config_variables' in hiera.
For example:
  rabbit_config_variables:
    heartbeat: 60
    handshake_timeout: 10000

Note: "heartbeat" in seconds, "handshake_timeout" in milliseconds.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to fuel-library (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/296415

Changed in fuel:
status: Triaged → Invalid
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to fuel-library (master)

Reviewed: https://review.openstack.org/296415
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=9cec7696d1f39a6d339e497afcee31292cb7224e
Submitter: Jenkins
Branch: master

commit 9cec7696d1f39a6d339e497afcee31292cb7224e
Author: Michael Polenchuk <email address hidden>
Date: Wed Mar 23 15:26:00 2016 +0300

    Merge rabbitmq default config vars w/ custom ones

    Merge all sources of rabbitmq config variables in order to
    avoid the default settings loss in case when custom config
    options come from hiera.

    Change-Id: I572bd72b6c9571a49deec9ee683f8e0d76bed9ae
    Related-Bug: #1560687

Changed in fuel:
status: Invalid → Fix Committed
Vladimir (vushakov)
tags: added: on-verification
Revision history for this message
Vladimir (vushakov) wrote :

Bug was reproduced on Fuel 9.0 ISO #142. Scenario:
1. Create new environment.
2. Add 1 controller and 1 compute.
3. Deploy changes.
4. SSH to controller node and cat /etc/rabbitmq/rabbitmq.config

heartbeat and handshake_timeout are missing from rabbitmq.config

tags: removed: on-verification
Changed in fuel:
status: Fix Committed → Confirmed
Revision history for this message
Michael Polenchuk (mpolenchuk) wrote :

Please read the comment #1.

Changed in fuel:
status: Confirmed → Fix Committed
Revision history for this message
Vladimir (vushakov) wrote :

Verified on:
    Fuel 9.0 ISO #157

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.