Closed filidav closed 6 years ago
A little more context would help before we start looking into this. The only thing I understood is that the service instance is on "forced" enrolment. What exactly did you do prior to deleting the app?
We have autosleep enabled only for a SANDBOX org. I have been seeing this issue when developers try to delete apps that are not even in the SANDBOX org when they try to delete The only way around this error is cf purge-instance-service and then delete the app.
@filidav I suggest you provide traces of the CF CLI command while doing the cf delete app
using the CF_TRACE=true environment variable, along with logs of the autosleep service broker app. This will help us understand the issue you're facing and try to provide some help.
When we get the next incident I will get the details.
Thank you
David Filippelli
On Oct 4, 2017, at 3:02 AM, Guillaume Berche notifications@github.com<mailto:notifications@github.com> wrote:
@filidavhttps://github.com/filidav I suggest you provide traces of the CF CLI command while doing the cf delete app using the CF_TRACE=true environment variable, along with logs of the autosleep service broker apphttps://github.com/cloudfoundry-community/autosleep/blob/develop/doc/publish.md#deploy-autosleep-app
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/cloudfoundry-community/autosleep/issues/282#issuecomment-334067143, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AWJsOivBovjRuMgulm8fVl9QyK6j5Pksks5soy19gaJpZM4PsrJw.
STATEMENT OF CONFIDENTIALITY The information contained in this email message and any attachments may be confidential and legally privileged and is intended for the use of the addressee(s) only. If you are not an intended recipient, please: (1) notify me immediately by replying to this message; (2) do not use, disseminate, distribute or reproduce any part of the message or any attachment; and (3) destroy all copies of this message and any attachments.
Closing for now until additional diagnostics get provided. @filidav please reopen the issue when you manage to reproduce
Really delete the app onboard-service-dev?> yes Deleting app onboard-service-dev in org / space as ...
FAILED
Server error, status code: 500, error code: 10011, message: Database error
The only way to get around this is take autosleep out of force enrollment mode , delete the app, then put it back in force enrollment. Or Purge the service.