-
Notifications
You must be signed in to change notification settings - Fork 18
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
build: bump juju, ops versions in ci and requirements files #402
Conversation
Bumping juju and ops packages to use them in newer versions of the charms, plus testing them in a CI with a more recent juju version. This commit also skips some test cases that will be removed in a follow up commit introduced by #401. Part of canonical/bundle-kubeflow#859 Part of #398 Signed-off-by: Daniela Plascencia <daniela.plascencia@canonical.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm except for one comment
Do we expect the integration CI to fail here?
So far yes, I have added a comment here. I am experimenting some solutions to unblock us. |
I believe the CI was failing due to a mismatch in the versions that were deployed in these integration tests. This PR is attempting to bump the juju version, which also requires most packages to have a newer |
Bumping juju and ops packages to use them in newer versions of the charms, plus testing them in a CI with a more recent juju version.
This commit also skips some test cases that will be removed in a follow up commit introduced by #401.
Part of canonical/bundle-kubeflow#859
Part of #398
Manual testing
juju config istio-pilot default-gateway="some-name"
andjuju relate istio-pilot istio-ingressgateway
track/1.17