@linux3276fan - The ovn-chassis charm is a subordinate (i.e. doesn't have it's 'own' machine) and thus the packages for ovn on the same unit as a subordinate charm come from the principle charm which should be running jammy-zed, but jammy-zed should have 22.09 for the principle charm.
So looking at the juju status for nova-compute (ovn-chassis' parent) and nova-cloud-controller:
nova-cloud-controller 26.1.1 active 1 nova-cloud-controller zed/stable 655 no Unit is ready
nova-compute 25.1.1 active 8 nova-compute zed/stable 661 no Unit is ready
i.e. nova-compute is running 25.1.1 which is yoga (https://releases.openstack.org/yoga/) whereas the controller is running zed. Somehow, nova-compute is misconfigured or has a bug. Please could you check the output of the config for nova-compute:
@linux3276fan - The ovn-chassis charm is a subordinate (i.e. doesn't have it's 'own' machine) and thus the packages for ovn on the same unit as a subordinate charm come from the principle charm which should be running jammy-zed, but jammy-zed should have 22.09 for the principle charm.
e.g. rmadison for zed shows.
ovn | 22.09.1- 0ubuntu0. 22.10.1~ cloud0 | zed | jammy-updates | source 0ubuntu0. 22.10.1~ cloud0 | zed-proposed | jammy-proposed | source
ovn | 22.09.1-
So looking at the juju status for nova-compute (ovn-chassis' parent) and nova-cloud- controller:
nova-cloud- controller 26.1.1 active 1 nova-cloud- controller zed/stable 655 no Unit is ready
nova-compute 25.1.1 active 8 nova-compute zed/stable 661 no Unit is ready
i.e. nova-compute is running 25.1.1 which is yoga (https:/ /releases. openstack. org/yoga/) whereas the controller is running zed. Somehow, nova-compute is misconfigured or has a bug. Please could you check the output of the config for nova-compute:
juju config nova-compute | less
and see what the openstack-origin is set to?