kolla-ansible

ovn : Unable to set inactivity_probe on ovn-sb and ovn-nb

  1. Series victoria
  2. Bug #1917484
Bug #1917484 reported by cyrille babon
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
High
Michal Nasiadka
Ussuri
Confirmed
Undecided
Unassigned
Victoria
New
Undecided
Unassigned
Wallaby
New
Undecided
Unassigned
Xena
New
Undecided
Unassigned
Yoga
Fix Released
High
Michal Nasiadka

Bug Description

**Bug Report**

What happened:
Many error in ovn log (nb and sb server):
no response to inactivity probe after 5 seconds, disconnecting
And unable to edit inactivity probe with command ovn-nbctl and ovn-sbctl.
First not any connection in list with ovn-nbctl list connection (same for ovn-sbctl)
And if I try to edit with :
ovn-nbctl set-connection ptcp:6641:0.0.0.0 -- set connection . inactivity_probe=60000
I have new log : 6641:0.0.0.0: bind: Address already in use

What you expected to happen:
Possibility to edit inactivity_probe on nb and sb db

How to reproduce it (minimal and precise):
Launch deployment with ovn and try to edit inactivity_probe

**Environment**:
* OS : Ubuntu 18.04.4 LTS (with last ubuntu-source for containers)
* Kernel : 4.15.0-112-generic
* Docker version if applicable : 19.03.11
* Kolla version : Stable Ussuri

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

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/kolla-ansible/+/839501

Changed in kolla-ansible:
status: New → In Progress
Michal Nasiadka (mnasiadka)
Changed in kolla-ansible:
importance: Undecided → High
assignee: nobody → Michal Nasiadka (mnasiadka)
Revision history for this message
ammarun (ammarun) wrote :

Any update on this issue?

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

Reviewed: https://review.opendev.org/c/openstack/kolla-ansible/+/839501
Committed: https://opendev.org/openstack/kolla-ansible/commit/b32d456ea23fe9bb999c06b0c6942bd89c9c1108
Submitter: "Zuul (22348)"
Branch: master

commit b32d456ea23fe9bb999c06b0c6942bd89c9c1108
Author: Michal Nasiadka <email address hidden>
Date: Tue Nov 15 18:20:32 2022 +0000

    ovn: Change NB/SB connection setup to allow usage of inactivity probe

    We have been using --db-nb-create-insecure-remote=yes - that results
    a TCP method is set by ovn-ctl script to run ovsdb-server.

    Downside is - we can't configure inactivity probe on that connection.

    Closes-Bug: #1917484
    Change-Id: I550aa4fe92aadea2a49ca5aff49c0183609b9470

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 15.0.0.0rc1

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

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

Fix proposed to branch: stable/yoga
Review: https://review.opendev.org/c/openstack/kolla-ansible/+/873007

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

Reviewed: https://review.opendev.org/c/openstack/kolla-ansible/+/873007
Committed: https://opendev.org/openstack/kolla-ansible/commit/094c2295cc3a0cba8cfe7210515431b3b378eff6
Submitter: "Zuul (22348)"
Branch: stable/yoga

commit 094c2295cc3a0cba8cfe7210515431b3b378eff6
Author: Michal Nasiadka <email address hidden>
Date: Tue Nov 15 18:20:32 2022 +0000

    ovn: Change NB/SB connection setup to allow usage of inactivity probe

    We have been using --db-nb-create-insecure-remote=yes - that results
    a TCP method is set by ovn-ctl script to run ovsdb-server.

    Downside is - we can't configure inactivity probe on that connection.

    Closes-Bug: #1917484
    Change-Id: I550aa4fe92aadea2a49ca5aff49c0183609b9470
    (cherry picked from commit b32d456ea23fe9bb999c06b0c6942bd89c9c1108)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 14.8.0

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

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

Other bug subscribers

Remote bug watches

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