Comment 4 for bug 1832566

The fix seems to be not complete because now when we run 'tempest cleanup --init-saved-state' and we have for example the subnet pool disabled, like the bug description mentioned, it will return a non-zero return code.
it should return zero return code, because the resources were discovered correctly.

From automation perspective if the subnetpools are disabled in tempest.conf, which is a valid case, the script will generate proper saved_state.json file but will exit with code which is interpreted as an errror.