-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.3.15
-
Fix Version/s: 2.4.6
-
Component/s: maxctrl
-
Labels:None
Creating services or linking objects sometimes return an error message that it's too generic: "Invalid object relations for".
This same message is returned for very different errors:
$ maxctrl create service "DynamicService003" readwritesplit master_accept_reads=true user=maxuser password=maxpwd --filters=MyFilter001,MyFilter002
|
Error: Server at localhost:8989 responded with status code 403 to `POST services`:{
|
"errors": [
|
{
|
"detail": "Invalid object relations for 'DynamicService003'"
|
}
|
]
|
}
|
|
The above is a syntax error, filters syntax is: --filters MyFilter001 MyFilter002
This case below is when trying to link a monitor to a non existing server:
$ maxctrl link monitor MariaDB-Monitor NonExistingServer
|
Error: Server at localhost:8989 responded with status code 403 to `PATCH monitors/MariaDB-Monitor`:{
|
"errors": [
|
{
|
"detail": "Invalid object relations for 'MariaDB-Monitor'"
|
}
|
]
|
}
|