Yesha Vora created AMBARI-20325:
-----------------------------------
Summary: Ambari should be able to detect misconfiguration of
Http/Https related configs
Key: AMBARI-20325
URL: https://issues.apache.org/jira/browse/AMBARI-20325
Project: Ambari
Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Yesha Vora
Priority: Critical
When user tries to misconfigure any component, ambari should validate and give
necessary error messages.
* When user enable/disable https for a service, ambari should recommend and
validate configs
* subsequently if user tries to misconfigure any port then appropriate
validation should be done
Example:
When Yarn http/https properties are misconfigured, it can break Quick links.
Ambari was not able to detect this misconfiguration. Ambari should add proper
validation for such scenario.
Steps to reproduce: ( HA cluster)
* Set yarn.resourcemanager.webapp.https.address to 8090. Set
yarn.resourcemanager.webapp.https.address.rm1 and
yarn.resourcemanager.webapp.https.address.rm2 to have port = 8088.
This is wrong configuration.
{code}
<property>
<name>yarn.resourcemanager.webapp.https.address</name>
<value>xxx1:8090</value>
</property>
<property>
<name>yarn.resourcemanager.webapp.https.address.rm1</name>
<value>xxx1:8088</value>
</property>
<property>
<name>yarn.resourcemanager.webapp.https.address.rm2</name>
<value>xxx2:8088</value>
</property>{code}
Expected behavior:
When user tries to modify Https related config incorrectly, ambari should be
able to detect that and throw an warning/error message stating the correct
reason such as "port mentioned in yarn.resourcemanager.webapp.https.address is
not same as yarn.resourcemanager.webapp.https.address.rm1/rm2."
Actual behavior:
Ambari perform no validation for such misconfiguration and allows user to
misconfigure the cluster without any warning.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
