charm-ovn-chassis

[yoga edge] ovsdb incomplete

Bug #1968699 reported by Marian Gasparovic
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charm-ovn-central
New
Undecided
Unassigned
charm-ovn-chassis
New
Undecided
Unassigned

Bug Description

In SQA testing yoga-focal we encountered this issue. It happens after vault is initialized but all ovn related units stay in waiting indefinitely.

Link to artifacts

https://oil-jenkins.canonical.com/artifacts/6e1710fd-5f24-477d-ac74-e6cc92944d00/index.html

Everything else deployed normally, no error states.

ovn-central/0 waiting idle 3/lxd/8 10.246.167.15 6641/tcp,6642/tcp 'ovsdb-peer' incomplete
  logrotated/43 active idle 10.246.167.15 Unit is ready.
ovn-central/1 waiting idle 4/lxd/9 10.246.167.141 6641/tcp,6642/tcp 'ovsdb-peer' incomplete
  logrotated/48 active idle 10.246.167.141 Unit is ready.
ovn-central/2* active idle 5/lxd/10 10.246.166.205 6641/tcp,6642/tcp Unit is ready (leader: ovnnb_db, ovnsb_db northd: active)
  logrotated/32 active idle 10.246.166.205 Unit is ready.

nova-compute/2 active idle 2 10.246.164.153 Unit is ready
  ceilometer-agent/5 active idle 10.246.164.153 Unit is ready
  lldpd/4 active idle 10.246.164.153 ready
  ovn-chassis/5 waiting idle 10.246.164.153 'ovsdb' incomplete

All of the OVN chassis were in this state

Revision history for this message
Frode Nordahl (fnordahl) wrote :

1) Does it work with a previous version of Juju?

2) Could you please provide the output from ``juju show-unit`` for all vault, ovn-central and ovn-chassis units?

Changed in charm-ovn-central:
status: New → Incomplete
Changed in charm-ovn-chassis:
status: New → Incomplete
Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

1) There's not any data around whether it works with a previous version of Juju as this is an SQA run for the release of yoga/quincy/22.03 for the 22.04 charms set.
2) We'll try to get data on the units, but these are from completed (failed) runs and thus the models have been reaped.

However, this will be a release blocker so we need to work out what's potentially going on.

Marian Gasparovic (marosg)
Changed in charm-ovn-chassis:
status: Incomplete → New
Changed in charm-ovn-central:
status: Incomplete → New
Revision history for this message
Frode Nordahl (fnordahl) wrote :

This is all fine, but we routinely deploy the charm on MAAS with spaces (several times today) and we've not encountered this issue. So there is nothing we can do with this without more information.

Changed in charm-ovn-central:
status: New → Incomplete
Changed in charm-ovn-chassis:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for charm-ovn-chassis because there has been no activity for 60 days.]

Changed in charm-ovn-chassis:
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for charm-ovn-central because there has been no activity for 60 days.]

Changed in charm-ovn-central:
status: Incomplete → Expired
Bas de Bruijne (basdbruijne)
Changed in charm-ovn-central:
status: Expired → New
Changed in charm-ovn-chassis:
status: Expired → New
Revision history for this message
Bas de Bruijne (basdbruijne) wrote :

Its not a very frequent bug, we have seen it on both focal and jammy, yoga and antelope, juju 2.9.28, 2.9.42, 2.9.43.

To find the juju show-unit outputs, 1) download the crashdump (https://oil-jenkins.canonical.com/artifacts/fa7a3246-7c2c-4453-af06-5730f6c7c567/generated/generated/openstack/juju-crashdump-openstack-2023-06-14-04.59.03.tar.gz), 2) navigate to the unit of interest, 3) look in the juju-show-unit dir

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.