[MCOL-925] cant remove or enable pm3 after pm2 was removed Created: 2017-09-14  Updated: 2023-10-26  Resolved: 2019-07-10

Status: Closed
Project: MariaDB ColumnStore
Component/s: ?
Affects Version/s: 1.1.0
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: David Hill (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Environment:

amazon system 1.1 testing



 Description   

during addmodule and removemodule testing. I added pm2 and pm3 modules.
then did a removemodule pm2, leaving pm1 and pm3.
now getting errors when I try to enable or remove pm3.

mcsadmin> removemodule pm3
removemodule Thu Sep 14 19:20:43 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

Removing Module(s) pm3, please wait...

Failed to Remove Module: Invalid Parameter passed in removeModule API

mcsadmin>
mcsadmin>
mcsadmin> altersystem-en pm3
altersystem-enablemodule Thu Sep 14 19:21:36 2017

This command starts the processing of applications on a Module within the MariaDB ColumnStore System
Do you want to proceed: (y or n) [n]: y

Enabling Modules

        • enableModule Failed : Invalid Parameter passed in enableModule API
          mcsadmin> getsystems
          getsystemstatus Thu Sep 14 19:21:45 2017

System 1.1.0

System and Module statuses

Component Status Last Status Change
------------ -------------------------- ------------------------
System ACTIVE Thu Sep 14 16:10:13 2017

Module pm1 ACTIVE Thu Sep 14 16:10:11 2017
Module pm3 MAN_DISABLED Thu Sep 14 18:58:54 2017

Active Parent OAM Performance Module is 'pm1'
Primary Front-End MariaDB ColumnStore Module is 'pm1'
MariaDB ColumnStore Replication Feature is enabled


Generated at Thu Feb 08 02:24:50 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.