Bug 1625951 - [GSS] Recursive move from a directory with double underscore fails
Summary: [GSS] Recursive move from a directory with double underscore fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 2.5
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 4.1
Assignee: Matt Benjamin (redhat)
QA Contact: Tejas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-06 09:30 UTC by Karun Josy
Modified: 2023-09-14 04:34 UTC (History)
15 users (show)

Fixed In Version: ceph-14.2.8-3.el8, ceph-14.2.8-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-19 17:30:39 UTC
Embargoed:
hyelloji: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:2231 0 None None None 2020-05-19 17:30:58 UTC

Comment 7 Karun Josy 2018-11-30 07:44:13 UTC
Hi Matt,

Were you able to reproduce this bug? Or do you need more details?

Regards,
Karun

Comment 9 Karun Josy 2018-12-03 06:53:58 UTC
Hi Matt, 

I am able to reproduce this even on 2.5.z3
-------

# ceph -v
ceph version 10.2.10-43.el7cp (a3727e7c4651dd9db224a2e8480dd8262d412a18)

To reproduce :

Create a local directory named DIR and a few files in it
#mkdir DIR ; for i in {1..10} ; do dd if=/dev/zero bs=4k count=1 of=./DIR/$i.txt 2>/dev/null ; done

#aws s3 mb s3://test-underscore-bug --endpoint-url $endpoint_url --no-verify-ssl

#aws s3 sync DIR s3://test-underscore-bug/DIR/ --endpoint-url $endpoint_url --no-verify-ssl

#aws s3 --recursive mv s3://test-underscore-bug/DIR s3://test-underscore-bug/__DIR --endpoint-url $endpoint_url --no-verify-ssl


# aws s3 --recursive mv s3://test-underscore-bug/__DIR s3://test-underscore-bug/DIR --endpoint-url $endpoint_url --no-verify-ssl
move failed: s3://test-underscore-bug/__DIR/1.txt to s3://test-underscore-bug/DIR/1.txt An error occurred (NoSuchKey) when calling the CopyObject operation: Unknown
move failed: s3://test-underscore-bug/__DIR/10.txt to s3://test-underscore-bug/DIR/10.txt An error occurred (NoSuchKey) when calling the CopyObject operation: Unknown
move failed: s3://test-underscore-bug/__DIR/3.txt to s3://test-underscore-bug/DIR/3.txt An error occurred (NoSuchKey) when calling the CopyObject operation: Unknown
move failed: s3://test-underscore-bug/__DIR/test to s3://test-underscore-bug/DIR/test An error occurred (NoSuchKey) when calling the CopyObject operation: Unknown
move failed: s3://test-underscore-bug/__DIR/7.txt to s3://test-underscore-bug/DIR/7.txt An error occurred (NoSuchKey) when calling the CopyObject operation: Unknown
move failed: s3://test-underscore-bug/__DIR/8.txt to s3://test-underscore-bug/DIR/8.txt An error occurred (NoSuchKey) when calling the CopyObject operation: Unknown
move failed: s3://test-underscore-bug/__DIR/2.txt to s3://test-underscore-bug/DIR/2.txt An error occurred (NoSuchKey) when calling the CopyObject operation: Unknown
move failed: s3://test-underscore-bug/__DIR/4.txt to s3://test-underscore-bug/DIR/4.txt An error occurred (NoSuchKey) when calling the CopyObject operation: Unknown
move failed: s3://test-underscore-bug/__DIR/9.txt to s3://test-underscore-bug/DIR/9.txt An error occurred (NoSuchKey) when calling the CopyObject operation: Unknown
move failed: s3://test-underscore-bug/__DIR/5.txt to s3://test-underscore-bug/DIR/5.txt An error occurred (NoSuchKey) when calling the CopyObject operation: Unknown
move failed: s3://test-underscore-bug/__DIR/6.txt to s3://test-underscore-bug/DIR/6.txt An error occurred (NoSuchKey) when calling the CopyObject operation: Unknown

Let me know if you need more details

Comment 18 Giridhar Ramaraju 2019-08-05 13:08:18 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 19 Giridhar Ramaraju 2019-08-05 13:09:48 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 29 errata-xmlrpc 2020-05-19 17:30:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:2231

Comment 30 Red Hat Bugzilla 2023-09-14 04:34:20 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.