You are right, attach-storage does not perform the same AZ validation as does deploy. This is actually an attach-storage bug. The Juju model does currently require any volume AZ matches that of the machine to which it is attached, otherwise things can break.
Is there any way to adjust the AZ reported by the storage? If the Juju modelling bug is fixed, the work around will break. Or we'd need to add an option to ignore AZ mismatches or something.
You are right, attach-storage does not perform the same AZ validation as does deploy. This is actually an attach-storage bug. The Juju model does currently require any volume AZ matches that of the machine to which it is attached, otherwise things can break.
Is there any way to adjust the AZ reported by the storage? If the Juju modelling bug is fixed, the work around will break. Or we'd need to add an option to ignore AZ mismatches or something.