On Thu, Feb 25, 2021 at 1:24 AM Karthik Chandrashekar
<karthi...@nutanix.com> wrote:
>
> OVN upgrade documentation talks about upgrading the ovn-controller first
> followed by upgrade to OVN database and ovn-northd. However this doesn’t seem
> to work for upgrade from v2.11 to OVN v20.09.
>
>
>
> v2.11 is running "OVN_Southbound" schema, version="2.0.2"
>
> When you upgrade the ovn-controller first the controller tries to register
> the Chassis and fails.
>
> 2021-02-24T19:27:19.640Z|00073|ovsdb_idl|WARN|transaction error:
> {"details":"No column other_config in table Chassis.","error":"unknown
> column","syntax":"{\"encaps\":[\"named-uuid\",\"rowbd2a07f5_ca59_447e_9972_fb02458c8e53\"],\"external_ids\":[\"map\",[[\"datapath-type\",\"\"],[\"iface-types\",\"erspan,geneve,gre,gtpu,internal,ip6erspan,ip6gre,lisp,patch,stt,system,tap,vxlan\"],[\"is-interconn\",\"false\"],[\"ovn-bridge-mappings\",\"physnet0:br0\"],[\"ovn-chassis-mac-mappings\",\"\"],[\"ovn-cms-options\",\"\"],[\"ovn-enable-lflow-cache\",\"true\"],[\"ovn-monitor-all\",\"false\"]]],\"hostname\":\"karthikc_controller_2\",\"name\":\"node_2\",\"other_config\":[\"map\",[[\"datapath-type\",\"\"],[\"iface-types\",\"erspan,geneve,gre,gtpu,internal,ip6erspan,ip6gre,lisp,patch,stt,system,tap,vxlan\"],[\"is-interconn\",\"false\"],[\"ovn-bridge-mappings\",\"physnet0:br0\"],[\"ovn-chassis-mac-mappings\",\"\"],[\"ovn-cms-options\",\"\"],[\"ovn-enable-lflow-cache\",\"true\"],[\"ovn-monitor-all\",\"false\"]]]}"}
>
> The SB schema is unaware of this new column and hence we are in a transient
> state where the chassis don’t show till we complete the schema and northd
> upgrades. Is this expected? What is the suggested order of upgrades to move
> from v2.11 to OVN v20.09?
Unfortunately the recommended upgrade procedure is broken because of
this. So you will have datapath downtime until
you upgrade ovn-northd to the same version.
A while back we added a commit [1] which pins ovn-controller to the
same version of ovn-northd, and if there is any mismatch,
it doesn't do anything keeping the existing flows intact. This commit
is in OVN v20.12+
So you can consider upgrading to 20.12 and enabling the option -
ovn-match-northd-version
[1] -
https://github.com/ovn-org/ovn/commit/1dd27ea7aea40122c1edbff845e14abaa70c0413
Thanks
Numan
>
> Thank You,
> Karthik C
>
> _______________________________________________
> discuss mailing list
> disc...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
