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

fix: supported series computation needed for juju 3.6 #1170

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

dimaqq
Copy link
Contributor

@dimaqq dimaqq commented Oct 18, 2024

Covered by existing integration tests

@dimaqq
Copy link
Contributor Author

dimaqq commented Oct 21, 2024

Fixes #1171


# use the charm default
if requested_series == '':
return supported_series[-1]
Copy link
Member

@SimonRichardson SimonRichardson Oct 21, 2024

Choose a reason for hiding this comment

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

This was incorrect. It should have been 0. So your change is correct.

https://github.com/juju/charm/blob/bd9cd4649313dc47c456713e33543c957ce1eaad/charm.go#L126-L129

@dimaqq
Copy link
Contributor Author

dimaqq commented Oct 22, 2024

The naive change is not enough: https://github.com/juju/python-libjuju/actions/runs/11454556295/job/31869929957?pr=1175

test tried to deploy keystone victoria/stable

  • ResolveCharms(ch:keystone, track: victoria, risk: stable) --> 'url': 'ch:amd64/keystone-690', 'supported-series': ['focal']
  • AddCharmCharm("url": "ch:amd64/jammy/keystone-690", "channel": "22.04/stable") --> OK
    • client is already wrong, it ignores supported-series
    • Juju accepted AddCharm even though rev 690 doesn't support jammy
  • DeployFromRepository(...) --> base "[email protected]/stable" is not supported, supported bases are: [email protected]

@dimaqq dimaqq marked this pull request as draft October 24, 2024 03:21
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