Bug 1529292
Summary: | uploaded image alignment should be validated | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Daniel Erez <derez> |
Component: | Frontend.WebAdmin | Assignee: | Daniel Erez <derez> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Belka <jbelka> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.2.0 | CC: | bugs, lsvaty |
Target Milestone: | ovirt-4.2.1 | Flags: | rule-engine:
ovirt-4.2+
|
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
On 'Upload Image' dialog, the sector alignment of the selected file should be validated. I.e. the selected file must be aligned to 512 bytes (size in bytes is a multiple of 512); otherwise, the file is not recognized as a valid image for upload. Note that this restriction is due to the sector size defined in vdsm (i.e. 512 bytes).
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-12 11:47:03 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Daniel Erez
2017-12-27 13:12:31 UTC
ok, ovirt-engine-webadmin-portal-4.2.1.3-0.1.el7.noarch ovirt-imageio-proxy-1.2.1-0.el7ev.noarch i tried to upload a raw image which which size was not multiplied by 512 - got error about bad image format in Upload dialog. upload of a raw image multiplied by 512 was initialized but there's no more progres on the action itself. but i was not able to initialize upload of a qcow2 at all - https://bugzilla.redhat.com/show_bug.cgi?id=1539104 This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |