Deploying charm using unsupported series does not error

Bug #1815097 reported by Tyler Treat
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Unassigned

Bug Description

I was attempting to deploy mysql (https://jujucharms.com/mysql/) but after running the deploy, the status remained on "waiting for machine." The machine message says: "no matching agent binaries available."

https://paste.ubuntu.com/p/rpzVRzgrwF/

It appears this is because the mysql charm uses an unsupported series (Zesty). It would be great if juju could notice if a charm is asking for an unsupported series and refuse to deploy or fall back to a different series which is supported.

Revision history for this message
Tyler Treat (tylertreat) wrote :

I think I've filed this with the wrong project. Where would be a more appropriate place to file this?

Revision history for this message
George Kraft (cynerva) wrote :
Revision history for this message
Cory Johns (johnsca) wrote :

Actually, while I agree that the mysql charm should be updated to correct the series, I think this issue as written would be better placed on the Juju project, as it would involve the Juju CLI or agent handling the request better.

affects: charm-gcp-integrator → juju
Revision history for this message
Cory Johns (johnsca) wrote :

TBH, I'm not sure how much better Juju could handle it, though, since it won't know until the point it queries simplestreams what series are supported. Maybe the client or controller could do a preliminary query to be able to fail fast.

Revision history for this message
Richard Harding (rharding) wrote :

We're working to define the full UX around unsupported series with the charmstore API teams as well as Juju. We agree that Juju should ERROR on deploy, however it should also allow you to override with the existing `deploy --force` command in cases of testing upgrade paths and such.

There's a mix of updated needed to handle this in the local charm case, charmstore case, and cases where the charm lists series and while the preferred series might be unsupported (as is the case with mysql) there are other valid series to select from.

Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.6-beta1
summary: - Deploying charm using unsupported series fails ungracefully
+ Deploying charm using unsupported series does not error
Changed in juju:
milestone: 2.6-beta1 → 2.6-beta2
Changed in juju:
milestone: 2.6-beta2 → 2.6-rc1
Changed in juju:
milestone: 2.6-rc1 → 2.6-rc2
Changed in juju:
milestone: 2.6-rc2 → 2.6.1
Changed in juju:
milestone: 2.6.1 → 2.6.2
Changed in juju:
milestone: 2.6.2 → 2.6.3
Changed in juju:
milestone: 2.6.3 → 2.6.4
Changed in juju:
milestone: 2.6.4 → 2.6.5
Changed in juju:
milestone: 2.6.5 → 2.6.6
Changed in juju:
milestone: 2.6.6 → 2.6.7
Revision history for this message
Richard Harding (rharding) wrote :

This has been updated in 2.6 and now provides better error messaging and hints for using outdated series. Marking this as fix-released.

Changed in juju:
status: Triaged → Fix Released
Revision history for this message
Anastasia (anastasia-macmood) wrote :

2.6.7 release never went out. This fix was instead released in 2.6.8 - re-targeting this report.

Changed in juju:
milestone: 2.6.7 → 2.6.8
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.