Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1382936 - upgrade failed for single master
upgrade failed for single master
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Upgrade (Show other bugs)
3.3.0
Unspecified Unspecified
unspecified Severity medium
: ---
: 3.3.1
Assigned To: Devan Goodwin
Anping Li
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2016-10-08 11:05 EDT by Anping Li
Modified: 2017-04-14 04:42 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-15 14:09:48 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Upgrade logs files (45.61 KB, application/x-gzip)
2016-10-08 11:07 EDT, Anping Li 		no flags Details
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2778 normal SHIPPED_LIVE Moderate: atomic-openshift-utils security and bug fix update 2016-11-15 19:08:29 EST

  None (edit)
Comment 1 Anping Li 2016-10-08 11:07 EDT 
Created attachment 1208357 [details]
Upgrade logs files
Comment 2 Scott Dodson 2016-10-11 11:17:10 EDT 
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.
Comment 3 Anping Li 2016-10-13 06:43:20 EDT 
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.
Comment 4 Devan Goodwin 2016-10-19 14:16:07 EDT 
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.
Comment 6 Anping Li 2016-10-31 21:11:36 EDT 
I  think it is OK to remove pacemaker.
Comment 8 Anping Li 2016-11-04 02:22:11 EDT 
Openshift 3.3, it works
Openshift 3.2, The test failed for https://bugzilla.redhat.com/show_bug.cgi?id=1391805
Comment 9 Devan Goodwin 2016-11-04 07:53:23 EDT 
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.
Comment 10 Anping Li 2016-11-07 04:22:28 EST 
The customer report similar bug with BZ1391805, the control path doesn't work. so block for testing.
Comment 11 Devan Goodwin 2016-11-09 13:21:06 EST 
https://bugzilla.redhat.com/show_bug.cgi?id=1392169 is now ON_QA
Comment 12 Anping Li 2016-11-10 01:38:44 EST 
Both v3.2.1 and v3.3.1 upgrade failed.
https://bugzilla.redhat.com/show_bug.cgi?id=1393663
https://bugzilla.redhat.com/show_bug.cgi?id=1393662
Comment 14 Anping Li 2016-11-15 02:13:08 EST 
No blocked bugs now. move to verified.
Comment 15 errata-xmlrpc 2016-11-15 14:09:48 EST 
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/RHSA-2016:2778
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.