Comment 5 for bug 2065754

I've updated the MP with test cases for this change. To run them, do:

    $ make check

I built the snap and tried to reproduce Mitchell's finding but the snap seems to show the fixed behavior okay for me:

stirling: ~/src/PpaDevTools/ppa-dev-tools$ /snap/bin/ppa-dev-tools.ppa tests https://launchpad.net/~mitchdz/+archive/ubuntu/rabbitmq-server-mre-2204/
The authorization page:
 (https://launchpad.net/+authorize-token?oauth_token=SWQnVhtZWkLF7QPVhLBz&allow_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
* Triggers:
  - Source rabbitmq-server/3.9.27-0ubuntu0.1~jammy8: Published
    + Trigger basic @amd64♻️ Trigger all-proposed @amd64💍
    + Trigger basic @arm64♻️ Trigger all-proposed @arm64💍
    + Trigger basic @armhf♻️ Trigger all-proposed @armhf💍
    + Trigger basic @i386♻️ Trigger all-proposed @i386💍
    + Trigger basic @ppc64el♻️ Trigger all-proposed @ppc64el💍
    + Trigger basic @s390x♻️ Trigger all-proposed @s390x💍
  - Source rabbitmq-server/3.8.3-0ubuntu0.1~focal5: Published
    + Trigger basic @amd64♻️ Trigger all-proposed @amd64💍
    + Trigger basic @arm64♻️ Trigger all-proposed @arm64💍
    + Trigger basic @armhf♻️ Trigger all-proposed @armhf💍
    + Trigger basic @i386♻️ Trigger all-proposed @i386💍
    + Trigger basic @ppc64el♻️ Trigger all-proposed @ppc64el💍
    + Trigger basic @s390x♻️ Trigger all-proposed @s390x💍
* Results:
  - rabbitmq-server/3.8.3-0ubuntu0.1~focal5
    + ⛔ rabbitmq-server on focal for amd64 @ 16.05.24 01:43:46 Log️ 🗒️
      • testbed BAD ⛔
    + ✅ rabbitmq-server on focal for amd64 @ 21.05.24 14:50:15 Log️ 🗒️
    + ⛔ rabbitmq-server on focal for arm64 @ 12.05.24 03:07:20 Log️ 🗒️
      • testbed BAD ⛔
    + ✅ rabbitmq-server on focal for arm64 @ 21.05.24 14:50:48 Log️ 🗒️
    + ⛔ rabbitmq-server on focal for armhf @ 11.05.24 08:01:13 Log️ 🗒️
      • testbed BAD ⛔
    + ✅ rabbitmq-server on focal for armhf @ 21.05.24 14:53:34 Log️ 🗒️
    + ✅ rabbitmq-server on focal for i386 @ 11.05.24 13:35:11 Log️ 🗒️
    + ✅ rabbitmq-server on focal for ppc64el @ 14.05.24 23:10:14 Log️ 🗒️
    + ✅ rabbitmq-server on focal for s390x @ 14.05.24 03:20:42 Log️ 🗒️
  - rabbitmq-server/3.9.27-0ubuntu0.1~jammy4
    + ✅ rabbitmq-server on jammy for amd64 @ 06.05.24 23:39:20 Log️ 🗒️
    + ✅ rabbitmq-server on jammy for arm64 @ 06.05.24 23:21:35 Log️ 🗒️
    + ✅ rabbitmq-server on jammy for armhf @ 06.05.24 23:22:57 Log️ 🗒️
    + ✅ rabbitmq-server on jammy for i386 @ 06.05.24 23:39:34 Log️ 🗒️
    + ✅ rabbitmq-server on jammy for ppc64el @ 06.05.24 23:23:10 Log️ 🗒️
    + ✅ rabbitmq-server on jammy for s390x @ 06.05.24 23:23:28 Log️ 🗒️
  - rabbitmq-server/3.9.27-0ubuntu0.1~jammy8
    + ⛔ rabbitmq-server on jammy for amd64 @ 17.05.24 10:35:04 Log️ 🗒️
      • testbed BAD ⛔
    + ❌ rabbitmq-server on jammy for amd64 @ 17.05.24 20:50:40 Log️ 🗒️
      • smoke-test PASS 🟩
      • hello-world PASS 🟩
      • work-queue PASS 🟩
      • publish-subscribe PASS 🟩
      • rpc FAIL 🟥
    + ✅ rabbitmq-server on jammy for arm64 @ 13.05.24 19:10:51 Log️ 🗒️
    + ⛔ rabbitmq-server on jammy for armhf @ 13.05.24 12:50:51 Log️ 🗒️
      • testbed BAD ⛔
    + ✅ rabbitmq-server on jammy for armhf @ 16.05.24 14:21:04 Log️ 🗒️
    + ✅ rabbitmq-server on jammy for i386 @ 13.05.24 19:16:38 Log️ 🗒️
    + ❌ rabbitmq-server on jammy for ppc64el @ 16.05.24 01:29:45 Log️ 🗒️
      • smoke-test PASS 🟩
      • hello-world PASS 🟩
      • work-queue PASS 🟩
      • publish-subscribe PASS 🟩
      • rpc FAIL 🟥
    + ✅ rabbitmq-server on jammy for ppc64el @ 16.05.24 13:18:08 Log️ 🗒️
    + ✅ rabbitmq-server on jammy for s390x @ 15.05.24 01:04:39 Log️ 🗒️
* Running: (none)
* Waiting: (none)

I had to specify the path explicitly since the pip installation seems to take precidence in my PATH. Might be something to doublecheck.

Anyway, let me go ahead and land this, and Mitchell tomorrow you can try installing the snap from the nightly that includes this fix, and see if it is resolved.