Skip to content

Update ovsdb relation to handle multiple relations#64

Open
crypticC0der wants to merge 2 commits intocanonical:mainfrom
crypticC0der:betterovsdb
Open

Update ovsdb relation to handle multiple relations#64
crypticC0der wants to merge 2 commits intocanonical:mainfrom
crypticC0der:betterovsdb

Conversation

@crypticC0der
Copy link
Copy Markdown
Collaborator

Allows ovsdb to support being used by multiple charms, also updates the relation data once a unit has joined the cluster to avoid desync.

Fixes: lp-2138439
Fixes: lp-2138426

@crypticC0der crypticC0der requested a review from a team as a code owner March 6, 2026 18:30
Allows ovsdb to support being used by multiple charms, also updates the
relation data once a unit has joined the cluster to avoid desync.

Fixes: lp-2138439
Fixes: lp-2138426
Signed-off-by: MJ Ponsonby <mj.ponsonby@canonical.com>
return
self.unit.status = ops.MaintenanceStatus("Refreshing MicroOVN snap")
self.microovn_snap_client.install()
self._on_update_status(event)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is CollectStatusEvent

That can run per unit and per leader unit (unit vs app) at every hook (it's an OPS only lifecycle event) if you don't want not to have not to forger to put it everywhere.

Currently if the user is enabling and disabling services through the
microovn snap service control capabilities the ovsdb relation can get
out of date. We would like to make this an invalid use case through a
possible role-distributor but for now we need to support it and the
easiest way to do this is just updating the relation as part of the
update status hook.

Signed-off-by: MJ Ponsonby <mj.ponsonby@canonical.com>
@crypticC0der
Copy link
Copy Markdown
Collaborator Author

flaky tests due to: #63

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants