we are hitting the same issue in a standard controller configuration (2+2).
Also, it's not possible to lock controller-0, after system host-lock controller-0 the always shows:
[wrsroot@controller-1 ~(keystone_admin)]$ system host-show controller-0 | grep administrative | administrative | unlocked |
we are hitting the same issue in a standard controller configuration (2+2).
Also, it's not possible to lock controller-0, after system host-lock controller-0 the always shows:
[wrsroot@ controller- 1 ~(keystone_admin)]$ system host-show controller-0 | grep administrative
| administrative | unlocked |