Juniper Openstack

  1. Bug #1362421
  2. Comment #2

Comment 2 for bug 1362421

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?