Persistent Bucket Notification Reconfiguring with CreateTopic
Hi folks, Currently running a test Ceph cluster on 19.1.0 and seeing some odd behaviour using the CreateTopic API. Initially I call the CreateTopic API, and all looks well: $ rga topic list { "topics": [ { "topics": [ { "owner": "ahk2", "name": "ahk2", "dest": { "push_endpoint": "http://1.2.3.6:4321", "push_endpoint_args": "", "push_endpoint_topic": "ahk2", "stored_secret": false, "persistent": true, "persistent_queue": ":ahk2", "time_to_live": "None", "max_retries": "None", "retry_sleep_duration": "None" }, "arn": "arn:aws:sns:geored_zg::ahk2", "opaqueData": "", "policy": "" } ] } ] } I call it again, in an identical manner: $ rga topic list { "topics": [ { "topics": [ { "owner": "ahk2", "name": "ahk2", "dest": { "push_endpoint": "http://1.2.3.6:4321", "push_endpoint_args": "", "push_endpoint_topic": "ahk2", "stored_secret": false, "persistent": true, "persistent_queue": "", "time_to_live": "None", "max_retries": "None", "retry_sleep_duration": "None" }, "arn": "arn:aws:sns:geored_zg::ahk2", "opaqueData": "", "policy": "" } ] } ] } Notice that the "persistent_queue" field is gone. I now hit errors trying to use my topic, for example: $ rga topic stats --topic ahk2 This topic does not have a persistent queue. Suspect this might be a bug in the RC. Happy to open a tracker if so. Unless I'm doing something stupid...? Best Wishes, Alex
I raised Bug #67765: Updating a Topic via the CreateTopic API Corrupts the Topic - rgw - Ceph<https://tracker.ceph.com/issues/67765> for this issue. Kind regards, Alex ________________________________ From: Alex Hussein-Kershaw (HE/HIM) Sent: Tuesday, August 27, 2024 6:01 PM To: ceph-users <ceph-users@ceph.io> Cc: Connor Coull <t-ccoull@microsoft.com> Subject: Persistent Bucket Notification Reconfiguring with CreateTopic Hi folks, Currently running a test Ceph cluster on 19.1.0 and seeing some odd behaviour using the CreateTopic API. Initially I call the CreateTopic API, and all looks well: $ rga topic list { "topics": [ { "topics": [ { "owner": "ahk2", "name": "ahk2", "dest": { "push_endpoint": "http://1.2.3.6:4321", "push_endpoint_args": "", "push_endpoint_topic": "ahk2", "stored_secret": false, "persistent": true, "persistent_queue": ":ahk2", "time_to_live": "None", "max_retries": "None", "retry_sleep_duration": "None" }, "arn": "arn:aws:sns:geored_zg::ahk2", "opaqueData": "", "policy": "" } ] } ] } I call it again, in an identical manner: $ rga topic list { "topics": [ { "topics": [ { "owner": "ahk2", "name": "ahk2", "dest": { "push_endpoint": "http://1.2.3.6:4321", "push_endpoint_args": "", "push_endpoint_topic": "ahk2", "stored_secret": false, "persistent": true, "persistent_queue": "", "time_to_live": "None", "max_retries": "None", "retry_sleep_duration": "None" }, "arn": "arn:aws:sns:geored_zg::ahk2", "opaqueData": "", "policy": "" } ] } ] } Notice that the "persistent_queue" field is gone. I now hit errors trying to use my topic, for example: $ rga topic stats --topic ahk2 This topic does not have a persistent queue. Suspect this might be a bug in the RC. Happy to open a tracker if so. Unless I'm doing something stupid...? Best Wishes, Alex
participants (1)
-
Alex Hussein-Kershaw (HE/HIM)