So I did a little debugging here.
DVR router (router1) $ openstack router set --disable router1 All ports (3) showed in DOWN state
$ openstack router set --ha router1 $ openstack router set --enable router1 All ports showed in ACTIVE state
$ openstack router set --disable router1 All ports still in ACTIVE state
Any future attempt to disable the router always showed ports ACTIVE, even if I changed it back to non-ha, so it was permanently broken.
Created a new router, just DVR (router2) - it was fine - could disable/enable and see ports change state.
The fact that the ports got "stuck" would point to an issue on the server-side.
So I did a little debugging here.
DVR router (router1)
$ openstack router set --disable router1
All ports (3) showed in DOWN state
$ openstack router set --ha router1
$ openstack router set --enable router1
All ports showed in ACTIVE state
$ openstack router set --disable router1
All ports still in ACTIVE state
Any future attempt to disable the router always showed ports ACTIVE, even if I changed it back to non-ha, so it was permanently broken.
Created a new router, just DVR (router2) - it was fine - could disable/enable and see ports change state.
The fact that the ports got "stuck" would point to an issue on the server-side.