Bug 1834934
Summary: | Upgrade from OCS-4.3 to OCS-4.4 failed | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jose A. Rivera <jarrpa> |
Component: | OLM | Assignee: | Vu Dinh <vdinh> |
OLM sub component: | OLM | QA Contact: | Jian Zhang <jiazha> |
Status: | CLOSED DUPLICATE | Docs Contact: | |
Severity: | urgent | ||
Priority: | high | CC: | assingh, branto, ebondare, ecordell, jarrpa, jcall, laparici, madam, nbecker, ocs-bugs, owasserm, pbalogh, ratamir, shmohan, sostapov, uchapaga |
Version: | 4.4 | Keywords: | Automation, Regression, Upgrades |
Target Milestone: | --- | ||
Target Release: | 4.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1823937 | Environment: | |
Last Closed: | 2020-05-21 13:58:37 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Comment 1
Petr Balogh
2020-05-12 19:00:05 UTC
Looks like upgrade started OK on OCP 4.3 but then we hit another noobaa related issue. But OLM started rolling upgrade of OCS fine in the job mentioned above. If someone is curious about must gather logs from OCP 4.3 execution they are here: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/jnk-ai3c33-ua/jnk-ai3c33-ua_20200512T181114/logs/failed_testcase_ocs_logs_1589311239/test_upgrade_ocs_logs/ We are looking at the issue on noobaa, however this is does prevent the progress on this BZ right ? fixing direction of BZ dependency.. ;-) Nimrod on OCP 4.4 we cannot even start upgrade cause of OLM issue. On OCP 4.3 the upgrade to OCS 4.4 will start OK, but then it's failing on noobaa BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1835125 So basically we cannot really confirm that upgrade working even on OCP 4.3. But actually without running any pre upgrade tests we passed the whole upgrade. *** This bug has been marked as a duplicate of bug 1834936 *** |