You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Alok Lal (JIRA)" <ji...@apache.org> on 2014/11/01 06:48:33 UTC

[jira] [Created] (ARGUS-149) If the HDFS file system is empty then repository configurator gives confusing message

Alok Lal created ARGUS-149:
------------------------------

             Summary: If the HDFS file system is empty then repository configurator gives confusing message
                 Key: ARGUS-149
                 URL: https://issues.apache.org/jira/browse/ARGUS-149
             Project: Argus
          Issue Type: Bug
    Affects Versions: 0.4.0
            Reporter: Alok Lal
             Fix For: 0.4.0


test of correct hdfs repo relies on non-null file listing.  If one tries to configure an empty repository then one gets the following message:

{code}
Connection Failed.
Unable to retrieve any files using given parameters, You can still save the repository and start creating policies, but you would not be able to use autocomplete for resource names. Check xa_portal.log for more info.

Unable to retrieve any files using given parameters, You can still save the repository and start creating policies, but you would not be able to use autocomplete for resource names. Check xa_portal.log for more info.
{code}

The message is factually correct.  It would be helpful if it said something to the effect: unable to retrieve any files.  Either the file system is currently empty or connection wasn't successful.

While it asks one to look at xa_portal.log in this case the log does not have any helpful information because connection in fact was successful.

h4. Steps to reproduce
- format the namenode: {{bin/hdfs namenode -format}}
- confirm that fs is empty {{bin/hdfs dfs -ls -R /}}
- go to admin portal and test the connection.  You will get the above error.  Check in the xa_portal.log to confirm that there wasn't any connection error or exceptions.
- Now go an create a single file {{bin/hdfs dfs -touchz /test}}
- go back to admin portal and test the connection.  Test would succeed this time.



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