Upgrading NooBaa core container with CVE fixes and bumping the version with minor fixes.
Prasanth, can you please ack?
(In reply to Eran Tamir from comment #1) > Prasanth, can you please ack? done
Testing has been completed and marking this BZ as Verified. ############ [root@dhcp46-122 ~]# oc get pods NAME READY STATUS RESTARTS AGE noobaa-core-0 2/2 Running 1 5h noobaa-operator-778bd5cdb8-7s2p5 1/1 Running 0 5h testme-noobaa-noobaa-0 1/1 Running 0 3h testme-noobaa-noobaa-1 1/1 Running 0 3h testme-noobaa-noobaa-2 1/1 Running 0 3h [root@dhcp46-122 ~]# oc rsh noobaa-operator-778bd5cdb8-7s2p5 Defaulting container name to core. Use 'oc describe pod/noobaa-core-0 -n demo' to see all of the containers in this pod. sh-4.4$ rpm -qa |grep sqlite sqlite-libs-3.26.0-4.el8_1.x86_64 sh-4.4$ rpm -qa |grep libarchive libarchive-3.3.2-8.el8_1.x86_64 sh-4.4$ ############
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/RHBA-2020:0625