For one reason or another, I sometimes run into the following error when trying to deploy an OpenStack TripleO overcloud in my lab:
ClientException: Object GET failed: https://192.0.2.2:13808/v1 /AUTH_1a5df8c242d848e8b01b974a72afcf8c /overcloud/plan-environment.yaml 404 Not Found
This usually occurs after impatiently cancelling an overcloud deployment – strongly not recommended of course. The overcloud plan, which is stored in a Swift container, is left missing one or more objects.
Given that Mistral (OpenStack’s workflow service) is meant to first delete the existing plan before continuing, it’s an odd error. The solution, it turns out, is not quite as straight forward as manually deleting the plan.