Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Renaming a Pesudo-Directory in Cloud Files Deletes Contents #7299

Closed
cyberduck opened this issue Jun 16, 2013 · 1 comment
Closed

Renaming a Pesudo-Directory in Cloud Files Deletes Contents #7299

cyberduck opened this issue Jun 16, 2013 · 1 comment
Assignees
@dkocher
Labels
bug cloudfiles Rackspace CloudFiles high priority worksforme
Milestone
4.4

Comments

@cyberduck
Copy link
Collaborator

1d82ba3 created the issue

Hello,

We've found under a few situations that trying to rename a pseudo-folder will result in deleting the folder object and all of the objects listed as children thereof.

To reproduce:

  • Create new container
  • Create pseudo-directory in this container
  • Create an object within this pesudo-directory
  • Rename the pseudo-directory

Expected result:

  • 1 - The object you're attempting to rename is removed from Cloud Files
  • 2- All subobjects of the pseudo-directory are removed from Cloud Files.

In every attempt I've come across, case 1 happens. In most attempts, Case 2 happens as well.

I intend to provide exact Cloud Files api logs to help track down the issue once they're available. (API logs and CDN logs are generally produced with a few hours' delay due to sheer volume). I'm also looking to get version information for users experiencing this issue.

So far, I can state that this has occurred on 4.3.1 for Windows (Server 2008)
@cyberduck
Copy link
Collaborator Author

@dkocher commented

You can provide the transcript from the log drawer View → Toggle Log Drawer. It is expected that when you rename a placeholder object, all subobjects are renamed to the new key name format as well. This is implemented by copying over the object and then deleting the object.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug cloudfiles Rackspace CloudFiles high priority worksforme
Projects
None yet
Milestone
4.4
Development

No branches or pull requests
2 participants
@dkocher @cyberduck