Created attachment 1208357 [details]
Upgrade logs files
Are the versions for the steps correct? It looks like you're using 3.3 installer to install 3.2 and then using the 3.2 installer to upgrade from 3.2 to 3.3.
There is a type error, OCP 3.2 are installed by atomic-openshift-utils-3.2.28 upgraded by atomic-openshift-utils-3.3.22.
I cannot reproduce with the steps above, however looking at the code triggering the error it looks like we can work past is as there's no longer any need to check for pacemaker cluster method as it's not supported.
I will remove everything related to pacemaker cluster restarts.
I think it is OK to remove pacemaker.
Openshift 3.3, it works
Openshift 3.2, The test failed for https://bugzilla.redhat.com/show_bug.cgi?id=1391805
Other issue is an ansible limitation with known workaround, see other bug for details, moving this one back ON_QA, should be able to be tested once that control path setting is adjusted.
The customer report similar bug with BZ1391805, the control path doesn't work. so block for testing.
https://bugzilla.redhat.com/show_bug.cgi?id=1392169 is now ON_QA
Both v3.2.1 and v3.3.1 upgrade failed.
No blocked bugs now. move to verified.
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.