[ 
https://issues.apache.org/jira/browse/AMBARI-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ximo Guanter updated AMBARI-1866:
---------------------------------

    Attachment: test.js
                ambari.js

Sure, here you go. To repro the issue you will need to "{{node test.js}}". You 
will need as a pre-requisite the Q library ({{npm install q}})

You might need to change the {{hostname}} (the name of the machine that has an 
ambari agent) and {{serverName}} (the name of the machine that has the ambari 
server)variables to match your settings.

The script works fine when run against the ambari version is HDP 1.2, but fails 
in Amabri's trunk.
                
> Configurations that are applied to a service aren't returned in 
> cluster.getDesiredConfigs()
> -------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-1866
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1866
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.3.1
>            Reporter: Ximo Guanter
>         Attachments: ambari.js, test.js
>
>
> h3.Repro
> Here's the symptom of this bug: if you create a cluster, add some 
> configurations to it (not as part of the desired_configs) and apply them 
> (i.e. add them to desired_configs) to a service, you will not be able to 
> install the service. You get the error message {{has_key(): expects the first 
> argument to be a hash, got \"\" which is of type String}} because the 
> $configuration variable is not being set in the generated site.pp
> These are basically the instructions in 
> https://cwiki.apache.org/confluence/display/AMBARI/Adding+a+New+Service+to+an+Existing+Cluster
> h3. Technical details
> It seems the problem happens in line 2076 in 
> AmbariManagementControllerImpl.java The call to 
> {{cluster.getDesiredConfigs()}} should be returning a {{DesiredConfig}} with 
> no tag, indicating that it is being overridden in the service, but this is 
> not happening. An empty set is returned, and even though the Service is 
> correctly configured, no configuration gets sent to the agent.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to