Description of problem: While performing 'get-object-attributes', it fails with 'Unable to parse response (syntax error: line 1, column 0), invalid XML received. ' [root@rgw-host ~]# aws --endpoint http://ceph-pri-mp-y2rdao-node6:5000 s3api get-object-attributes --bucket hello01 --key test_cloud_cfg --object-attributes Unable to parse response (syntax error: line 1, column 0), invalid XML received. Further retries may succeed: b'[default]\naccess_key = M977OZb.u0THSI19bcM7\naccess_token = \nadd_encoding_exts = \nadd_headers = \nbucket_location = US\nca_certs_file = \ncache_file = \ncheck_ssl_certificate = True\ncheck_ssl_hostname = True\ncloudfront_host = cloudfront.amazonaws.com\nconnection_pooling = True\ncontent_disposition = \ncontent_type = \ndefault_mime_type = binary/octet-stream\ndelay_updates = False\ndelete_after = False\ndelete_after_fetch = False\ndelete_removed = False\ndry_run = False\nenable_multipart = True\nencoding = UTF-8\nencrypt = False\nexpiry_date = \nexpiry_days = \nexpiry_prefix = \nfollow_symlinks = False\nforce = False\nget_continue = False\ngpg_command = /usr/bin/gpg\ngpg_decrypt = %(gpg_command)s -d --verbose --no-use-agent --batch --yes --passphrase-fd %(passphrase_fd)s -o %(output_file)s %(input_file)s\ngpg_encrypt = %(gpg_command)s -c --verbose --no-use-agent --batch --yes --passphrase-fd %(passphrase_fd)s -o %(output_file)s %(input_file)s\ngpg_passphrase = \nguess_mime_type = True\nhost_base = 10.0.210.105:5000\nhost_bucket = 10.0.210.105:5000\nhuman_readable_sizes = False\ninvalidate_default_index_on_cf = False\ninvalidate_default_index_root_on_cf = True\ninvalidate_on_cf = False\nkms_key = \nlimit = -1\nlimitrate = 0\nlist_md5 = False\nlog_target_prefix = \nlong_listing = False\nmax_delete = -1\nmime_type = \nmultipart_chunk_size_mb = 15\nmultipart_max_chunks = 10000\npreserve_attrs = True\nprogress_meter = True\nproxy_host = \nproxy_port = 0\npublic_url_use_https = False\nput_continue = False\nrecursive = False\nrecv_chunk = 65536\nreduced_redundancy = False\nrequester_pays = False\nrestore_days = 1\nrestore_priority = Standard\nsecret_key = bFuWM8RXQW7EPKM2CeIEUrPZ3N.ceW7CVeYc7HPN\nsend_chunk = 65536\nserver_side_encryption = False\nsignature_v2 = True\nsignurl_use_https = False\nsimpledb_host = sdb.amazonaws.com\nskip_existing = False\nsocket_timeout = 300\nstats = False\nstop_on_error = False\nstorage_class = \nurlencoding_mode = normal\nuse_http_expect = False\nuse_https = False\nuse_mime_magic = True\nverbosity = WARNING\nwebsite_endpoint = http://%(bucket)s.10.0.210.105-%(location)s\nwebsite_error = \nwebsite_index = index.html\n\n' Version-Release number of selected component (if applicable): ceph version 18.2.1-38.el9cp (c709c61e19be87249f04b05dec1e586c1f9dd7b0) reef How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
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 (Red Hat Ceph Storage 8.0 security, bug fix, and enhancement updates), 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/RHBA-2024:10216
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days