Description of problem: VS list shows only Persistent Volume claim as source and not volume snapshot content as source. Version-Release number of selected component (if applicable): How reproducible:1/1 Steps to Reproduce: 1. Create volume snapshot from Volume Snapshot Content 2. Go to List Page 3. Actual results: Doesn't show the source of Volume Snapshot Expected results: Should show the source of Volume Snapshot Fix: Rename the PVC column to source and use the relevant resource. Additional info:
The source field is not available and shows the correct source. Hence this bug is verified attached the screenshots of the post fix as attachment Steps to reproduce: 1. create a project, new app and a PVC to attach to a pod 2. create a volume snapshot class for the same provision-er as the PVC 3. create a volume snapshot for the above snap shot class Check that the volume snapshot details page shows the "source" field and it contains the PVC name. If the source is VSC then it should contain the VSC name.
(In reply to Siva Reddy from comment #2) > The source field is not available and shows the correct source. Hence this > bug is verified > attached the screenshots of the post fix as attachment > > Steps to reproduce: > 1. create a project, new app and a PVC to attach to a pod > 2. create a volume snapshot class for the same provision-er as the PVC > 3. create a volume snapshot for the above snap shot class > > Check that the volume snapshot details page shows the "source" field and > it contains the PVC name. If the source is VSC then it should contain the > VSC name. version 4.6.0-0.nightly-2020-09-21-230455 the bug is verified in
Created attachment 1715688 [details] The screenshot with the fix showing source field
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 (OpenShift Container Platform 4.6 GA Images), 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:4196