[RFE] export-bundle should have an option to export bundle with current machine code

Bug #1865550 reported by Pedro Guimarães
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

Hi,

Juju 2.7.0

We are running a change with Juju on a live cloud and we are seeing that following the procedure:

(1) export bundle from UI
(2) change the bundle (45 machines exported, from 0 to 44)
(3) juju deploy bundle.yaml --dry-run

It will complain that juju has machines like "machine #180" because, actually that machine had been removed and readded during cloud life-cycle, but it corresponds to one of the machines ranging from 0 to 44 on the exported bundle.

Juju should have a native way to route it back between a recently exported bundle and actual juju status.

My suggestion: export-bundle and exported bundles from UI should have the machine-id at the moment, not the original bundle's machine-id.

Otherwise I need to run:

juju deploy my-recent-exported-bundle.yaml --map-machines=<ALL_THE_MACHINES_REMAPPED>

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

Thanks, I can see a case for a known environment wanting something like a --keep-machine-nums or something that would have it specific setup.

I do argue that we're abusing the bundles in this way to handle changes and I think it's a gap that we should fill in a better way.

Changed in juju:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Pedro Guimarães (pguimaraes) wrote :

Hi rharding, yes I don't think that is 100% of the cases. Some times we just want to recover the original bundle to deploy somewhere else.

This case fits an operational task of running a big replacement, which cannot be easily done with charms (upgrade, configs, actions, etc). The real example I have: removing a charm that upgrade-charm functionality is broken or does not exist. Remove it and reinstall the newest (fixed) charm.

The easiest way would be: (1) pull the bundle with actual machine-ids; (2) remove the old charm; (3) change the bundle to have the new charm version; and (4) redeploy with that bundle.

Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Wishlist → Low
tags: added: expirebugs-bot
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.