State for non-master schema should be Standby instead of initializing

Bug #1374313 reported by Kumar Harsh
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Juniper Openstack
Fix Committed
Undecided
Raj Reddy
R1.1
Won't Fix
High
Raj Reddy

Bug Description

Build 41 Ubuntu havana :
env.roledefs = {
    'all': [host1, host2, host3, host4, host5],
    'cfgm': [host1, host2, host3],
    'openstack': [host2],
    'control': [host2, host3],
    'compute': [host4, host5],
    'collector': [host1],
    'webui': [host1],
    'database': [host1, host2],
    'build': [host_build],
}

env.hostnames = {
    'all': ['nodec6', 'nodec7', 'nodec8', 'nodec9', 'nodec10']
}

active schema on nodec6 :
root@nodec6:/opt/contrail/utils# contrail-status
== Contrail Analytics ==
supervisor-analytics: active
contrail-analytics-api active
contrail-analytics-nodemgr active
contrail-collector active
contrail-query-engine active

== Contrail Config ==
supervisor-config: active
contrail-api:0 active
contrail-config-nodemgr active
contrail-discovery:0 active
contrail-schema active
contrail-svc-monitor active
ifmap active
rabbitmq-server active

== Contrail Web UI ==
supervisor-webui: active
contrail-webui active
contrail-webui-middleware active
redis-webui active

== Contrail Database ==
supervisord-contrail-database:active
contrail-database active
contrail-database-nodemgr active

But on other two config nodes it is in initializing state which should be standby :
root@nodec7:~# contrail-status
== Contrail Control ==
supervisor-control: active
contrail-control active
contrail-control-nodemgr active
contrail-dns active
contrail-named active

== Contrail Config ==
supervisor-config: active
contrail-api:0 active
contrail-config-nodemgr active
contrail-discovery:0 active
contrail-schema initializing <====== Here initializing
contrail-svc-monitor initializing
ifmap active
rabbitmq-server active

== Contrail Database ==
supervisord-contrail-database:active
contrail-database active
contrail-database-nodemgr active

root@nodec8:~# contrail-status
== Contrail Control ==
supervisor-control: active
contrail-control active
contrail-control-nodemgr active
contrail-dns active
contrail-named active

== Contrail Config ==
supervisor-config: active
contrail-api:0 active
contrail-config-nodemgr active
contrail-discovery:0 active
contrail-schema initializing <====== Here initializing
contrail-svc-monitor initializing
ifmap active
rabbitmq-server active

Revision history for this message
Vedamurthy Joshi (vedujoshi) wrote :

It causes lot of questions in the field if it is "initializing"...looks as if something is wrong

Changed in juniperopenstack:
assignee: nobody → Megh Bhatt (meghb)
Revision history for this message
Megh Bhatt (meghb) wrote :

I would think that initializing is the right thing to show on non-master schema since it really is initializing, moving to Sachin to decide

Changed in juniperopenstack:
assignee: Megh Bhatt (meghb) → Sachin Bansal (sbansal)
information type: Proprietary → Public
tags: added: releasenote
Sachin Bansal (sbansal)
Changed in juniperopenstack:
assignee: Sachin Bansal (sbansal) → Raj Reddy (rajreddy)
Revision history for this message
Raj Reddy (rajreddy) wrote :

Fixed through

commit 2c42a6505b2e96d9f84e4988e0a2ef851d8028b4
Author: Raj Reddy <email address hidden>
Date: Wed Feb 11 12:06:09 2015 -0800

    for some contrail services like contrail-schema, we should show them
    as backup in contrail-status when they are not active

    Change-Id: I8d166b507889e18df2eeb95e14c99ac46b2f498e

Changed in juniperopenstack:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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