New module got added to the stack when the addmodule command failed

Build tested: Github source 1.1.0
commit 349cae544b6bc71910267a3b3b0fa3fb57b0a587
Merge: bd13090 2ecb85c
Author: benthompson15 <ben.thompson@mariadb.com>
Date: Thu May 4 16:06:16 2017 -0500
[root@localhost mariadb-columnstore-engine]# git show
commit 2cc5fc7195a76ce6ff475ba85f67123ec94b9fbe
Author: david hill <david.hill@mariadb.com>
Date: Tue May 30 15:12:50 2017 -0500
I did a non-distributed installation for a 1um2pm stack, the tried to add pm3, using a node that did not have ColumnStore files installed. The addmodule command failed expected. But the getprocessstatus command showed pm3 as part of the stack.

To correct the issue, the user needs to use the removemodule command to remove it.

My understanding is that this issue is not new. If affects existing releases.

OAM should either add the new module to the configuration file upon successful installation, or remove it if installation failed.