Skip to content
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.

Upgrade to 0.31.z with address space created by service broker in a non-existent namespace fails #4705

Closed
lulf opened this issue Jun 9, 2020 · 0 comments · Fixed by #4710
Labels

Comments

@lulf
Copy link
Member

lulf commented 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.

image

@lulf lulf added the kind/bug label Jun 9, 2020
@lulf 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
@lulf lulf closed this as completed in #4710 Jun 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant