Description of problem (please be detailed as possible and provide log
snippests):

RBD mirroring only allows one peer, in an attempt to remove a cluster with 2 peers configured, we are running this command: "rbd mirror pool peer remove ocs-storagecluster-cephblockpool"

Running this command removes it for a moment, then it is re-added with a different UUID.
rbd mirror pool peer remove ocs-storagecluster-cephblockpool 4ff383e6-2417-44fa-baa4-67767b937853

Question:
1. Is there an issue with this command as it is only removing it for it to be re-added with a different UUID?

Version of all relevant components (if applicable): ODF 4.13, OCP 4.13

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)? Product still works. RBD is still working on the other cluster

Is there any workaround available to the best of your knowledge?

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?

Can this issue reproducible? Yes steps below

Can this issue reproduce from the UI? n/a

If this is a regression, please provide more details to justify this:

Steps to Reproduce:
sh-5.1$ rbd mirror pool status ocs-storagecluster-cephblockpool

health: ERROR
daemon health: ERROR
image health: OK
images: 0 total
sh-5.1$ rbd mirror pool info ocs-storagecluster-cephblockpool

Mode: image
Site Name: e4d70934-6c49-431a-8a4d-c5494c6be35a

Peer Sites:

UUID: 4ff383e6-2417-44fa-baa4-67767b937853
Name: 23e67d87-fc7b-4a4c-8adb-c71ab26a1960
Mirror UUID: 45c83bbe-7423-4a04-936e-e8289b78802b
Direction: tx-only

UUID: 98c7412f-8399-42ab-9ba3-6ecd0c591a6a
Name: dc18825b-d207-4540-a7b5-e9bfbaca8815
Mirror UUID: 3e91649f-f6f4-45d0-bcd8-8a3a24940852
Direction: rx-tx
Client: client.rbd-mirror-peer
sh-5.1$ rbd mirror pool disable ocs-storagecluster-cephblockpool

2023-12-15T04:55:46.695+0000 7fa71237db80 -1 librbd::api::Mirror: mode_set: mirror peers still registered
sh-5.1$ rbd mirror pool peer remove ocs-storagecluster-cephblockpool 4ff383e6-2417-44fa-baa4-67767b937853
sh-5.1$ rbd mirror pool status ocs-storagecluster-cephblockpool

health: ERROR
daemon health: ERROR
image health: OK
images: 0 total
sh-5.1$ rbd mirror pool info ocs-storagecluster-cephblockpool

Mode: image
Site Name: e4d70934-6c49-431a-8a4d-c5494c6be35a

Peer Sites:

UUID: 98c7412f-8399-42ab-9ba3-6ecd0c591a6a
Name: dc18825b-d207-4540-a7b5-e9bfbaca8815
Mirror UUID: 3e91649f-f6f4-45d0-bcd8-8a3a24940852
Direction: rx-tx
Client: client.rbd-mirror-peer

UUID: 9c42f2b4-919c-4f5b-b60a-218351a0130e
Name: 23e67d87-fc7b-4a4c-8adb-c71ab26a1960
Mirror UUID: 45c83bbe-7423-4a04-936e-e8289b78802b
Direction: tx-only
sh-5.1$ rbd mirror pool enable ocs-storagecluster-cephblockpool pool

note: changing mirroring mode from image to pool
sh-5.1$ rbd mirror pool status ocs-storagecluster-cephblockpool

health: ERROR
daemon health: ERROR
image health: OK
images: 0 total
sh-5.1$ rbd mirror pool info ocs-storagecluster-cephblockpool

Mode: pool
Site Name: e4d70934-6c49-431a-8a4d-c5494c6be35a

Peer Sites:

UUID: 98c7412f-8399-42ab-9ba3-6ecd0c591a6a
Name: dc18825b-d207-4540-a7b5-e9bfbaca8815
Mirror UUID: 3e91649f-f6f4-45d0-bcd8-8a3a24940852
Direction: rx-tx
Client: client.rbd-mirror-peer

UUID: 9c42f2b4-919c-4f5b-b60a-218351a0130e
Name: 23e67d87-fc7b-4a4c-8adb-c71ab26a1960
Mirror UUID: 45c83bbe-7423-4a04-936e-e8289b78802b
Direction: tx-only

Actual results:

The tx-only is readded with a different UUID

Expected results:

Expecting it to be removed

Additional info: