getsystemstatus and getprocessstatus returned different statuses

Build tested: 1.1.6-1 source
/root/columnstore/mariadb-columnstore-server
commit 513775738f72ec990d055a5d47e2511e3c0e34dd
Merge: 3c37210 9236098
Author: Andrew Hutchings <andrew@linuxjedi.co.uk>
Date: Wed Jul 18 09:37:17 2018 +0100

Merge pull request #123 from drrtuy/MCOL-970

MCOL-970 Slow query log now contains original query even in vtable mode

/root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine
commit 150171b714c16bd91ef620ea483f6200ad775038
Merge: 1068679 8a42949
Author: benthompson15 <ben.thompson@mariadb.com>
Date: Thu Aug 9 17:49:01 2018 -0500

Merge pull request #535 from mariadb-corporation/MCOL-1605

MCOL-1605 - changed error to debug, alarms trying to get issued befor…

Test environment: 1um4pm gluster

This issue was encountered when testing MCOL-1610

When PM2 recovered after failure, processes on PM2 showed up as normal, came out from AUTO_OFFLINE. Then I believe dbroot2 failed to mount (on purpose), in getsystemstatus, it showed:

mcsadmin> getsystemstatus
getsystemstatus Mon Aug 13 20:00:41 2018

System vagrantTestStack

System and Module statuses

Component Status Last Status Change
------------ -------------------------- ------------------------
System ACTIVE Mon Aug 13 19:49:47 2018

Module um1 ACTIVE Mon Aug 13 17:12:05 2018
Module pm1 ACTIVE Mon Aug 13 17:11:36 2018
Module pm2 MAN_OFFLINE Mon Aug 13 19:58:34 2018
Module pm3 ACTIVE Mon Aug 13 19:29:22 2018
Module pm4 ACTIVE Mon Aug 13 19:29:23 2018

But getprocessstatus showed:

ProcessMonitor pm2 ACTIVE Mon Aug 13 19:49:35 2018 4040
ProcessManager pm2 HOT_STANDBY Mon Aug 13 19:58:44 2018 11086
DBRMControllerNode pm2 COLD_STANDBY Mon Aug 13 19:49:37 2018
ServerMonitor pm2 ACTIVE Mon Aug 13 19:49:38 2018 4330
DBRMWorkerNode pm2 ACTIVE Mon Aug 13 19:58:58 2018 11129
DecomSvr pm2 ACTIVE Mon Aug 13 19:49:40 2018 4359
PrimProc pm2 ACTIVE Mon Aug 13 19:59:13 2018 11153
WriteEngineServer pm2 ACTIVE Mon Aug 13 19:59:21 2018 11200

This one is a tough judgment call. The processes are in fact running. In that regard, getprocessstatus is correct. At the same time, getSystem is showing the module as OFFLINE. Maybe that is correctly too. It is just confuse to me as an user.