Juniper Openstack

service stop or restart of api is restarting all services in config

Bug #1362421 reported by Hari Prasad Killi
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Juniper Openstack
Fix Committed
High
Prakash Bailkeri
R1.1
Fix Committed
High
Prakash Bailkeri

Bug Description

In R1.10, build 26, when I do "service contrail-api stop", all "Contrail Config" including supervisor-config are restarted and at the end, api is started again.

Service restart also is restarting all processes.

Revision history for this message
Hari Prasad Killi (haripk) wrote :

This is done through
/etc/contrail/supervisord_config_files/contrail-config.rules

config guys have decided to do a supervisor restart on api server restart..
You can temporarily change
/etc/contrail/supervisord_config_files/contrail-config.rules
to not do the restart..

-
Raj

Changed in juniperopenstack:
status: New → Invalid
Sundaresan Rajangam (srajanga)
Changed in juniperopenstack:
status: Invalid → New
assignee: c mishra (cdmishra) → nobody
Revision history for this message
Sundaresan Rajangam (srajanga) wrote :

/etc/contrail/supervisord_config_files/contrail-config.rules

{ "Rules": [
    {"processname": "contrail-api", "process_state": "PROCESS_STATE_STOPPED", "action": "service supervisor-config restart"},
    {"processname": "contrail-api", "process_state": "PROCESS_STATE_EXITED", "action": "service supervisor-config restart"},
    {"processname": "contrail-api", "process_state": "PROCESS_STATE_FATAL", "action": "service supervisor-config restart"},
    {"processname": "ifmap", "process_state": "PROCESS_STATE_STOPPED", "action": "service supervisor-config restart"},
    {"processname": "ifmap", "process_state": "PROCESS_STATE_EXITED", "action": "service supervisor-config restart"},
    {"processname": "ifmap", "process_state": "PROCESS_STATE_FATAL", "action": "service supervisor-config restart"}
     ]
}

"processname": "contrail-api", "process_state": "PROCESS_STATE_STOPPED", "action": "service supervisor-config restart"
"processname": "ifmap", "process_state": "PROCESS_STATE_STOPPED", "action": "service supervisor-config restart"

The above two rules doesn't seem correct.
If the user stops contrail-api or ifmap service, all the services in contrail-config is restarted. This not the expected behavior. Perhaps, we may want to restart all the services expect for the service being stopped by the user?

Changed in juniperopenstack:
assignee: nobody → Prakash Bailkeri (prakashmb)
Sudheendra Rao (sudheendra-k)
tags: added: releasenote
Ashish Ranjan (aranjan-n)
information type: Proprietary → Public
Revision history for this message
Prakash Bailkeri (prakashmb) wrote :

Issue is resolved with
https://github.com/Juniper/contrail-controller/commit/4da565788934c422e00de70bd35f746333e2b06e

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

Subscribing...

Other bug subscribers

Remote bug watches

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