[ 
https://issues.apache.org/jira/browse/HDDS-13249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18003524#comment-18003524
 ] 

Sreeja edited comment on HDDS-13249 at 7/9/25 4:55 AM:
-------------------------------------------------------

After further review, looks like the cluster where you tested the command did 
not include the changes from HDDS-12055 which is why I initially assumed the 
command in the description might be incorrect.
Therefore, this will require further analysis.


was (Author: JIRAUSER308351):
After further review, looks like the cluster where you tested the command did 
not include the changes from HDDS-12055 which is why I initially assumed the 
command in the description might be incorrect.

However, I have now verified that even with the changes from HDDS-12055, the 
command still fails with the same issue.
Therefore, this will require further analysis.

> Issue with debug container command with the default VERSION path
> ----------------------------------------------------------------
>
>                 Key: HDDS-13249
>                 URL: https://issues.apache.org/jira/browse/HDDS-13249
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: Ozone CLI
>    Affects Versions: 2.0.0
>            Reporter: Soumitra Sulav
>            Assignee: Sreeja
>            Priority: Major
>
> The debug container command fails by pointing to the default invalid version 
> path
> {code:java}
> # ozone debug container info --container=4111
> /tmp/hadoop-root/dfs/data/hdds/VERSION (No such file or directory)
> # ozone debug container inspect
> /tmp/hadoop-root/dfs/data/hdds/VERSION (No such file or directory)
> # ls /hadoop-ozone/datanode/data/hdds/VERSION
> /hadoop-ozone/datanode/data/hdds/VERSION
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to