Description of problem: openstack overcloud status shows an ugly exception when plan name is different than overcloud: (undercloud) [stack@undercloud-0 ~]$ openstack overcloud status The action raised an exception [action_ex_id=dcb2c62a-7a26-40b3-9f4b-b8166f371701, action_cls='<class 'mistral.actions.action_factory.SwiftAction'>', attributes='{u'client_method_name': u'get_object'}', params='{u'obj': u'deployment_status.yaml', u'container': u'overcloud-messages'}'] SwiftAction.get_object failed: Object GET failed: https://192.168.24.2:13808/v1/AUTH_c3687695ddbf40e9b5a574a99ca27d02/overcloud-messages/deployment_status.yaml 404 Not Found [first 60 chars of response] <html><h1>Not Found</h1><p>The resource could not be found.< Exception getting deployment status: The action raised an exception [action_ex_id=dcb2c62a-7a26-40b3-9f4b-b8166f371701, action_cls='<class 'mistral.actions.action_factory.SwiftAction'>', attributes='{u'client_method_name': u'get_object'}', params='{u'obj': u'deployment_status.yaml', u'container': u'overcloud-messages'}'] SwiftAction.get_object failed: Object GET failed: https://192.168.24.2:13808/v1/AUTH_c3687695ddbf40e9b5a574a99ca27d02/overcloud-messages/deployment_status.yaml 404 Not Found [first 60 chars of response] <html><h1>Not Found</h1><p>The resource could not be found.< (undercloud) [stack@undercloud-0 ~]$ (undercloud) [stack@undercloud-0 ~]$ openstack overcloud plan list +-----------+ | Plan Name | +-----------+ | openshift | +-----------+ Version-Release number of selected component (if applicable): openstack-tripleo-common-9.3.1-0.20180920204841.18ea890.el7ost.noarch python2-tripleo-common-9.3.1-0.20180920204841.18ea890.el7ost.noarch openstack-tripleo-common-containers-9.3.1-0.20180920204841.18ea890.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Run 'openstack overcloud status' when a plan different than 'overcloud' exists Actual results: An ugly exception is printed. Expected results: We should show a human readable message such as: "No 'overcloud' plan exists' Additional info:
*** This bug has been marked as a duplicate of bug 1624464 ***