@Alex When you say a "non existing tenant ID" do you mean a tenant that used to exist and has been deleted, or a tenant that never existed at all? It looks to me like that ID could belong to a deleted tenant that owns a shared network, in which case the command is working as intended. Can you confirm whether there is a shared network associated with that tenant ID? This command should never return "There is not tenant with 'SPECIFIED ID' id found" or similar, as it's intended for cleaning up orphaned resources of tenants that no longer exist.
@Assaf No, it doesn't look like anything has merged which would affect this. I suspect that this bug is invalid.
@Alex When you say a "non existing tenant ID" do you mean a tenant that used to exist and has been deleted, or a tenant that never existed at all? It looks to me like that ID could belong to a deleted tenant that owns a shared network, in which case the command is working as intended. Can you confirm whether there is a shared network associated with that tenant ID? This command should never return "There is not tenant with 'SPECIFIED ID' id found" or similar, as it's intended for cleaning up orphaned resources of tenants that no longer exist.
@Assaf No, it doesn't look like anything has merged which would affect this. I suspect that this bug is invalid.