Friday, 2022-09-02

opendevreviewMerged openstack/openstack-ansible-ceph_client master: Provide opportunity to define cluster_name  https://review.opendev.org/c/openstack/openstack-ansible-ceph_client/+/85258800:42
*** chandankumar is now known as chkumar|ruck05:02
*** ysandeep|out is now known as ysandeep05:22
noonedeadpunkdamiandabrowski: pls take a look at https://review.opendev.org/c/openstack/openstack-ansible/+/855255 when possible 06:55
damiandabrowskimorning, done ;)07:00
*** arxcruz is now known as arxcruz|rover07:12
anskiyjamesdenton: I haven't been able to reproduce the problem with OVN cluster not upgrading, at least, on newly created OVN cluster, without ovn-controllers/openstack. I can possibly try to install test Xena cluster with more controller nodes and try to upgrade to Yoga, but I did it prior to "production" upgrade and haven't catched that error, at least with one controller.07:33
anskiynon-cluster setup seems to be upgrading just fine too07:33
*** ysandeep is now known as ysandeep|afk09:49
*** ysandeep|afk is now known as ysandeep11:08
*** carloss is now known as carloss|afk11:28
jamesdentoni believe you. i will try an OVN MNAIO and see - i don't think we have any specific "cluster upgrade" task, so if it's not rolled into an OVS/OVN service restart then we might be missing something11:32
jamesdentonnoonedeadpunk: when you have a sec, please let me know about this: https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/85557311:34
noonedeadpunkah, that's good one11:42
noonedeadpunkthanks11:42
*** carloss|afk is now known as carloss13:03
anskiyjamesdenton: this environment on which I've tested upgrade is kinda similar to MNAIO, I just spawn it with Vagrant: one controller, one compute, one deployment host and a couple more VMs to help replicate "production" network and storage. "cluster upgrade" thing SHOULD be run on service restart, as it's backend in execstart script for ovsdb. Maybe, something was just more broken with my "production" setup13:41
jamesdentonFWIW i have done a 24.x -> 25.0.0 upgrade in the last few weeks and don't recall any OVN-related issue.13:42
anskiymaybe, even prior to X->Y upgrade, as this thing survived W->X upgrade already, but I do believe, that schema version in SB_Global DB was set to the version, that is used in OVN/OVS 20.0313:42
anskiyyeah, that's what I'm talking: could be just some different problem on my end13:43
jamesdentonquite possible, good to know either way13:45
jamesdentoni am happy to say i know enough to know i don't know13:46
anskiywell, at least, I know how to fix this thing if it ever breaks :)13:46
noonedeadpunkwell, for X our OVN implementation was a bit different as it was jsut adopted quite recently13:49
noonedeadpunk(back then)13:49
jamesdentonnon-proper cluster implementation vs now?13:56
anskiynah, I was carrying those spatel patches for proper cluster since the beginning in W14:01
spatelsorry i am not able to see offline messages.. just curious what is going on here?14:04
spateli did upgrade from W -> X in OVN deployment without issue.. 14:04
spatelbecause upgrade process just going to upgrade your distro binaries of ovn and openvswitch14:05
noonedeadpunkthere was some issue that ovndb did not get upgraded when binaries were14:05
opendevreviewMerged openstack/openstack-ansible-os_neutron master: Switch jobs from CentOS 8 Stream to CentOS 9 Stream  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/85557314:05
spatelnoonedeadpunk hmm 14:06
anskiyspatel: so I had to run upgrade manually, and can't reproduce this thing now. That's it.14:08
anskiycould be just my broken environment, that highlight was more for appreciation of work :)14:09
spatelnoonedeadpunk i am not seeing it required anything to update DB - https://docs.ovn.org/en/stable/intro/install/ovn-upgrades.html14:09
spatelanskiy How did you upgrade manually just curious? 14:10
anskiyoh god... so, `upgrade_cluster` function is located in "library" (`/usr/share/openvswitch/scripts/ovs-lib`), which sourced in `/usr/share/ovn/scripts/ovn-ctl`14:12
spatelhmm interesting 14:13
anskiyhttps://github.com/openvswitch/ovs/blob/024ba52575e3110118bbedc91f1c0d75eb60b8e8/utilities/ovs-lib.in14:13
anskiyI've either sourced it and called this thing directly, or fixed startup script `/usr/share/ovn/scripts/ovn-ctl` to always explicitly run upgrade, not quite sure now :)14:15
jamesdentonnoted. will see if it happens again! :)14:16
anskiythis is how broken state looks in ovn-northd: https://paste.opendev.org/show/big24pUad9s4COBTREB1/14:20
anskiyand all agents become dead, because neutron checks that https://paste.opendev.org/show/bXpHnsB7ohB6eQmqMl0b/ *_cfg's values are the same (or less, than one) in all databases (can't quite remember which ones are important, but during normal operation they should be the same14:22
anskiyand here, you can see the DB "version"14:23
anskiywhich should somewhat replicate the OVN's package version14:24
noonedeadpunkthat is veeeery interesting. 14:28
*** ysandeep is now known as ysandeep|out14:34
anskiynoonedeadpunk: well, here is the code for you then! https://opendev.org/openstack/neutron/src/branch/master/neutron/plugins/ml2/drivers/ovn/agent/neutron_agent.py#L99-L11114:34
noonedeadpunkyeah, I just did not have chance to get my hands into ovn14:35
noonedeadpunkso just writing down everything that might go wrong for the future me14:36
*** dviroel is now known as dviroel|lunch15:13
noonedeadpunkfwiw I already applied https://review.opendev.org/c/openstack/openstack-ansible/+/855184 from my AZ sandbox and overrides are soooo much cleaner now, so thank for contributing back anskiy :)15:40
anskiynoonedeadpunk: it was mostly your idea, but thanks :)15:59
opendevreviewJames Denton proposed openstack/openstack-ansible-os_neutron master: Dynamic ovn-encap-type configuration  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/85063916:09
*** dviroel|lunch is now known as dviroel16:41
*** dviroel is now known as dviroel|out20:56

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!