Bug 1315994
Summary: | force iso image filename lowercase | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Stefano Cislaghi <cislo78> |
Component: | BLL.Storage | Assignee: | Tal Nisan <tnisan> |
Status: | CLOSED WONTFIX | QA Contact: | Elad <ebenahar> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.0 | CC: | bugs, cislo78, ebenahar, lveyde, sbonazzo, tnisan, ylavi |
Target Milestone: | --- | Flags: | sbonazzo:
ovirt-4.3-
|
Target Release: | --- | ||
Hardware: | All | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-30 09:05:02 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1091377 |
Description
Stefano Cislaghi
2016-03-09 08:29:11 UTC
Isn't it better to just be able to use ISO prefix case insensitive? This sounds like a more reasonable solution to the problem Hi Tal, I was just wondering why uppercase prefix is not recognized, but i'm no developer so i assume there's some good reason for this to work this way, that i'm not aware of. If it isn't, of course it should be more comfortable the way you suggest. I think this solution will be the better one in that case. Amit, when you are looking at this bug please try to reach that solution tal, do you mind move also the product to ovirt-engine if you plan to solve this bug there? Assuming the solution will be trivial of course, if there is a legacy reason for not checking extensions in case insensitive due to some limitation and it won't be possible we will have to resort to the first proposed solution I think that the bug needs to be renamed force ISO filename *extension* to be lowercase, if any, as there is no reason to touch the filename itself. IMHO the best option would be to simply modify the filter to accept any combination of ISO extension. We plan to address this in next release by moving ISOs to use from API\UI. We will address this then. @Tal - has this issue been already handled as part of your work on upload ISO? (In reply to Daniel Erez from comment #8) > @Tal - has this issue been already handled as part of your work on upload > ISO? 4.2.z will allow you to upload an arbitrary file to a DATA domain and use it as an ISO. Once we make sure this that feature is in, this BZ can probably be closed as WONTFIX. Since 4.2 we support uploading ISO images to a data domain, the image itself is recognized as an ISO regardless of the name or prefix thus making this bug obsolete |