No column dpdk_version in table Open_vSwitch

Bug #1792496 reported by ByungYeol Woo
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
High
Michal Nasiadka

Bug Description

-kolla-anbile version: 7.0.0.0rc2.dev14
-install type: source, distro: ubuntu
-kolla image: built by kolla-build at 2018.09.04 and openstack release is Rocky

I upgraded neutron from 13.0.0.0rc2.dev18 to 13.0.0.0rc2.dev121.
It was successful, but weird logs were found on every openvswich nodes after upgrading altough I don't use dpdk.

----------- ovs-vswitchd.log -------------
2018-09-14T03:25:26.251Z|00476|ovsdb_idl|WARN|Dropped 667 log messages in last 59 seconds (most recently, 0 seconds ago) due to excessive rate
2018-09-14T03:25:26.251Z|00477|ovsdb_idl|WARN|transaction error: {"details":"No column dpdk_version in table Open_vSwitch.","error":"unknown column","syntax":"{\"dpdk_version\":\"none\"}"}

Revision history for this message
ByungYeol Woo (wby1089) wrote :

I found db schema was updated after upgrading of ovs-db.
After upgrading of db schema, those error messages was disappeared.

--------------------------
(openvswitch-db)[root@net01 /]# ovssdb-tool needs-conversion
yes

(openvswitch-db)[root@net01 /]# ovssdb-tool convert /var/lib/openvswitch/conf.db
...

(openvswitch-db)[root@net01 /]# ovsdb-tool needs-conversion
no
--------------------------

I think ovs's db schema needs to be converted after upgrade and this procedure needs to be added at upgrade.yml of openvswitch role.

Revision history for this message
Ian Kumlien (pomac) wrote :

It looks like it just needs something along the lines of:
TMP=$(/usr/bin/ovsdb-tool needs-conversion /var/lib/openvswitch/conf.db)

if [ $TMP eq "yes" ]; then
  /usr/bin/ovsdb-tool convert /var/lib/openvswitch/conf.db
fi
---

In start-ovsdb-server

Revision history for this message
Serhat Rıfat Demircan (serhatd) wrote :
Download full text (4.2 KiB)

This bug report is still valid.

We installed Openstack Queens release from stable/queens branch than tried to upgrade it to Rocky from stable/rocky branch. All task completed without a error but we could not launch a new instance.

We got following errors in log files:

nova-compute.log:
-----------------
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] Traceback (most recent call last):
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/nova/compute/manager.py", line 2132, in _build_and_run_instance
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] block_device_info=block_device_info)
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 3080, in spawn
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] destroy_disks_on_failure=True)
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 5625, in _create_domain_and_network
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] destroy_disks_on_failure)
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] self.force_reraise()
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] six.reraise(self.type_, self.value, self.tb)
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 5604, in _create_domain_and_network
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] error_callback=self._neutron_failed_callback):
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] File "/usr/lib/python2.7/contextlib.py", line 17, in __enter__
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] return self.gen.next()
2019-03-25 13:55:48.841 6 ERROR nova.compute.manager [instance: 8993d64b-47d1-4328-a9b1-87dea1a6fbae] File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/nova/compute/manager.py", line 474, in wait_for_instance_event
2019-03-25 13:55:48.841 6 ERROR nova.compute.mana...

Read more...

Changed in kolla-ansible:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Michal Nasiadka (mnasiadka)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (master)

Fix proposed to branch: master
Review: https://review.openstack.org/648516

Changed in kolla-ansible:
status: Triaged → In Progress
Changed in kolla-ansible:
milestone: none → 8.0.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.openstack.org/648516
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=2a6070b963b99b2b0477b6352502fc3a81564989
Submitter: Zuul
Branch: master

commit 2a6070b963b99b2b0477b6352502fc3a81564989
Author: Michal Nasiadka <email address hidden>
Date: Thu Mar 28 20:33:00 2019 +0100

    Add support for ovsdb conversion

    After upgrade we should check if OVSDB doesn't need conversion to new
    version - this patch adds that to ovsdb start script.

    Change-Id: Ifa8766d050b506708142a1970121ce5944c6bae1
    Closes-Bug: #1792496

Changed in kolla-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 8.0.0.0rc1

This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (stable/rocky)

Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/709451

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (stable/rocky)

Reviewed: https://review.opendev.org/709451
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=f72b8e82c29308cae3360558600d4df33807240d
Submitter: Zuul
Branch: stable/rocky

commit f72b8e82c29308cae3360558600d4df33807240d
Author: Michal Nasiadka <email address hidden>
Date: Thu Mar 28 20:33:00 2019 +0100

    Add support for ovsdb conversion

    After upgrade we should check if OVSDB doesn't need conversion to new
    version - this patch adds that to ovsdb start script.

    Change-Id: Ifa8766d050b506708142a1970121ce5944c6bae1
    Closes-Bug: #1792496
    (cherry picked from commit 2a6070b963b99b2b0477b6352502fc3a81564989)

tags: added: in-stable-rocky
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 7.2.1

This issue was fixed in the openstack/kolla-ansible 7.2.1 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.