Started with a 1 controller, 1 compute deployment, virt environment without network isolation. I ran the following but the stack update eventually failed: openstack overcloud deploy --plan-uuid 3b7779f5-8206-4913-909e-eb6e1e9d9f63 --control-scale 3 --ceph-storage-scale 1 Attaching the output of heat deployment-show.
Created attachment 1052106 [details] heat deployment-show output
This failure doesn't seem to have the AttributeError failure. Rather, looks like a pacemaker issue. "Error: cluster is not currently running on this node" is in the puppet log you attached. Also, I think --plan-uuid is deprecated in favor of --plan, but I'm not certain.
(In reply to Ryan Brown from comment #8) > This failure doesn't seem to have the AttributeError failure. Rather, looks > like a pacemaker issue. "Error: cluster is not currently running on this > node" is in the puppet log you attached. So this is a different issue and should be filed separately. Moving back to ON_QA > > Also, I think --plan-uuid is deprecated in favor of --plan, but I'm not > certain. Yes, but it still works (until the next puddle)
You are right, this is different issue than the one reported initially in this bug. I'm going to close this and open another one for the new issue. Thanks.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2015:1549