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

Make ingress-per-app compatible with ops 2.10.0 #293

Closed
natalian98 opened this issue Feb 15, 2024 · 2 comments
Closed

Make ingress-per-app compatible with ops 2.10.0 #293

natalian98 opened this issue Feb 15, 2024 · 2 comments

Comments

@natalian98
Copy link
Contributor

Enhancement Proposal

Ingress-per-unit relies on ops 2.10 behaviour that breaking relations don't show up in model.relations.
A similar fix is needed for ingress-per-app, see this conversation for reference.

@PietroPasotti
Copy link
Contributor

By looking at the traceback, I don't see how ingress-per-app is related.
I think the issue you're having is that adding a relation to the harness doesn't automatically add a network for it, which the library (rightfully) expects.
Are you saying this changed with some recent release of ingress, or of ops?

Maybe it's behaviour that has changed in ops 2.10 with respect to 2.9, but I don't recall seeing anything about this.

@PietroPasotti
Copy link
Contributor

Fixed by: canonical/operator#1138

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

No branches or pull requests

2 participants