I confirm - this is due to the way that wrappers are used to run the commands. Note, the ovn-chassis snap moves away from using the wrappers to execute commands as they get in the way.
A hacky work around for the time being, would be to try executing these commands using the snap shell, e.g. "sudo snap run --shell microstack.ovn-trace"
This drops you into an interactive shell where you can exec ovn-trace directly and passing the arguments through. You will likely need to have some environment variables set that the wrappers attempt to do. (see https://github.com/ubuntu-ovn-eng/snap-ovn-chassis/blob/main/snap/snapcraft.yaml#L26 as an example of the env variables set in the ovn-chassis snap).
I confirm - this is due to the way that wrappers are used to run the commands. Note, the ovn-chassis snap moves away from using the wrappers to execute commands as they get in the way.
A hacky work around for the time being, would be to try executing these commands using the snap shell, e.g. "sudo snap run --shell microstack. ovn-trace"
This drops you into an interactive shell where you can exec ovn-trace directly and passing the arguments through. You will likely need to have some environment variables set that the wrappers attempt to do. (see https:/ /github. com/ubuntu- ovn-eng/ snap-ovn- chassis/ blob/main/ snap/snapcraft. yaml#L26 as an example of the env variables set in the ovn-chassis snap).