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

Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2020/03/04 17:34:20 UTC

[GitHub] [hadoop-ozone] adoroszlai commented on issue #553: HDDS-3021. Ozone S3 CLI path command not working on HA cluster.

adoroszlai commented on issue #553: HDDS-3021. Ozone S3 CLI path command not working on HA cluster.
URL: https://github.com/apache/hadoop-ozone/pull/553#issuecomment-594687891
 
 
   Thanks @bharatviswa504 for the explanation.
   
   > So, in HA for all commands, we have mandated to pass the serviceID, instead of best effort.
   
   But this also means the same command does not work in both non-HA and HA case.
   
   My current concern is that smoke tests need to be aware of the environment they are run in.  Eg. I wanted to add a test to verify behavior of `ozone s3 getsecret` command, but it needs to distinguish between `ozone` and `ozone-om-ha-s3` environments (as well as `ozonesecure`, but we already have an env. variable for that).

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org