Bug 1837934

Summary: PV-pool yaml is missing requested storage when created from UI
Product: OpenShift Container Platform Reporter: Afreen <afrahman>
Component: Console Storage PluginAssignee: Bipul Adhikari <badhikar>
Status: CLOSED ERRATA QA Contact: Ankush Behl <anbehl>
Severity: high Docs Contact:
Priority: high    
Version: 4.5CC: anbehl, aos-bugs, 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:
: 1837995 (view as bug list) Environment:
Last Closed: 2020-07-13 17:40:28 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1837995, 1838420    
Attachments:
Description Flags
Backing store for default size none

Description Afreen 2020-05-20 08:39:56 UTC 
Description of problem:
PV-pool yaml is missing requested storage when created from UI

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

How reproducible:
Install OCS operator on OCP

Steps to Reproduce:
1.Go to OCS operator
2.Click on backing store
3.Select provider as PVC.
4.Enter the size
5.Check yaml

Actual results:
The PV-pool yaml is missing the storage size mentioned on form

Expected results:
The PV pool form must reflect the requested storage in yaml and pass it to the operator.

Additional info:
Comment 3 Ankush Behl 2020-05-21 07:47:09 UTC 
Created attachment 1690543 [details]
Backing store for default size
Comment 5 Ankush Behl 2020-05-27 10:58:37 UTC 
Verified. The request is coming properly now.

```
spec:
  pvPool:
    numVolumes: 1
    resources:
      requests:
        storage: 50Gi
    storageClass: gp2
  ssl: false
  type: pv-pool
```

OpenShift Version: 4.5.0-0.nightly-2020-05-27-000432
Kubernetes Version: v1.18.2+9835af5
Comment 6 errata-xmlrpc 2020-07-13 17:40:28 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