[jira] [Created] (AMBARI-24664) Non-kerberized environment alert
Raffaele Saggino created AMBARI-24664: - Summary: Non-kerberized environment alert Key: AMBARI-24664 URL: https://issues.apache.org/jira/browse/AMBARI-24664 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Environment: |ZooKeeper|3.4.6| |Kafka|1.1.1| |Ranger|1.0.0| |Kerberos|1.10.3-30| Reporter: Raffaele Saggino I am running Ambari-Server on a kerberized environment and since a few days, while enabling "ranger-kafka-plugin-enabled" I receive the following warning: Ranger Kafka plugin should not be enabled in non-kerberos environment. Ambari thinks that the environment is not kerberized, a side effect of this problem seems to be Ambari not creating the repository on ranger (after Kafka has been enabled). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22683) Custom username setting is not propagated
Raffaele Saggino created AMBARI-22683: - Summary: Custom username setting is not propagated Key: AMBARI-22683 URL: https://issues.apache.org/jira/browse/AMBARI-22683 Project: Ambari Issue Type: Bug Components: ambari-agent Affects Versions: 2.5.2, 2.6.0 Environment: HDF 3.0.2.0 Reporter: Raffaele Saggino Priority: Critical Hello, I am using Ambari to install registry on a HDF platform. I customized "registry" username to a different one in the "Misc." settings, this setting leads to a fail during the installation process. My current workaround is to manually edit the file "/etc/registry/conf/registry-env.sh" and add: export REGISTRY_USER= new_registry_name P.S. This happens also while installing the streamline component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
