Bug 1104661
| Summary: | zero returncode on error | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Petr Beňas <pbenas> |
| Component: | ovirt-image-uploader | Assignee: | Lev Veyde <lveyde> |
| Status: | CLOSED ERRATA | QA Contact: | Gonza <grafuls> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.5.0 | CC: | dfediuck, gklein, melewis, pstehlik, rbalakri, Rhev-m-bugs, sbonazzo, sherold, srevivo, ylavi |
| Target Milestone: | ovirt-4.0.0-alpha | ||
| Target Release: | 4.0.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt 4.0.0 alpha1 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, a returncode of 0 was returned, even if something went wrong during the file upload phase. Now, this has been corrected and makes the program return ExitCodes.UPLOAD_ERR code (3) if something went wrong during the file upload phase.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-08-23 21:00:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Petr Beňas
2014-06-04 13:04:16 UTC
Not critical, not urgent, not a regression, postponing to 3.6 Verified with: ovirt-image-uploader-4.0.0-1.el7ev.noarch # engine-image-uploader -e export_domain -N appliance --ovf-id upload rhevm-appliance-20160623.0-1.x86_64.rhevm.ova WARNING: ovirt-image-uploader is deprecated in 4.0 and will be removed in 4.1 Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): ERROR: /tmp/tmpu5InQw/6f6d46f8-12a6-49c8-9814-c4903b95466f/master/vms/7b51fb3b-c42b-4f0b-89ce-a2d778a4734e/7b51fb3b-c42b-4f0b-89ce-a2d778a4734e.ovf exists on 10.34.63.199. Either remove it or supply the --force option to overwrite it. # echo $? 3 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, 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://rhn.redhat.com/errata/RHEA-2016-1746.html |