Placement directive for a MAAS system id does not work in a bundle

Bug #1989484 reported by Peter Matulis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
High
Unassigned

Bug Description

This works:

$ juju deploy --to system-id=e4dx7e --channel yoga/stable ch:nova-compute

But this does not:

$ juju deploy ./bundle.yaml

Where bundle.yaml contains:

===

applications:

  nova-compute:
    charm: ch:nova-compute
    channel: yoga/stable
    num_units: 1
    to: system-id=e4dx7e

===

Output:

ERROR cannot deploy bundle: the provided bundle has the following errors:
at least one application must be specified

If I remove the placement directive line ('to: system-id=e4dx7e') then Juju accepts the bundle.

Revision history for this message
Ian Booth (wallyworld) wrote :

Looks like different placement parsing apis are used depending on if it's a bundle or the CLI. This seems wrong to me.

Revision history for this message
Ian Booth (wallyworld) wrote :

I think the bundle version is restricted to specifying placement with a given application rather than the more general option allowed via the CLI.

Changed in juju:
milestone: none → 2.9.35
importance: Undecided → High
status: New → Triaged
Changed in juju:
milestone: 2.9.35 → 2.9.36
Changed in juju:
milestone: 2.9.36 → 2.9.37
Changed in juju:
milestone: 2.9.37 → 2.9.38
Changed in juju:
milestone: 2.9.38 → 2.9.39
Revision history for this message
Juan M. Tirado (tiradojm) wrote :

Could we confirm this still happens on 2.9.38?

Changed in juju:
milestone: 2.9.39 → 2.9.40
Changed in juju:
milestone: 2.9.40 → 2.9.41
Changed in juju:
milestone: 2.9.41 → 2.9.42
Changed in juju:
milestone: 2.9.42 → 2.9.43
Changed in juju:
milestone: 2.9.43 → 2.9.44
Changed in juju:
milestone: 2.9.44 → 2.9.45
Changed in juju:
milestone: 2.9.45 → 2.9.46
Revision history for this message
Ian Booth (wallyworld) wrote :

The next 2.9.46 candidate release will not include a fix for this bug and we don't plan on any more 2.9 releases. As such it is being removed from its 2.9 milestone.

If the bug is still important to you, let us know and we can consider it for inclusion on a 3.x milestone.

tags: added: bundles maas-provider
Changed in juju:
milestone: 2.9.46 → none
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.