HDDS-13361. Attempt to delete non-empty tenant fails after revoke

[Gargi-jais11]

What changes were proposed in this pull request?

• ozone tenant delete fails with TENANT_NOT_EMPTY if user is assigned to the tenant, but OM deletes associated policies from Ranger first.
• Thus, after ozone tenant user revoke, the tenant is empty, but ozone tenant delete still fails, now due to 404 Not Found error from Ranger, when OM tries to delete policies.

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-13361

How was this patch tested?

Passed Existing Acceptance Test.

[adoroszlai]

Thanks @Gargi-jais11 for the patch. In HDDS-13354 I assumed ozone admin om updateranger would work in non-HA case by taking OM address from the config, but apparently it does not. To fix the test, please:

1. Move these two keywords from upgrade/lib.robot to a new file admincli/lib.resource.
   

   ozone/hadoop-ozone/dist/src/main/smoketest/upgrade/lib.robot

   Lines 22 to 34 in e0b804e

   	Get OM Service ID
   	${service_id} = Get Environment Variable OM_SERVICE_ID ${EMPTY}
   	RETURN ${service_id}
   	Get OM Service Param
   	${service_id} = Get OM Service ID
   	IF '${service_id}' == ''
   	RETURN --service-host om
   	ELSE
   	RETURN --service-id '${service_id}'
   	END

2. Make sure to add license header and *** Settings *** section with Library OperatingSystem, which is required for Get OM Service ID.
3. Import the new file by adding Resource ../admincli/lib.resource in both upgrade/lib.robot and security/ozone-secure-tenant.robot.
4. Make Trigger and wait call Get OM Service Param. Replace ${OM_HA_PARAM} with its return value.

[adoroszlai]

Thanks @Gargi-jais11 for updating the patch.

@smengcl please take a look

[smengcl]

Thanks @Gargi-jais11 for the patch.

[adoroszlai]

Thanks @Gargi-jais11 for the patch, @smengcl for the review.