Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable/22.03] Bail out configuring ovs if no OVNSDB available #97

Merged

Conversation

dosaboy
Copy link
Contributor

@dosaboy dosaboy commented Oct 8, 2024

When the ovsdb relation is departing the hook will fail since it will try to configure ovs while only partial information is available.

Closes-Bug: #1944983

When the ovsdb relation is departing the hook will fail since it will
try to configure ovs while only partial information is available.

Closes-Bug: #1944983
@dosaboy dosaboy changed the title Bail out configuring ovs if no OVNSDB available [stable/22.03] Bail out configuring ovs if no OVNSDB available Oct 8, 2024
else:
ch_core.hookenv.log('could not configure ovs due to unavailable '
'sbdb connection info - ovn-central relation '
'no longer available?',
Copy link
Contributor

Choose a reason for hiding this comment

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

Just have a nit on the message, should make it look like the one at the beginning of the function, something like:

'Could not configure Open vSwitch due to unavailable SBDB connection info - ovn-central relation no longer available?'

So what is the solution when this happens? Can we add more info to help get past it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thats a fair point re the msg, could get that fixed on master. this is is really fixing the case where the application is being uninstalled e.g. when the node is being released to stop it raising an exception. Therefore it is not something that will need resolving.

@javacruft javacruft merged commit 40d34ea into openstack-charmers:stable/22.03 Oct 9, 2024
3 checks passed
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.

3 participants