switch master in a no promotion list

Maxscale master switch operation is permitted to a server even if the server is in the no_promotion_master list on the monitor

• there are no warning once the switch completed that the server is part of the no_promotion
• this leave the runtime configuration inconstant, cause if the maxscale restart there will be no master anymore

Also there are even issue with the other maxscales in cooperative locking with the same configuration

The expected behavior to me would be:

in the conf:
servers_no_promotion = mydb1

maxctrl call command mariadbmon switchover MariaDB-Monitor mydb1
FAIL you cant promote a master in servers_no_promotion list, please remove it from the list first,

maxctrl alter monitor MariaDB-Monitor servers_no_promotion=''

and then

maxctrl call command mariadbmon switchover MariaDB-Monitor mydb1
OK

the runtime configuration , need to leave the maxscale in the same status in case it restart, so i have a master, maxscale restart, i have the same.
Instead this is a no expected behavior. cause as it this now

• we switch a master a server that is in no-promotion-list
• we restart maxscale
• we dont have the same master

The other maxscale that are in cooperative locking configuration but do not have the lock, they 'refuse' to report the mydb1 as primary, if is on no_promotion_list and has been switch by the maxscale that have the lock, even you restart the maxscales with no lock you end up with the montitor reporting no same same master ( it refuse)