You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Hari Sekhon (JIRA)" <ji...@apache.org> on 2015/01/15 17:07:35 UTC

[jira] [Updated] (AMBARI-9150) Fix deploying configurations out of correct stack instead of HDP 2.0.6

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

Hari Sekhon updated AMBARI-9150:
--------------------------------
    Component/s: ambari-server

> Fix deploying configurations out of correct stack instead of HDP 2.0.6
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-9150
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9150
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-agent, ambari-server, stacks
>    Affects Versions: 1.7.0
>         Environment: HDP 2.2
>            Reporter: Hari Sekhon
>            Priority: Minor
>
> Ambari's jinja2 configuration templates for HDP 2.1 were still being deployed out of the HDP 2.0.6 stack with Ambari 1.6 in 2014 and now I'm hacking config that isn't exposed via Ambari web UI I see that's still the case on my HDP 2.2 cluster with Ambari 1.7.
> This is unintuitive - can it be cleaned up so that configuration templates are deployed out of the stack that matches the deployed cluster version - seems like just a case of housekeeping?
> Regards,
> Hari Sekhon
> http://www.linkedin.com/in/harisekhon



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