Bug 1703009 - VM associated PVC errors does not show in VM events
Summary: VM associated PVC errors does not show in VM events
Keywords:
Status: CLOSED DUPLICATE of bug 1669163
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 2.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: ---
Assignee: Tomas Jelinek
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-25 10:02 UTC by Guohua Ouyang
Modified: 2019-04-25 22:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-25 22:42:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
vm_events (32.29 KB, image/png)
2019-04-25 10:02 UTC, Guohua Ouyang
no flags Details
home-events (83.39 KB, image/png)
2019-04-25 10:02 UTC, Guohua Ouyang
no flags Details

Description Guohua Ouyang 2019-04-25 10:02:11 UTC
Created attachment 1558593 [details]
vm_events

Description of problem:
Create a VM from cloned disk, once it fails to create volume, the event like "Failed to provision volume with StorageClass "glusterfs-storage": failed to create volume: failed to create volume: Failed to allocate new volume: No space" only available in Home -> Events, not available in VM Events tab.

Version-Release number of selected component (if applicable):
kubevirt-web-ui:v2.0.0-13

How reproducible:
100%

Steps to Reproduce:
1. upload a vm image via virtctl and make its size large
2. create a vm from cloned disk by attached this pvc in the wizard storage page.


Actual results:
PVC failure event is not available in VM event

Expected results:
The event about why the VM is failed to be provision should be available in VM events tab.

Additional info:
The VM is stucking in pending state when it failed to create volume.

Comment 1 Guohua Ouyang 2019-04-25 10:02:46 UTC
Created attachment 1558594 [details]
home-events

Comment 2 Guohua Ouyang 2019-04-25 22:42:49 UTC

*** This bug has been marked as a duplicate of bug 1669163 ***


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