juju deploy not respecting default-series

Bug #1663510 reported by Alberto Donato
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Eric Claude Jones

Bug Description

In a model with default-series: xenial I deployed a multiseries charm as:

juju deploy ./xenial/prometheus

This gives me a trusty unit. I noticed that the charm defines trusty first:

"series":
- "trusty"
- "xenial"

and it seems that juju is using the first option rather than matching default-series.

If I specify --series xenial on the deploy command, it works.

I think it should use the default-series value, if the charm supports that series.

Tags: charm charmers
Revision history for this message
Anastasia (anastasia-macmood) wrote :

@Alberto,

Could you please clarify what Juju version you've used?

Changed in juju:
status: New → Incomplete
Revision history for this message
Alberto Donato (ack) wrote :

@Anastasia,

I don't remember what version was it initially, but I still see this behavior with 2.1.1.

Changed in juju:
status: Incomplete → New
Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.2.0
tags: added: charm charmers
Changed in juju:
milestone: 2.2-beta2 → 2.2-beta3
Revision history for this message
John A Meinel (jameinel) wrote :

I don't think this is a duplicate, but an orthogonal request. He wants the order of precedence to be:
  juju deploy --series=Y
  juju model-config default-series=X
  juju deploy [series from the charm]

Right now, I believe for charms that are *not* multi-series, we lookup what charm to deploy based on model-config. (so if you do 'juju deploy mysql' if that was not a multi-series charm, then we would find 'default-series' and use that to try and find eg trusty/mysql or xenial/mysql.)

 bug #1673122 is more about 'juju upgrade-charm' not respecting the series of the already running application. (and not supporting --series, but as we would only let you set it to the value of the application running, we shouldn't require you to do that.)

I think its fine if we address both bugs at the same time, but they are fairly different. (one is changing upgrade-charm code, and one is changing deploy/find-default-series code.)

Changed in juju:
assignee: nobody → Eric Claude Jones (ecjones)
Revision history for this message
Anastasia (anastasia-macmood) wrote :

PR against develop (2.2): https://github.com/juju/juju/pull/7245

Changed in juju:
status: Triaged → In Progress
Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
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.