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?
Thank You,
Karthik C
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
