[
https://issues.apache.org/jira/browse/RANGER-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fateh Singh resolved RANGER-4657.
---------------------------------
Resolution: Fixed
Issue has been fixed:
[https://github.com/apache/ranger/pull/297/commits/0a17fa59546121eabb457b5c2b603d17cb36439d]
[https://github.com/apache/ranger/pull/297/commits]
> Ozone resource lookup is not working due to "Service ID specified does not
> match with ozone.om.service.ids defined in the configuration."
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: RANGER-4657
> URL: https://issues.apache.org/jira/browse/RANGER-4657
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Reporter: Fateh Singh
> Assignee: Fateh Singh
> Priority: Major
>
> Ozone service id in ranger is [hard-coded to be
> "ozone1"|https://github.infra.cloudera.com/CDH/ranger/blob/b90853027212628f3fd63c73aa8b017456a8cf8e/plugin-ozone/src/main/java/org/apache/ranger/services/ozone/client/OzoneClient.java#L57].
> Because of that, if a different value is used for ozone.service.id in Ozone
> configs, resource lookup won't work in Ranger.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
