Bug 1547636

Summary: Confusing description in OVA import
Product: [oVirt] ovirt-engine Reporter: Jiří Sléžka <jiri.slezka>
Component: Frontend.WebAdminAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED CURRENTRELEASE QA Contact: samuel macko <smacko>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.2.1.7CC: bugs, lsvaty, lveyde, michal.skrivanek
Target Milestone: ovirt-4.2.2Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.2.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 11:15:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jiří Sléžka 2018-02-21 16:22:39 UTC 
Description of problem:

When importing an ova file, there is an input field called "Path" which could imply the path to the directory where are ova files located. In fact, the user should enter the path to the particular ova file so description should befor example "Path to ova file".

Of course solution like listing all ova files in that directory would be even more user friendly.

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

4.2.1.7-1.el7.centos

How reproducible:

Steps to Reproduce:
1. click on Import (vm)
2. choose "Virtual Appliance (OVA)" as a source
3. see "Path" description

Expected results:

"Path to ova file" description
Comment 1 Michal Skrivanek 2018-03-07 19:01:10 UTC 
let's go with "File Path" to not make it too long for other languages. Should be still more clear than "Path"
Comment 2 samuel macko 2018-03-19 14:07:43 UTC 
Verified in ovirt version 4.2.2.4-0.1.el7.

Verified by following the reproducer.
Description changed to "File Path".
Comment 3 Sandro Bonazzola 2018-03-29 11:15:53 UTC 
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 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.