Mysql-router in blocked state after mysql-innodb-cluster went donw

[Hybrid512]

Hi,

I did some crash testing against my Juju deployed Openstack cluster.
In some cases, when the Mysql-innodb-cluster goes down the mysql-router subordinate enters in "blocked" state because it can't contact the Mysql cluster anymore which is normal.

If the cluster is down for too long (1h for example), after the cluster is up and in good state again, most of my mysql-router are stuck in "blocked" state with the message "Failed to connect to MySQL".

After restarting those units (or using the juju run-action <mysql-router-unit> restart-mysqlrouter), everything is fine again.

I tried to give some time to mysql-router hoping there would be some maintenance process that would do that check automagically but it seems there is nothing like this and those units remains indefinitely in that state until you do something manually to fix that.