Deployment fails with network-isolation and 1 node controller pacemaker setup

Bug #1473410 reported by Yanis Guenane on 2015-07-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
High
Yanis Guenane

Bug Description

When deploying with the following deployment is OK

export OVERCLOUD_CONTROLSCALE=3
export OVERCLOUD_COMPUTESCALE=1
export OVERCLOUD_CUSTOM_HEAT_ENV="$TRIPLEO_ROOT/tripleo-heat-templates/environments/puppet-pacemaker.yaml $TRIPLEO_ROOT/tripleo-heat-templates/environments/network-isolation.yaml $TRIPLEO_ROOT/tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml"

When deploying with the following deployment is KO

export OVERCLOUD_CONTROLSCALE=1
export OVERCLOUD_COMPUTESCALE=1
export OVERCLOUD_CUSTOM_HEAT_ENV="$TRIPLEO_ROOT/tripleo-heat-templates/environments/puppet-pacemaker.yaml $TRIPLEO_ROOT/tripleo-heat-templates/environments/network-isolation.yaml $TRIPLEO_ROOT/tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml"

Puppet fails at the following action :

Error: /Stage[main]/Main/Exec[neutron-server-start-wait-stop]/returns: change from notrun to 0 failed: systemctl start neutron-server && sleep 5s && systemctl stop neutron-server

Real issue is : NotFound: Exchange.declare: (404) NOT_FOUND - no exchange 'reply_2adbea77b5564b8fa832e4c106a24b9d' in vhost '/' (/var/log/neutron/server.log)

Changed in tripleo:
assignee: nobody → Yanis Guenane (yanis-guenane)

Fix proposed to branch: master
Review: https://review.openstack.org/201085

Changed in tripleo:
status: New → In Progress

Reviewed: https://review.openstack.org/201085
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=dcc66487cda9cabc3d830c5059d95aa285ef7543
Submitter: Jenkins
Branch: master

commit dcc66487cda9cabc3d830c5059d95aa285ef7543
Author: Yanis Guenane <email address hidden>
Date: Mon Jul 13 13:19:01 2015 +0200

    neutron-server: Remove start/sleep/stop pattern

    Currently the bootstrap of the neutron server happens with the use of a
    start/sleep/stop pattern.

    Since Pacemaker doesn't mind if the service is already started let
    simply start the neutron server on the $pacemaker_master node and wait
    for 5 sec.

    Change-Id: I894dc3305f7d6685ebcc6828e690c718a63f32bd
    Closes-Bug: #1473410

Changed in tripleo:
status: In Progress → Fix Committed
Changed in tripleo:
importance: Undecided → High
Steven Hardy (shardy) on 2016-04-21
Changed in tripleo:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers