-
Notifications
You must be signed in to change notification settings - Fork 340
Cannot create new bucket outside of OVA #1620
Comments
For the convenience of the Seagate development team, this issue has been mirrored in a private Seagate Jira Server: https://jts.seagate.com/browse/CORTX-33841. Note that community members will not be able to access that Jira server but that is not a problem since all activity in that Jira mirror will be copied into this GitHub issue. |
I can list buckets or upload data to bucket without any issues but creating a new bucket causes an issue with location constraint |
@rshenoy0831, did you come across this scenario in your test case? |
we have not came across this behaviour in our testing. |
This issue/pull request has been marked as |
@rshenoy0831 do you have any idea why this might happen for users? |
@rshenoy0831, can you check the test validation report if this test case was covered? |
@mukul-seagate11 Yes, we have a coverage. |
@hessio, as per QA, it was covered in test plan & test execution |
I am going through this testing guide to see but I am finding it difficult to identify what command you are running to create the bucket. It seems to be that when you create a bucket using the command: |
@hessio - we have validated following github page. |
can we check whether the issue is reproducible if we specify location as default during aws configuration |
Yes it is - when you try location as 'None', 'eu-west-1' or 'us-west-1' issue still occurs |
Ok thanks for letting me know. The problem with this issue that it seems to mostly only occur after using the OVA for a few days. Sometimes when you setup the OVA it doesn't occur and other times it does. |
ova issues which are reported by community https://github.com/Seagate/cortx/issues?q=is%3Aopen+is%3Aissue+label%3Aova will be further raised to QA and QA will try to verify these issues in next sprint. |
Haven't observed this issue as per #1644 |
As you can see this issue still appears with new OVA:
|
@mukul-seagate11 this issue is only faced if you try to create a new bucket from a remote machine. When you try to create a bucket on the OVA terminal there is no issue. So in this #1644 you have not tested for this scenario. And as you can see from above comment that when I tested this issue it failed the test. |
@hessio, this is not in the requirement so only 1 S3 instance is defined |
Yes I only have 1 s3 instance. The remote machine is just the host machine that I have my VMWare client installed on |
@hessio, Ok but with remote machine, the IO functionality hasn't tested yet |
Ok ya that's fine, would we be able to add his functionality to the testing? |
Not yet as its not in the roadmap yet |
Ok when is the roadmap being updated? I think this is an important feature for using the OVA |
Problem
When I try to make a new bucket on the OVA outside of the OVA I get an error with the location-constraint. This error does not occur when creating the bucket from inside the OVA.
Expected behavior
Should be able to create new bucket from a remote machine using the AWS cli (or any s3 client).
How to reproduce
Setup OVA PI-7 and try to create a new bucket from a remote machine. To do this I used VMWare Workstation to run the OVA file and then on my machine in a terminal I tried to create a new bucket using AWS cli.
Deployment information
VMware Workstation 16 Pro running on a Windows 10 machine.
OVA PI-7
Additional information
This also happened to some users during our most recent hackathon as you can see here:
The text was updated successfully, but these errors were encountered: