You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@knox.apache.org by "Kevin Minder (JIRA)" <ji...@apache.org> on 2015/04/20 20:15:59 UTC

[jira] [Updated] (KNOX-166) Improve diagnosability of connectivity issues

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

Kevin Minder updated KNOX-166:
------------------------------
    Fix Version/s:     (was: 0.6.0)
                   0.7.0

> Improve diagnosability of connectivity issues
> ---------------------------------------------
>
>                 Key: KNOX-166
>                 URL: https://issues.apache.org/jira/browse/KNOX-166
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 0.3.0
>            Reporter: Kevin Minder
>             Fix For: 0.7.0
>
>
> When connection issues occur due to either network problems is misconfiguration it is very difficult for the user to determine the root cause and resolve the issue.  We need to do some negative testing here to ensure that log based diagnosability is good.  Here are a few use cases to start with.
> 1) Cluster is secure but Knox not configured.
> 2) LDAP config is invalid
> 3) Clusters internal hostnames don't match external hostnames
> 4) Information in topology file is missing or incorrect



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)