"cf disable-diego" for Docker app results in confusing error message

[jochenehret]

Hi Diego developers,

when we push a Docker app to Diego and then call cf disable-diego <appname>, we get a confusing error message and the app status is inconsistent:

$ cf disable-diego lattice-app
Setting lattice-app Diego support to false
FAILED
Error: CF-AppPackageNotFound - The app package could not be found: 92e75ab6-d631-4069-9fb5-c6cd1dfedd6a
{
   "code": 150002,
   "description": "The app package could not be found: 92e75ab6-d631-4069-9fb5-c6cd1dfedd6a",
   "error_code": "CF-AppPackageNotFound"
}

The app is not listed in cf diego-apps any more, but still running. The status is inconsistent:

$ cf apps
Getting apps in org test / space diego-test as admin...
OK

name           requested state   instances   memory   disk   urls
lattice-app    started           ?/1         1G       1G     lattice-app.cfapps.hcp-dev04.aws.sapcloud.io

I know that it doesn't make sense to disable Diego for Docker apps, but can you still try to provide a better error message?

Thanks and Best Regards,

Jochen.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/130622989

The labels on this github issue will be updated when the story is started.

[emalm]

Hi, @jochenehret,

Thanks for the report. That experience does sound confusing. As it turns out, all of those errors originate in either Cloud Controller or the CC-Bridge components, all of which reside in the CF CAPI team's capi-release. Consequently, I've copied your issue to cloudfoundry/capi-release#28 instead, and I'll close this issue out as migrated to that one.

Best,
Eric, CF Runtime Diego PM

[jochenehret]

Thanks Eric for taking care of that issue!