podman: sdnotify play kube policies: podman container wait, hangs

[+1368s] not ok 310 sdnotify : play kube - with policies
...
$ podman container inspect test_pod-a --format {{.Config.SdNotifySocket}}
/var/tmp/-podman-notify-proxy.sock54032352
$ podman logs test_pod-a
/run/notify/notify.sock
READY
$ podman exec test_pod-a /bin/touch /stop
$ podman container inspect 9cffc8377ee1-service --format {{.State.ConmonPid}}
98526
$ podman container wait test_pod-a
timeout: sending signal TERM to command ?/var/tmp/go/src/github.com/containers/podman/bin/podman?
[ rc=124 (** EXPECTED 0 **) ]
*** TIMED OUT ***

• fedora-36 : sys podman fedora-36 rootless host
  • PR #16034
    • 10-03 15:32
    • 10-03 11:37
• fedora-36 : sys podman fedora-36 root host
  • PR #15794
    • 09-14 14:10
• fedora-36 : sys podman fedora-36 rootless host
  • PR #15846
    • 09-29 10:32
  • PR #15844
    • 09-17 08:32
  • PR #15796
    • 09-14 09:34
  • PR #15786
    • 09-14 13:49
  • PR #15072
    • 09-15 09:34
• fedora-36 : sys podman fedora-36 rootless host
  • PR #15933
    • 09-26 12:53
• fedora-36-aarch64 : sys podman fedora-36-aarch64 root host
  • PR #15910
    • 09-24 09:08
• fedora-36 : sys podman fedora-36 rootless host
  • PR #15753
    • 09-12 22:10
• fedora-36 : sys podman fedora-36 root host
  • PR #15695
    • 09-09 07:22

Looks like Sept 9 is the first logged instance.

So far, f36 only (both amd64 and aarch64), root and rootless.