Bug 1889213
| Summary: | The error message of uploading failure is not clear enough | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Guohua Ouyang <gouyang> |
| Component: | Console Kubevirt Plugin | Assignee: | Gilad Lekner <glekner> |
| Status: | CLOSED ERRATA | QA Contact: | Guohua Ouyang <gouyang> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.6 | CC: | aos-bugs, eparis, glekner, gouyang, mwasher, tjelinek, ycui, yzamir |
| Target Milestone: | --- | ||
| Target Release: | 4.7.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: | 2021-02-24 15:26:50 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: | |||
|
Description
Guohua Ouyang
2020-10-19 05:17:05 UTC
Sometimes the error is 'Request failed with status code 400'. (In reply to Guohua Ouyang from comment #1) > Sometimes the error is 'Request failed with status code 400'. the root cause of this is: E1019 05:21:02.509421 1 data-processor.go:221] Virtual image size 4294967296 is larger than available size 1073741824. A larger PVC is required. E1019 05:21:02.509458 1 uploadserver.go:366] Saving stream failed: Virtual image size 4294967296 is larger than available size 1073741824. A larger PVC is required. when 'Data Volume failed to initiate upload' is appearing, the dv is now deleted and the message changed to: 'Data Volume failed to initiate upload, and has been deleted.' regarding the 400 error, should we point the user to the logs? I don't know whether there is a common interface to retrieve the error reason from CDI or somewhere else for all types of error. If we just write the error reason by ourselves, it's fragile and not good to maintain them. @Tomas, wdyt？ There is this global "events" screen on the dashboard, would it show up there? (In reply to Gilad Lekner from comment #3) > when 'Data Volume failed to initiate upload' is appearing, the dv is now > deleted and the message changed to: 'Data Volume failed to initiate upload, > and has been deleted.' > The back pod are deleted in this way, not able to look into the pod log for exact failure reason. (In reply to Tomas Jelinek from comment #5) > There is this global "events" screen on the dashboard, would it show up > there? When the upload is failed, there are no error message and useful information in Home -> Events. Now it's have a link for looking at the pod log, but it's always a 404 pod. It only shows 'Request failed with status code 400" now. The issue is fixed on latest ocp 4.7, move back to ON_QA. 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.7.0 security, bug fix, and enhancement 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. https://access.redhat.com/errata/RHSA-2020:5633 *** Bug 1957071 has been marked as a duplicate of this bug. *** |