You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2020/06/02 16:45:00 UTC
[jira] [Updated] (HDDS-537) ozone sh vol complains for valid length
even when the length is valid for 3 characters
[ https://issues.apache.org/jira/browse/HDDS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Agarwal updated HDDS-537:
-------------------------------
Target Version/s: 0.6.0
Labels: Triaged (was: )
Let's check if this is still an issue, if so we should fix it for 0.6.0.
> ozone sh vol complains for valid length even when the length is valid for 3 characters
> --------------------------------------------------------------------------------------
>
> Key: HDDS-537
> URL: https://issues.apache.org/jira/browse/HDDS-537
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Namit Maheshwari
> Assignee: Namit Maheshwari
> Priority: Major
> Labels: Triaged
>
> {code:java}
> [root@ctr-e138-1518143905142-481027-01-000002 bin]# ./ozone sh vol info abc
> Bucket or Volume length is illegal, valid length is 3-63 characters
> {code}
> Here, the length is already 3 characters still it throws errors, that valid length is 3-63 characters
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org