[MXS-4170] Bad `create monitor` command leaves a ghost monitor Created: 2022-06-20  Updated: 2022-06-23  Resolved: 2022-06-23

Status: Closed
Project: MariaDB MaxScale
Component/s: REST-API
Affects Version/s: 6.4.0
Fix Version/s: 6.4.1

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None


 Description   

When the creation of a monitor fails at runtime, if another monitor already monitors one of the servers given in the initial servers relationship, the "unclaimed" servers that aren't monitored by anything are permanenty linked with the monitor being created. This causes further attempts to use them to fail with an error that states they are already monitored by another monitor.

The following commands will reproduce the problem:

maxctrl create server server1 127.0.0.1 3000
maxctrl create monitor MariaDB-Monitor mariadbmon user=maxuser password=maxpwd --servers server1 server1


Generated at Thu Feb 08 04:26:42 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.