Bug 1967435
| Summary: | noobaa-core-0 core image didn't get upgraded when upgrading OCS from 4.7 to 4.8 | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Petr Balogh <pbalogh> |
| Component: | Multi-Cloud Object Gateway | Assignee: | Liran Mauda <lmauda> |
| Status: | CLOSED WORKSFORME | QA Contact: | Petr Balogh <pbalogh> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.8 | CC: | ebenahar, etamir, nbecker, ocs-bugs, odf-bz-bot, ratamir |
| Target Milestone: | --- | Keywords: | Automation |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-07-12 14:03:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Petr Balogh
2021-06-03 07:18:05 UTC
Trying to reproduce it here: https://ocs4-jenkins-csb-ocsqe.apps.ocp4.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/1011/console This job will pause before teardown. In the execution: https://ocs4-jenkins-csb-ocsqe.apps.ocp4.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/1011/consoleFull it wasn't reproduced as I see we are running now tier1 after upgrade + from console output I see: 18:44:11 - MainThread - ocs_ci.ocs.ocp - INFO - All the images: {'core': 'quay.io/rhceph-dev/mcg-core@sha256:68832b8afaf01e49f418e67cec1e3def3a86cd967f8ea6fa4728045484cfd69f'} were successfully upgraded in: noobaa-core-0! 18:44:11 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n openshift-storage get Pod noobaa-db-pg-0 -n openshift-storage -o yaml 18:44:16 - MainThread - ocs_ci.ocs.ocp - INFO - All the images: {'db': 'registry.redhat.io/rhel8/postgresql-12@sha256:03a1e02a1b3245f9aa0ddd3f7507b915a8f7387a1674969f6ef039a5d7fd8bf0', 'init': 'quay.io/rhceph-dev/mcg-core@sha256:68832b8afaf01e49f418e67cec1e3def3a86cd967f8ea6fa4728045484cfd69f'} were successfully upgraded in: noobaa-db-pg-0! 18:44:16 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n openshift-storage get Pod noobaa-endpoint-74c8949cf8-pwf8r -n openshift-storage -o yaml 18:44:21 - MainThread - ocs_ci.ocs.ocp - INFO - All the images: {'endpoint': 'quay.io/rhceph-dev/mcg-core@sha256:68832b8afaf01e49f418e67cec1e3def3a86cd967f8ea6fa4728045484cfd69f'} were successfully upgraded in: noobaa-endpoint-74c8949cf8-pwf8r! 18:44:21 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n openshift-storage get Pod noobaa-operator-864dbcf7bb-w922v -n openshift-storage -o yaml 18:44:27 - MainThread - ocs_ci.ocs.ocp - INFO - All the images: {'noobaa_cor': 'quay.io/rhceph-dev/mcg-core@sha256:68832b8afaf01e49f418e67cec1e3def3a86cd967f8ea6fa4728045484cfd69f', 'noobaa_db': 'registry.redhat.io/rhel8/postgresql-12@sha256:03a1e02a1b3245f9aa0ddd3f7507b915a8f7387a1674969f6ef039a5d7fd8bf0', 'noobaa-operator': 'quay.io/rhceph-dev/mcg-operator@sha256:f73d206c0e206ca9d83bd90d0a9c37a580bf94aca5819cba431876ad8f549e6c'} were successfully upgraded in: noobaa-operator-864dbcf7bb-w922v! We had more executions, for example this one: https://ocs4-jenkins-csb-ocsqe.apps.ocp4.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/1372/ From this production job: https://ocs4-jenkins-csb-ocsqe.apps.ocp4.prod.psi.redhat.com/job/qe-trigger-aws-ipi-fips-encryption-3az-rhcos-3m-3w-3i-upgrade-ocs-auto/18/ This has passed upgrade stage and now running tier1 after upgrade which is still progressing. So we didn't hit this issue again yet. |