The problem with this issue, that we have multiple clouds (from different customers) where we have to change the 'flavor' of machines on a more or less regular basis.
With flavor in this case it refers to the physical host being setup to use vnf / sriov / hugepages or not (or even a mix of these settings).
Since the 'name' used to identify the secret is derived from the juju application name, we got hit by this every time we 'remove' one juju application flavor and add the other, even while the ceph is the same, and thus the actual secret does not change, just the label.
Added field-medium to this ticket as the only 'work around' involves manually going to the machine and issuing some command to remove the secret, which all risks involved.
The problem with this issue, that we have multiple clouds (from different customers) where we have to change the 'flavor' of machines on a more or less regular basis.
With flavor in this case it refers to the physical host being setup to use vnf / sriov / hugepages or not (or even a mix of these settings).
Since the 'name' used to identify the secret is derived from the juju application name, we got hit by this every time we 'remove' one juju application flavor and add the other, even while the ceph is the same, and thus the actual secret does not change, just the label.
Added field-medium to this ticket as the only 'work around' involves manually going to the machine and issuing some command to remove the secret, which all risks involved.