You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2021. It is now read-only.
If a failure happens during or after sending the bundle to Juju, there may be machines running and cloud resources being used. Depending on the particular failure, the cluster may even be in a functional state. At the very least, conjure-up should point the user at conjure-down to ensure that unused resources are cleaned up.
I'd recommend having the general error handler check conjureup.events.Bootstrapped.is_set() and add a standard addendum to the error indicating that cloud resources may be being used and to use conjure-down to clean up any failed deployments.
The text was updated successfully, but these errors were encountered:
johnsca
changed the title
Failures after deploy should inform that cluster may be running
Failures after deploy should inform that cloud resources may be used
Jun 27, 2018
If a failure happens during or after sending the bundle to Juju, there may be machines running and cloud resources being used. Depending on the particular failure, the cluster may even be in a functional state. At the very least, conjure-up should point the user at
conjure-down
to ensure that unused resources are cleaned up.I'd recommend having the general error handler check
conjureup.events.Bootstrapped.is_set()
and add a standard addendum to the error indicating that cloud resources may be being used and to useconjure-down
to clean up any failed deployments.The text was updated successfully, but these errors were encountered: