Bug 1823338 - CSI pod logging- CSI driver built version should be the release version not canary
Summary: CSI pod logging- CSI driver built version should be the release version not c...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: build
Version: 4.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: OCS 4.4.0
Assignee: Boris Ranto
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-13 11:45 UTC by Neha Berry
Modified: 2020-09-23 09:05 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-04 12:54:39 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:2393 0 None None None 2020-06-04 12:54:53 UTC

Description Neha Berry 2020-04-13 11:45:04 UTC
CSI pod logging - CSI driver built version should be the release version not canary

Description of problem (please be detailed as possible and provide log
snippests):
-----------------------------------------------------------------------
As discussed & brought up by Madhu, it is observed that even in OCS 4.3, the CSI driver version mentioned in logs of csi-rbdplugin/csi-cephfsplugin plugin pods is "Canary" instead of the CSI release version

The same git version is present in OCS 4.2.0 (rc9), 4.2.3 and OCS 4.3 builds. 

1. Shouldn't the version be newer in later releases. 

2. Are we using older images of CSI even for latest OCS releases ?

3. Isn't the Downstream CSI image not using the latest CSI released version ?


------- Some snips of log for different OCS releases -----

>> OCS 4.3 stage build(to be GA'd) - Log location [1]
ocs-operator:	v4.3.0-407.ci


>> 2020-04-09T22:04:37.22451269+05:30 I0409 16:34:37.223989       1 cephcsi.go:113] Driver version: canary and Git version: b812ec26df5c7519c400aeba0d23339c618a550b


[1] http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/jnk-vu1rv33-t1/jnk-vu1rv33-t1_20200409T151828/logs/ocs-ci-logs-1586450541_ocs_logs/ocs_must_gather/quay-io-rhceph-dev-ocs-must-gather-sha256-a512e88410cadd6e4b286aca63b8917389dd73e8c202189563055c37f4c50fef/ceph/namespaces/openshift-storage/pods/

----------------------------------------

>> Same Driver version and Git  version is logged in OCS 4.2.3

name: ocs-operator.v4.2.3

>> 2020-04-02T18:01:58.197363981Z I0402 18:01:58.197256       1 cephcsi.go:104] Driver version: canary and Git version: b812ec26df5c7519c400aeba0d23339c618a550b



[2] - http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/pbalogh-live/pbalogh-live_20200402T132910/logs/failed_testcase_ocs_logs_1585851490/test_change_reclaim_policy_of_pv%5bCephBlockPool-Delete%5d_ocs_logs/ocs_must_gather/quay-io-rhceph-dev-ocs-must-gather-sha256-5bdbea059a9495e076bad9912bff45c87fa84d7efbe12d5a58a28c37a7b1ad75/ceph/namespaces/openshift-storage/pods/csi-rbdplugin-provisioner-745584dcf8-4688b/csi-rbdplugin/csi-rbdplugin/logs/current.log

----------------------------------------

>> Same Driver and Git version is logged in OCS 4.2.0 (rc9) build - e.g. Log [3]

OCS 4.2.0 rc9 - ocs-operator.v0.0.284

>>2020-01-02T09:18:26.105201497Z I0102 09:18:26.105086       1 cephcsi.go:104] Driver version: canary and Git version: b812ec26df5c7519c400aeba0d23339c618a550b

[3] - http://rhsqe-repo.lab.eng.blr.redhat.com/cns/ocs-qe-bugs/BZ-1787563/ocs-must-gather/must-gather.local.7732664234412975099/ceph/namespaces/openshift-storage/pods/csi-cephfsplugin-hr8h5/csi-cephfsplugin/csi-cephfsplugin/logs/current.log





Version of all relevant components (if applicable):
-----------------------------------------------------------------------
OCS 4.3 - ocs-operator:	v4.3.0-407.ci

This is true for all OCS 4.3 images received so far


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

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

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

Can this issue reproducible?
-----------------------------------------------------------------------
Yes

Can this issue reproduce from the UI?
-----------------------------------------------------------------------
Yes

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

Steps to Reproduce:
-----------------------------------------------------------------------
1. Install OCS 4.3
2. Check the Driver and Git Version in the CSI containers of csi-cephfsplugin-** and csi-rbdplugin-** pods(both provsioner and plugin pods)
3. Check that the Driver version in the logs is not Canary




Actual results:
-----------------------------------------------------------------------
The CSI version and git version is logged as canary and b812ec26df5c7519c400aeba0d23339c618a550b respectively in all OCS 4.x releases. There is no change to newer supported CSI driver and git versions




Expected results:
-----------------------------------------------------------------------
The Driver should point to released version of CSI instead of Canary.
Accordingly, the git version should also be correctly logged.

Additional info:
-----------------------------------------------------------------------

Comment 19 Raz Tamir 2020-04-23 05:09:01 UTC
acked

Comment 22 Michael Adam 2020-04-24 16:25:24 UTC
should be contained in 4.4.0-414.ci aka 4.4.0-rc2

Comment 26 errata-xmlrpc 2020-06-04 12:54:39 UTC
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:2393


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