[Bug 2059721] Re: ovn db upgrade
Nah, I guess I just meant - after it. I just spotted that DB schema was updated only when ovn-northd -> ovn-central are restarted. For me ovn- central did not start on it's own, but I cut couple of corners while trying to reproduce the issue. Eventually, I just upgraded a host rather then re-install it. So that's why it could be working in my test env, as database was present on the expected location during OVN startup, rather then it needs to fetch it and convert. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059721 Title: ovn db upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/2059721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059721] Re: ovn db upgrade
Actually, I do have `2024-03-29T11:34:33.886Z|00041|main|INFO|OVNSB commit failed, force recompute next time.` - but I do get it on ovn- controller (compute) node which was not upgraded yet. Also I do not see that message right after service restart anymore: https://paste.openstack.org/show/bJDQ7Gx5e9zmzv4zN7HQ/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059721 Title: ovn db upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/2059721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059721] Re: ovn db upgrade
No, I do not. That is basically the whole log I got on one of isntances: https://paste.openstack.org/show/brE4aA8VFptpmMkGn8EE/ Though keep in mind, that I tried that on dummy sandbox. Also question - you've upgraded controllers or re-installed? As I assume you did rebuild ovn-northd containers afterwards? I'm just trying to find a way reproducing that in any way. And I indeed do see couple of chicken-egg situations already - as you've mentioned ordering of compute/controller upgrade. As eventually, to successfully upgrade compute you'd need to have at least 1 upgraded repo container for building wheels, otherwise OpenStack infrastructure could be exposed to quite heavy load if you'd deploy XX amount of computes at the same time... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059721 Title: ovn db upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/2059721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059721] Re: ovn db upgrade
Hi, So, I totally see issues in ordering of tasks for OVN upgrade and couple of missing handlers we obviously need to cover. However, I was able to launch OVN cluster after upgrade. Basically, these steps should be taken for successful upgrade: 1. Upgrade/restart all ovn-controllers 2. Upgrade ovn-northd. Once it's upgraded you need to restart ovn-northd service and ovn-central right after it. Once 2 out of 3 ovn-northd are upgraded, DB upgrade will be performed to the new schema. So eventually, I've updated 1st ovn-northd container to 22.04 and I got same output as you did: root@aio1-neutron-ovn-northd-container-519166b6:/# ovn-nbctl --version ovn-nbctl 23.03.1 Open vSwitch Library 3.1.2 DB Schema 7.0.0 root@aio1-neutron-ovn-northd-container-519166b6:/# ovsdb-client get-schema-version unix:/var/run/ovn/ovnnb_db.sock 6.1.0 root@aio1-neutron-ovn-northd-container-519166b6:/# Then, I've updated second container to 22.04 and restarted ovn-northd and ovn-central, and got new schema on the first one right away: root@aio1-neutron-ovn-northd-container-519166b6:/# ovsdb-client get-schema-version unix:/var/run/ovn/ovnnb_db.sock 7.0.0 root@aio1-neutron-ovn-northd-container-519166b6:/# I will work on role/playbooks to cover upgrade process ordering and found nits. ** Changed in: openstack-ansible Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059721 Title: ovn db upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/2059721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059721] Re: ovn db upgrade
Hey, Thanks for reporting that. I believe OpenStack-Ansible indeed miss a required step for proper OVN upgrade on OS resetup. I will check on the issue in a timely manner. ** Changed in: openstack-ansible Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059721 Title: ovn db upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/2059721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902293] Re: fixed_network_name still exists in drivers except heat
I've reported bug to magnum https://storyboard.openstack.org/#!/story/2008596 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902293 Title: fixed_network_name still exists in drivers except heat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1902293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902293] Re: fixed_network_name still exists in drivers except heat
fedora-coreos worked for me as well. That totally sounds like magnum bug... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902293 Title: fixed_network_name still exists in drivers except heat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1902293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909843] Re: high CPU usage when running nothing
Also I'd suggest joining #openstack-ansible IRC channel on Freenode for futher community help with solving out this issue ** Changed in: openstack-ansible Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909843 Title: high CPU usage when running nothing To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1909843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909843] Re: high CPU usage when running nothing
In case it's openstack-ansible, I'd suggest decreasing amount of workers you're using since they may cause high load in small systems. ie for CI we're using https://opendev.org/openstack/openstack- ansible/src/branch/master/tests/roles/bootstrap- host/templates/user_variables.aio.yml.j2#L50-L176 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909843 Title: high CPU usage when running nothing To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1909843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909843] Re: high CPU usage when running nothing
I'm not sure it's realted to openstack-ansible, at least according to screenshot, since we support lxd at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909843 Title: high CPU usage when running nothing To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1909843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741247] Re: Upgrade from Ocata fails with timeout
** Changed in: openstack-ansible Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741247 Title: Upgrade from Ocata fails with timeout To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1741247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881874] Re: Unable to launch Loadbalancer from Horizon Dashboard
This is now merged to the stable train and will be released with upcoming 20.1.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881874 Title: Unable to launch Loadbalancer from Horizon Dashboard To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1881874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1101647] Re: ID 138a:003d Validity Sensors, Inc.
Agree, nothing changed untill now -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101647 Title: ID 138a:003d Validity Sensors, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1101647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
