Bug 2269006 - After upgrade, noobaa-db-pg-0 is still using old image
Summary: After upgrade, noobaa-db-pg-0 is still using old image
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.15
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Jacky Albo
QA Contact: Vijay Avuthu
URL:
Whiteboard:
: 2269066 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-03-11 13:33 UTC by Vijay Avuthu
Modified: 2025-03-26 10:21 UTC (History)
13 users (show)

Fixed In Version: 4.16.0-39
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github noobaa noobaa-operator pull 1319 0 None Merged [DB Upgrade] Fixing returned status and adding prints 2024-03-17 08:56:42 UTC
Github noobaa noobaa-operator pull 1320 0 None Merged [Backport to 5.15] fixing returned status and adding prints 2024-03-17 08:56:42 UTC

Description Vijay Avuthu 2024-03-11 13:33:28 UTC
Description of problem (please be detailed as possible and provide log
snippests):

After upgrade from 4.14.5 to 4.15.0-157,  noobaa-db-pg-0 is still using old image
( CSV of 4.15.0-157 has different image )

Version of all relevant components (if applicable):
upgrade from 4.14.5 to 4.15.0-157

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1 

Can this issue reproducible?
Not seen on every upgrade, but jobs failed couple of times

Can this issue reproduce from the UI?
Not tried

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. upgrade from 4.14.5 to 4.15.0-157
2. check all the images in pods are upgraded according to CSV
3.


Actual results:

noobaa-db-pg-0 is still using old image instead of new one

Expected results:
container should use new one as mentioned in CSV


Additional info:

NAME                                    DISPLAY                       VERSION        REPLACES                                PHASE
mcg-operator.v4.15.0-rhodf              NooBaa Operator               4.15.0-rhodf   mcg-operator.v4.14.5-rhodf              Succeeded
ocs-operator.v4.15.0-rhodf              OpenShift Container Storage   4.15.0-rhodf   ocs-operator.v4.14.5-rhodf              Succeeded
odf-csi-addons-operator.v4.15.0-rhodf   CSI Addons                    4.15.0-rhodf   odf-csi-addons-operator.v4.14.5-rhodf   Succeeded
odf-operator.v4.15.0-rhodf              OpenShift Data Foundation     4.15.0-rhodf   odf-operator.v4.14.5-rhodf              Succeeded


2024-03-11 15:58:39  10:28:39 - MainThread - ocs_ci.utility.utils - INFO  - Executing command: oc --kubeconfig /home/jenkins/current-cluster-dir/openshift-cluster-dir/auth/kubeconfig -n openshift-storage get Pod noobaa-db-pg-0 -n openshift-storage -o yaml
2024-03-11 15:58:39  10:28:39 - MainThread - ocs_ci.ocs.resources.pod - WARNING  - Images: {'registry.redhat.io/rhel8/postgresql-12@sha256:493358aa1f1f9aa0862fca14e27f972f73a6356b5032fe3b372432f0b6db880a'} weren't upgraded in: noobaa-db-pg-0!


from CSV, image should be

- name: NOOBAA_DB_IMAGE
                  value: registry.redhat.io/rhel9/postgresql-15@sha256:76ff2541e3ff13b7f5feb1662597f33283bf9dc80e110bef2fb39633e8bbac00


job: https://url.corp.redhat.com/b4adae7
must gather: https://url.corp.redhat.com/8695878
csv yaml:  https://url.corp.redhat.com/0a1f8e2
pod yaml: https://url.corp.redhat.com/58faadf

Comment 4 Petr Balogh 2024-03-11 21:44:11 UTC
*** Bug 2269066 has been marked as a duplicate of this bug. ***

Comment 12 Tiffany Nguyen 2024-04-18 17:51:01 UTC
Had discussion with Vijay and this is a corner case issue. Assign to Vijay for verification.

Comment 28 Sunil Kumar Acharya 2024-09-17 10:05:02 UTC
Moving the non-blocker BZs out of ODF-4.17.0 as part of Development Freeze.


Note You need to log in before you can comment on or make changes to this bug.