Bug 1924728 - Difficult to identify deployment issue if the destination disk is too small
Summary: Difficult to identify deployment issue if the destination disk is too small
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Matan Schatzman
QA Contact: Guohua Ouyang
: 1940296 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2021-02-03 14:22 UTC by Martin Tessun
Modified: 2021-07-27 22:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-07-27 22:40:55 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 8700 0 None open Bug 1924728: Add warning events to vm status and changed appearance to be more similar to cluster overview 2021-04-19 13:28:22 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:41:21 UTC

Description Martin Tessun 2021-02-03 14:22:56 UTC
Description of problem:
Deploying a Windows VM with default settings (20GB disk) may lead to a deployment issue, as my Windows deployment needs a 50GB disk at least.
Unfortunately the error is hard to find.

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

How reproducible:

Steps to Reproduce:
1. USe a qcow2 Windows Image for deployment that is using a 50GiB disk
2. In the UI use the wizard and keep the defaults (20GiB Disk Size)
3. Create the VM

Actual results:
The VM status stays in "Starting" but the Event log shows a Warning with "Back-off restarting failed container".
Looking closer at the event it shows that the root-disk import fails. This import is retried forever.

Once you click on the link, you get to the pod details, still not revealing the 
reason of the failure.
You need to navigate to the "Logs" tab to finally see the real reason:

E0203 14:16:34.001176       1 data-processor.go:239] Virtual image size 59055800320 is larger than available size 19788924395 (PVC size 59055800320, reserved overhead 0.055000%). A larger PVC is required.
Unable to convert source data to target format

Expected results:
The installation is aborted and a sensible error message is shown (e.g.: disk too small xx GiB needed, xx GiB provided)

Additional info:

Comment 1 Yaacov Zamir 2021-02-03 16:27:37 UTC
TL;DR of bug description :-)

Status of VM in the UI is wrong when trying to create a VM and vm pod can't create storage:

Actual status:

Expectd status:
"Error" + helpful message

Comment 2 Guohua Ouyang 2021-03-03 09:37:36 UTC
This is a bit similar with bz https://bugzilla.redhat.com/show_bug.cgi?id=1889213, not sure whether can we able to expose the cdi importer pod's logs on console.

Comment 3 Yaacov Zamir 2021-04-07 06:40:04 UTC
*** Bug 1940296 has been marked as a duplicate of this bug. ***

Comment 5 Guohua Ouyang 2021-04-22 03:50:23 UTC
Looks good on master

Comment 8 errata-xmlrpc 2021-07-27 22:40:55 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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