Tom Beerbower created AMBARI-7496:
-------------------------------------

             Summary: Views: when we have an error deploying a view, the log 
should also indicate the version
                 Key: AMBARI-7496
                 URL: https://issues.apache.org/jira/browse/AMBARI-7496
             Project: Ambari
          Issue Type: Task
            Reporter: Tom Beerbower
            Assignee: Tom Beerbower
             Fix For: 1.7.0


I have 3 versions of a view. I deployed version 4 that has an error deploying. 
The UI correctly shows me the deploy failed and to check the log.

I check the log and can see there was an error deploying the view. But it 
doesn't specify which version, which would be good to know instance there are 
failures of the same view, diff versions.

{code}
12:26:13,491 ERROR [pool-1-thread-1] ViewRegistry:1244 - Caught exception 
loading view CAPACITY-SCHEDULER
java.lang.IllegalStateException: No property values exist for the required 
parameters [ambari.server.password, something.new, ambari.server.username, 
ambari.server.url]
        at 
org.apache.ambari.server.orm.entities.ViewInstanceEntity.validate(ViewInstanceEntity.java:753)
        at 
org.apache.ambari.server.view.ViewRegistry.createViewInstanceDefinition(ViewRegistry.java:858)
        at 
org.apache.ambari.server.view.ViewRegistry.readViewArchive(ViewRegistry.java:1224)
        at 
org.apache.ambari.server.view.ViewRegistry.access$000(ViewRegistry.java:97)
        at 
org.apache.ambari.server.view.ViewRegistry$4.run(ViewRegistry.java:1176)
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:744)
12:26:15,912  INFO [qtp1899753024-68] HeartBeatHandler:458 - State of service 
compone
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to