Hi, According to the JIRA https://issues.apache.org/jira/browse/AMBARI-8174 that fix was included with Ambari 1.7.0 release.
If you confirm you are running Ambari 1.7.0 (either “ambari-server –version” or “yum info ambari-server”), then that means you are running the ambari version that includes the fix in it. Are you find that not to the the case?