[
https://issues.apache.org/jira/browse/AMBARI-17264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15333543#comment-15333543
]
Andrii Babiichuk commented on AMBARI-17264:
-------------------------------------------
+1 for the patch
> Ranger Tagsync shows under Summary Tab after upgrade from 2.4 to 2.5
> --------------------------------------------------------------------
>
> Key: AMBARI-17264
> URL: https://issues.apache.org/jira/browse/AMBARI-17264
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17264.patch
>
>
> Ranger Tagsync is introduced in stack 2.5 onwards as a SLAVE component.
> After stack upgrade from 2.4 to 2.5 Summary Tab shows:
> {noformat}Ranger Tagsyncs / Started{noformat}
> /api/v1/clusters/upcheck/components/RANGER_TAGSYNC
> {noformat}
> {
> "status" : 404,
> "message" : "The requested resource doesn't exist: ServiceComponent not
> found, clusterName=upcheck, serviceName=RANGER,
> serviceComponentName=RANGER_TAGSYNC"
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
