You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Maciej Bryński (JIRA)" <ji...@apache.org> on 2018/07/26 11:59:00 UTC

[jira] [Updated] (AMBARI-24360) Blueprint doesn't replace hostnames in ranger-audit configurations

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

Maciej Bryński updated AMBARI-24360:
------------------------------------
    Description: 
Those variables have hostnames inside and blueprint export and importer can't handle HOSTGROUPS properly.
{code}
          "ranger.audit.solr.urls"
          "ranger.audit.solr.zookeepers"
          "xasecure.audit.destination.solr.zookeepers"
          "xasecure.audit.destination.solr.urls"
          "ranger.plugin.yarn.policy.rest.url"
          "ranger.plugin.hdfs.policy.rest.url"
          "ranger.plugin.hive.policy.rest.url"
{code}
Some of them can be in more than one config file.

Thread started here:
https://community.hortonworks.com/questions/208011/hardcoded-hostnames-in-ambari-blueprints.html

  was:
Those variables have hostnames inside and blueprint export and importer can't handle HOSTGROUPS properly.
{code}
          "ranger.audit.solr.urls"
          "ranger.audit.solr.zookeepers"
          "xasecure.audit.destination.solr.zookeepers"
          "xasecure.audit.destination.solr.urls"
          "ranger.plugin.yarn.policy.rest.url"
          "ranger.plugin.hdfs.policy.rest.url"
          "ranger.plugin.hive.policy.rest.url"
{code}
Some of them can be in more than one config file.


> Blueprint doesn't replace hostnames in ranger-audit configurations
> ------------------------------------------------------------------
>
>                 Key: AMBARI-24360
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24360
>             Project: Ambari
>          Issue Type: Bug
>          Components: blueprints
>    Affects Versions: 2.6.0
>            Reporter: Maciej Bryński
>            Priority: Major
>
> Those variables have hostnames inside and blueprint export and importer can't handle HOSTGROUPS properly.
> {code}
>           "ranger.audit.solr.urls"
>           "ranger.audit.solr.zookeepers"
>           "xasecure.audit.destination.solr.zookeepers"
>           "xasecure.audit.destination.solr.urls"
>           "ranger.plugin.yarn.policy.rest.url"
>           "ranger.plugin.hdfs.policy.rest.url"
>           "ranger.plugin.hive.policy.rest.url"
> {code}
> Some of them can be in more than one config file.
> Thread started here:
> https://community.hortonworks.com/questions/208011/hardcoded-hostnames-in-ambari-blueprints.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)