export-bundle on model with single-space binding does not contain bindings

[Drew Freiberger]

I'm working in an environment running juju models and controllers on 2.9.9 and using the snapped juju client version 2.9.17, I'm experiencing an unexpected result when exporting bundles.

In my openstack model which has applications binding to multiple spaces, I see "bindings:" sections for each of the applications when I run "juju export-bundle".

However, in my LMA model, where each application only binds all interfaces to oam-space, there are no "bindings:" sections when I run "juju export-bundle".

If I deploy a new application, or add a second space binding to an existing application, with a binding other than the single oam-space binding, I get "bindings:" in the resulting "juju export-bundle" output.

The machines in the bundle without bindings: do list "constraints: spaces=oam-space" as part of the bundle, so we can infer from that which space is present/configured, but it would be nice for all exported bundles in a space-aware cloud to contain bindings info for visibility and modification by the operator.

[Drew Freiberger (afreiberger)]

Perhaps the logic which is simplifying the bundle if there is only one space could have an override with a flag to explicitly include bindings.