-
Notifications
You must be signed in to change notification settings - Fork 1
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
get-last-operation indefinidely returns error if broker is restarted during service provisionning #7
Comments
Associated symptom
To get traces of the associated service instance guid:
Check the restart history of the broker
|
gberche-orange
changed the title
osb-cmdb is not complying to 12 factors apps: breaks if restarts during service provisionning
osb-cmdb is not complying to 12 factors apps: get-last-operation returns error if restarted during service provisionning
Feb 20, 2020
gberche-orange
changed the title
osb-cmdb is not complying to 12 factors apps: get-last-operation returns error if restarted during service provisionning
get-last-operation indefinidely returns error if broker is restarted during service provisionning
Feb 20, 2020
fixed in v1.0.0: osb-cmdb now relying of osb api operation state to maintain it state, and does not maintain state in the broker RAM anymore. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
As an osb-cmdb operator, in order to operate osb-cmdb onto cloudfoundry without causing downtime, I need osb-cmdb to preserve service during diego cells evacuations
Observed behavior
osb-cmdb is not complying to 12 factors apps:
Following a restart of osb-cmdb, async service provisionning hangs/fails
get last operation
systematically returns an error (presumably 500 status code)Root cause
get last operation
returns the content of theInMemoryServiceInstanceStateRepository
which was clear during last broker restartPossible fixes
ServiceInstanceStateRepository
implementation (e.g. using a mysql database) instead ofInMemoryServiceInstanceStateRepository
get last operation
to lookup the status of the backing service instance(s) (along with possible backing application(s))Workaround
cf curl -X DELETE v2/service_instances/a005a22e-3684-423a-ad25-c5ad63ce0ca1
Affected release
Reproduced on version x.y
-->
The text was updated successfully, but these errors were encountered: