anyone had any experience with objects that show as read-only which will not be deleted? I am trying to delete buckets and the tenant but inside the buckets are 2 read-only objects. when i run query from rest it tells me that the bucket has zero usage zero objects but when we look through an S3 browser, they are there and showing read only. simply cannot get rid of them.
#cannot delete objects
1 messages · Page 1 of 1 (latest)
does the bucket have object lock enabled?
no
Within an S3 browser, if you left or right click on the file and look at the properties are you sure object lock is not enabled ?
cannot see any object lock at the object level
did you try deleting the object as the S3 root user?
as in the grid root user or tenant root user?
we are now getting messages that the parent bucket is readonly when trying to delete or modify permissions on the object
hm that is strange
Had a similar issue; could not completely get rid of a single file. If deleted if left a delete marker which we could not get rid off.
After a few months of NetApp support trying various things they finally sent me a python script which did the trick.
Could be there were still versions of the object(s) available. Check with a client like S3browser. Remove the versions from there. Or use the "aws s3 rb" command from the AWSCLI
yes we are at that stage now, 3 or 4 python attempts, looks like the meta is still there but the data behind is not.
i did try that but everytime i attempted to remove, another version appeared.
Are you using versioning ?
No, this has been identified by netapp as a grid OS bug.