Open webteam-app opened 1 year ago
2&3 are mutually exclusive by design and MAAS doesn't not allow to release a node if both 2&3 are enabled
I have a second thought on this. API operations actually allows both to be set. And the API client's help explains the behavior at least from a documentation point of view.
$ maas admin machine release -h ...
If both
secure_erase
andquick_erase
are specified and the drive does NOT have a secure erase feature, MAAS will behave as if onlyquick_erase
was specified.
So the mutually-exclusive behavior itself can be the bug in the UI.
Bug originally filed by nobuto at https://bugs.launchpad.net/bugs/2009669
maas: 1:3.3.0-13159-g.1c22f7beb-0ubuntu1~22.04.1 maas-ui: 3.3.0 acde9f13b45dd515b3d9638545bf82d282d7d5a2
In WebUI as MAAS/r/settings/storage, there is disk erase related configurations.
Those 3 are presented equally at the same UI level in the WebUI. However,
2&3 do not take effect unless 1 is True, so it would be nice if
2&3 are mutually exclusive by design and MAAS doesn't not allow to release a node if both 2&3 are enabled so it would be nice if