[RFE] export-bundle should have an option to export bundle with current machine code
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-
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.