The DCOS CLI tests are failing due to a 409 error returned from "POST /v2/apps" with the message "App is locked by one or more deployments. Override with the option '?force=true'. View details at '/v2/deployments/<DEPLOYMENT_ID>'"
AFAICT, this endpoint should never return such a message. If the app already exists, I've seen it return a 409 with an "already exists" message, but not an "app locked" message.
The CLI test runs `dcos package install helloworld`, which calls "POST /v2/apps" on the helloworld app, and fails (non-deterministically). There is no existing helloworld app at the time it runs, but the previous test does install and remove helloworld. Maybe those two operations aren't being serialized properly?
The relevant part of the log is in the attached part.txt. The log from the entire CLI test suite is in complete.txt. See line 90 of part.txt for the 409 response.
Edit: Given Matthias' explanation that this is expected behavior, I think the only action item here is documentation.