Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1688726 - [Kubevirt-Foreman] The entry for PVC claim in list for new host shows all PVC
Summary: [Kubevirt-Foreman] The entry for PVC claim in list for new host shows all PVC
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Compute Resources - CNV
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Moti Asayag
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-14 10:26 UTC by Vatsal Parekh
Modified: 2019-04-01 08:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-01 08:53:01 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Vatsal Parekh 2019-03-14 10:26:11 UTC
Description of problem:
List PVC shown when creating a new host along side the option to create a new claim contains the list of all PVC regardless if they're already bound to a VM.
While this detail is not available on the PVC, but we can look into VMI/VM spec.volume to see consumed PVC and get a list of PVC to not show.

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

How reproducible:


Steps to Reproduce:
1.Go to create a new host
2.Select Kubevirt compute resource as host to provision
3.Go to storage part under Virtual Machine

Actual results:


Expected results:
Should show only non-used PVCs

Additional info:

Comment 3 Moti Asayag 2019-04-01 08:53:01 UTC
Instead of relying on an existing PVC for static provision, the storage selection will be based on storage class.
Therefore there will be no list of PVCs, hence this bug is no longer relevant.


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