Bug 2413062

Description of problem:



As part of the dedup feature testing on versioned buckets, we found that if we delete the latest version of the object of the bucket,  and do a dedup estimate, 
The dedup stats show corrupted ETAG, which may be due to the versioned buckets having 0-sized objects. 


Version-Release number of selected component (if applicable):

latest 9.0 

How reproducible:

always

Steps to Reproduce:
1. create a rgw user 

radosgw-admin user create --uid user1 --access-key 123 --secret 123 --display-name user1

2. set aws profile 

# pip install awscli
# aws --profile user1  configure set endpoint_url http://ceph-pri-vim-ms-90-t9my2o-node5:80
#  aws --profile user1  configure

3. create a bucket via awscli

# aws --profile user1  s3 mb s3://version1
# aws  --profile user1  s3api put-bucket-versioning --bucket version1 --versioning-configuration Status=Enabled

4. write 1M object 

#truncate -s 1M object-1M
# aws  --profile user1  s3 cp object-1M s3://version1/object-version-1m
# aws  --profile user1  s3 cp object-1M s3://version1/object-version-1m

5. list the object version via awscli
# aws  --profile user1  s3api list-object-versions --bucket version1 --key object-version-1m
# rados ls -p primary.rgw.buckets.data

6. Delete the object (latest version) using lifecycle 

- set the ceph config rgw_lc_debug_interval 30 in the ceph.conf file or through the ceph config set as below 
 # ceph config set client.rgw_service_name rgw_lc_debug_interval 30
# restart the rgws ( via systemctl restart)

# aws --profile user1 s3api put-bucket-lifecycle-configuration  --bucket version1 --lifecycle-configuration file://lifecycle.json
# cat lifecycle.json
{
  "Rules": [
    {
      "ID": "DeleteObjectsAfter1Day",
      "Status": "Enabled",
      "Filter": {
        "Prefix": ""
      },
      "Expiration": {
        "Days": 1
      }
    }
  ]
}


7. Do the dedup estimate and dedup stats


Actual results:

the dedup stats shows corrupted ETAG which can be misleading

Expected results:

the dedup stats should not show corrupted ETAG

Additional info: