SM : Purging the packages leaves the server manager process to run
Bug #1555601 reported by
sundarkh
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Fix Committed
|
High
|
Dheeraj Gautam | |||
Trunk |
Fix Committed
|
High
|
Dheeraj Gautam |
Bug Description
SM : Purging the packages leaves the server manager process to run
1) Install Server Manager , ./setup.sh --al l under /opt/contrail/
2) Make sure the process is runing,under ps -eaf | grep contrail , lets says PID is 4000
3) Now, Purge the Server Manager package, using dpkg -P <ServerManagerP
4)Observe that the PID of Server Manager is still alive (PID 4000)
Impact :
During ServerManager upgrade, when the SM admin, purges the packages , and installs the new server manager , New Server Manager does not start (due to the old PID is alive)
There should be a error message, that the old SM process is still alive
To post a comment you must log in.
"2016-03-15 00:51:00, 025-DEBUG- server_ mgr_main. py:2666- reimage_ server( ): reimage_server" 026-DEBUG- server_ mgr_main. py:1047- validate_ smgr_request( ): validate_ smgr_request" 028-DEBUG- server_ mgr_main. py:1072- validate_ smgr_request( ): ret_val_data returned: {'status': 0, 'match_key': 'cluster_id', 'do_reboot': True, 'match_value': u'cluster_multi', 'package_image_id': None, 'base_image_id': u'ubuntu-14-04'}" 070-DEBUG- server_ mgr_main. py:2837- reimage_ server( ): reimage queued. Number of servers reimaged is 4:" 282-DEBUG- server_ mgr_main. py:2954- _reimage_ server_ cobbler( ): reimage processed from queue" 497-DEBUG- server_ mgr_main. py:2954- _reimage_ server_ cobbler( ): reimage processed from queue" 726-DEBUG- server_ mgr_main. py:2954- _reimage_ server_ cobbler( ): reimage processed from queue" 948-DEBUG- server_ mgr_main. py:2954- _reimage_ server_ cobbler( ): reimage processed from queue" 948-DEBUG- server_ mgr_main. py:2976- _reimage_ server_ cobbler( ): reimage_ server_ cobbler failed: list index out of range
"2016-03-15 00:51:00,
"2016-03-15 00:51:00,
"2016-03-15 00:51:00,
"2016-03-15 00:51:00,
"2016-03-15 00:51:00,
"2016-03-15 00:51:00,
"2016-03-15 00:51:00,
"2016-03-15 00:51:00,
Faced again this issue,with R2.21.x-29 Juno
1) SM had a running mainline 2720 2) Installed 2.21.x-29 juno sanity got triggered , and server manager got installed
3) But the server manager process still pointed to old pid , restricting the new SM process to initiate (User is unaware of this , since no error message comes)