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 Dec 4, 2023. It is now read-only.
Describe the bug
When upgrading from EnMasse 0.30.z or older to 0.31.z or newer, and having an address space created via the service-broker, it was possible to specify a non-existing namespace for the service instance. If such an invalid address space have been created, the upgrade may fail with the address-space-controller not being able to convert an address space from the ConfigMap representation to the AddressSpace CRD representation due to conflict: already exists.
The text was updated successfully, but these errors were encountered:
lulf
changed the title
Upgrade to 0.31.X with address space created by service broker fails
Upgrade to 0.31.z with address space created by service broker in a non-existent namespace fails
Jun 9, 2020
lulf
added a commit
to lulf/enmasse
that referenced
this issue
Jun 9, 2020
Describe the bug
When upgrading from EnMasse 0.30.z or older to 0.31.z or newer, and having an address space created via the service-broker, it was possible to specify a non-existing namespace for the service instance. If such an invalid address space have been created, the upgrade may fail with the address-space-controller not being able to convert an address space from the ConfigMap representation to the AddressSpace CRD representation due to conflict: already exists.
The text was updated successfully, but these errors were encountered: