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
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:
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
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
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
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
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
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.
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
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
** 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
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
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:
13 matches
Mail list logo
