Error messages referenced an invalid OAM command unassignPmDbrootConfig

Build tested: Github source 1.1.0

[root@localhost mariadb-columnstore-server]# git show
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

mcsadmin> removemodule pm3
removemodule Wed May 31 20:26:03 2017

!!!!! DESTRUCTIVE COMMAND !!!!!

This command does a stop and remove a module from the MariaDB ColumnStore System
Do you want to proceed: (y or n) [n]: y

• • • • removeModule Failed : pm3 has dbroots still assigned. Please run movePmDbrootConfig or unassignPmDbrootConfig.

The returned messages referenced the unassignPmDbrootConfig, which is not an OAM command. The command should be unassignDbrootPmConfig.

1.0.10 should be affected by this too, although I did not test for it.