Bug 1826477

Summary: Can see snapshot option, but feature moved to 4.6
Product: OpenShift Container Platform Reporter: Kanika Murarka <kmurarka>
Component: Console Storage PluginAssignee: Kanika Murarka <kmurarka>
Status: CLOSED ERRATA QA Contact: Oded <oviner>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, ebenahar, nthomas
Target Milestone: ---   
Target Release: 4.5.0   
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: 2020-07-13 17:29:56 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:
Bug Depends On:    
Bug Blocks: 1811545    
Attachments:
Description Flags
pvc_snapshot none

Description Kanika Murarka 2020-04-21 18:42:34 UTC
Description of problem:
User able to see snapshot option for PVC's but the snapshot feature has been shifted to 4.5 release

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Go to PVC listing page
2. Click on PVC and go to PVC details page
3. Click Volume snasphots

Actual results:
Able to see create volumesnapshot option

Expected results:
Shouldnt see create snapshot option

Additional info:

Comment 3 Kanika Murarka 2020-05-14 10:45:17 UTC
*** Bug 1810642 has been marked as a duplicate of this bug. ***

Comment 4 Oded 2020-05-24 17:39:21 UTC
Bug Not Reconstructed

Setup:
Provider:AWS
OCP Version:4.5.0-0.nightly-2020-05-24-072501
OCS Version:ocs-operator.v4.5.0-433.ci


Steps to Reproduce:
1.Go to "Storage"-> "Persistent Volume Claims"
2.Click on PVC and go to PVC details page
3.No option to create snapshot 
*Attached Screen shot

Comment 5 Oded 2020-05-24 17:40:47 UTC
Created attachment 1691605 [details]
pvc_snapshot

Comment 6 errata-xmlrpc 2020-07-13 17:29:56 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:2409