Bug 1138558 - rhevm-image-uploader ignores insecure option
Summary: rhevm-image-uploader ignores insecure option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-image-uploader
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
urgent
medium
Target Milestone: ---
: 3.4.3
Assignee: Simone Tiraboschi
QA Contact: sefi litmanovich
URL:
Whiteboard: integration
Depends On: 1136434
Blocks: 1126430
TreeView+ depends on / blocked
 
Reported: 2014-09-05 07:45 UTC by rhev-integ
Modified: 2014-12-15 15:06 UTC (History)
12 users (show)

Fixed In Version: rhevm-image-uploader-3.4.3-1.el6ev
Doc Type: Rebase: Bug Fixes Only
Doc Text:
Rebase package(s) to version: 3.4.3 Highlights and important bug fixes: since previous rhevm-image-uploader version, it fixed this bug only.
Clone Of: 1136434
Environment:
Last Closed: 2014-10-23 12:09:25 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1706 0 normal SHIPPED_LIVE rhevm-image-uploader bug fix update 2014-10-23 16:08:40 UTC
oVirt gerrit 32329 0 master MERGED ovirt-image-uploader: fixing usage of API SDK insecure parameter Never
oVirt gerrit 32353 0 ovirt-image-uploader-3.5 MERGED ovirt-image-uploader: fixing usage of API SDK insecure parameter Never
oVirt gerrit 32355 0 ovirt-image-uploader-3.4 MERGED ovirt-image-uploader: fixing usage of API SDK insecure parameter Never

Comment 2 sefi litmanovich 2014-10-02 13:42:09 UTC 
Verfied with rhevm-3.4.3-1.1.el6ev.noarch, rhevm-image-uploader-3.4.3-1.el6ev.noarch

1. created export domain.
2. configured engine's credentials in /etc/ovirt-engine/imageuploader.conf.
3. verified that trying to upload ovf file with wrong cert file fails.
4. verified that uploading the same file with the wrong cert file and --insecure option succeeds.
Comment 4 errata-xmlrpc 2014-10-23 12:09:25 UTC 
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/RHBA-2014-1706.html
Note You need to log in before you can comment on or make changes to this bug.