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

Scott Creeley updated AMBARI-5194:
----------------------------------

    Description: improve the HostInfo.py (Host Check) during the ambari 
installer process, particularly for step 3 of the process where the nodes are 
registered and confirmed.  In particular this JIRA will address the erroneous 
iptables check that currently always returns a value of 0 which indicates in 
the script that iptables is running and active, even when the iptables have 
actually been flushed.  This results in an erroneous warning message.  (was: 
improve the HostInfo.py (Host Check) during the ambari installer process, 
particularly for step 3 of the process where the nodes are registered and 
confirmed.  The check will find some user and directories that are normal for a 
RHS GlusterFS cluster, and we think they should be suppressed to help improve 
overall user experience.  Also, the iptables check always returns a 0, even 
when the iptables have been flushed, again this results in an erroneous warning 
message.)

> Improve User Experience during install
> --------------------------------------
>
>                 Key: AMBARI-5194
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5194
>             Project: Ambari
>          Issue Type: Improvement
>          Components: agent
>    Affects Versions: 1.4.4
>         Environment: Red Hat Storage Server - GlusterFS stack
>            Reporter: Scott Creeley
>              Labels: Ambari, HostCheck
>             Fix For: 1.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> improve the HostInfo.py (Host Check) during the ambari installer process, 
> particularly for step 3 of the process where the nodes are registered and 
> confirmed.  In particular this JIRA will address the erroneous iptables check 
> that currently always returns a value of 0 which indicates in the script that 
> iptables is running and active, even when the iptables have actually been 
> flushed.  This results in an erroneous warning message.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to