Ranger plugin communication fails after upgrade to Ambari-2.5.x version if Ambari-2.5.x upgrade fails

[#1]

Scenario - Cluster managed by Ambari with Ranger Plugins enabled and if Ambari upgrade process fails, below are the things to consider.

1) Updating stack_features property in cluster-env config type
Get the current cluster-env version using configs.sh utility.

/var/lib/ambari-server/resources/scripts/configs.sh get <AMBARI_HOST> <CLUSTER_NAME> cluster-env cluster_env.json

Open cluster_env.json and check for "ranger_xml_configuration" feature in stack_features property. If it is not present add below content and save the cluster_env.json.

{\n        \"name\": \"ranger_xml_configuration\",\n        \"description\": \"Ranger code b
ase support xml configurations\",\n        \"min_version\": \"2.3.0.0\"\n      }

Now update the latest cluster-env,

/var/lib/ambari-server/resources/scripts/configs.sh set <AMBARI_HOST> <CLUSTER_NAME> cluster-env cluster_env.json

2) Updating Ranger url in plugin properties.
Update "ranger.plugin.<SERVICE>.policy.rest.url" property value under Advanced ranger.<SERVICE>.security section with Ranger Url. ie (http:RANGER_ADMIN_HOST:RANGER_ADMIN_PORT).