Name is error when finding revision_number in CheckRevisionNumber

Bug #1745103 reported by XuRong
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-ovn
Fix Released
Undecided
Unassigned

Bug Description

Just for test:

MariaDB [neutron]> update standardattributes set revision_number=9 where id=13;
MariaDB [neutron]> select * from standardattributes where id=13;
| 13 | routers | 2018-01-10 05:55:51 | 2018-01-24 03:15:48 | | 9 |

[root@devstack-147 ~]# ovn-nbctl list logical_router | grep external_ids
external_ids : {"neutron:gw_port_id"="f4683ce8-6b87-4d3d-88f4-ae1033947152", "neutron:revision_number"="12", "neutron:router_name"="router2"}

[root@devstack-147 ~]# neutron router-update 3da0ea0f-c01f-40ec-86ed-b3475edb02ea --name router1
[root@devstack-147 ~]# ovn-nbctl list logical_router | grep external_ids
external_ids : {"neutron:gw_port_id"="f4683ce8-6b87-4d3d-88f4-ae1033947152", "neutron:revision_number"="10", "neutron:router_name"="router1"}

This is because no information is matched to logical_router in CheckRevisionNumberCommand

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-ovn (master)

Reviewed: https://review.openstack.org/537282
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=17f62a5d68d73ef9be8311b9d56542baf814e154
Submitter: Zuul
Branch: master

commit 17f62a5d68d73ef9be8311b9d56542baf814e154
Author: xurong00037997 <email address hidden>
Date: Wed Jan 24 11:51:47 2018 +0800

    Name is error when finding revision_number in CheckRevisionNumber

    Change-Id: Ic13cc467aaf863f6bc18cccb5c9632722dd71b38
    Closes-bug: #1745103

Changed in networking-ovn:
status: New → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-ovn 4.0.0.0rc1

This issue was fixed in the openstack/networking-ovn 4.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-ovn 5.0.0.0b1

This issue was fixed in the openstack/networking-ovn 5.0.0.0b1 development milestone.

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.