[ https://issues.apache.org/jira/browse/AMBARI-18765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Thorpe updated AMBARI-18765: -------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) > Services with invalid themes hang the UI when you attempt to add them > --------------------------------------------------------------------- > > Key: AMBARI-18765 > URL: https://issues.apache.org/jira/browse/AMBARI-18765 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: trunk, 2.4.0, 2.5.0 > Reporter: Tim Thorpe > Assignee: Tim Thorpe > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18765.patch > > > For a given service if the theme.json file is not properly formatted, Ambari > server will still start 'successfully' but attempts to add that service to > the cluster will fail. > The Ambari server start will log the theme error. Although it neglects to > mention which theme file and service are in error. > When you attempt to add the service, it will query for the service's themes: > api/v1/stacks/<stack>/versions/<version>/services?StackServices/service_name.in(HDFS,YARN,MAPREDUCE2,ZOOKEEPER,RANGER,RANGER_KMS,SLIDER)&themes/ThemeInfo/default=true&fields=themes/* > This will return something like the following for the invalid theme: > "ThemeInfo" : { > "default" : true, > "file_name" : "theme_version_2.json", > "service_name" : "RANGER_KMS", > "stack_name" : "BigInsights", > "stack_version" : "4.3", > "theme_data" : null > } > where the theme_data is null. -- This message was sent by Atlassian JIRA (v6.3.4#6332)