Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix issue #356 #357

Merged
merged 0 commits into from
Jan 27, 2021
Merged

Fix issue #356 #357

merged 0 commits into from
Jan 27, 2021

Conversation

gberche-orange
Copy link
Member

@gberche-orange gberche-orange commented Jan 27, 2021

Now rejects update requests when the corresponding deployment is missing enable-deployment.yml marker.

cf update-service gberche-noop-x-osb-cmddb --upgrade
You are about to update gberche-noop-x-osb-cmddb.
Warning: This operation may be long running and will block further operations on the service until complete.
Really update service gberche-noop-x-osb-cmddb? [yN]: y
Updating service instance gberche-noop-x-osb-cmddb as gberche...
Service broker error: CF-ServiceBrokerRequestRejected(10001): Service broker error: Service instance does not exist: id=ba567621-3edb-4980-a498-9e204fab9ace
FAILED

and prints the following trace to hint operators

   2021-01-27T09:10:08.92+0100 [APP/PROC/WEB/0] OUT 2021-01-27 08:10:08.928  WARN 14 --- [nio-8080-exec-5] c.o.o.c.b.o.o.pipeline.BoshProcessor     : Enable-deployment is missing while receiving a request to update instance ba567621-3edb-4980-a498-9e204fab9ace Suspecting inconsistency from OSB client and COA deployment. Please check if manual cleanup was performed on coa deployments without going through CF (OSB client)

@gberche-orange gberche-orange merged this pull request into develop Jan 27, 2021
gberche-orange added a commit that referenced this pull request Apr 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant