Description of problem: iso-uploader shows the same behavior describer here https://bugzilla.redhat.com/1136434 for image-uploader. --insecure still requires a valid CA cert Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Use iso-uploader with --insecure option and an invalid CA cert 2. 3. Actual results: ERROR: Problem connecting to the REST API. Is the service available and does the CA certificate exist? Expected results: - insecure option is honored Additional info:
still happening in vt3.1 [root@pb-rh35 foo]# engine-iso-uploader upload -i ISO_DOMAIN --insecure --cert-file=ca.pem test.iso Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): ERROR: Problem connecting to the REST API. Is the service available and does the CA certificate exist? ERROR: Unable to get ISO domain data INFO: Use the -h option to see usage. [root@pb-rh35 foo]# rpm -qa | grep iso-uploader
Truncated copy-paste, sorry [root@pb-rh35 foo]# rpm -qa | grep iso-uploader rhevm-iso-uploader-3.5.0-0.3.beta.el6ev.noarch
Sorry, forgot to set fixed-in-version.
in rhevm-image-uploader-3.5.0-1.el6ev.noarch
Hi Simone, In regards to "Fix: Avoiding CA file check. Result: with --insecure option the user could also avoid to prove the CA cert path", isn't the --insecure option doesn't work fixed in BZ1100824? Do we still want to tell users to avoid CA file check? If not, I think the requires_doc_text flag can set to -. Cheers, Julie
Hi Julie, the two patches together solve the issue: now using --insecure option it skips the SSL validation and so the user doesn't also need to provide a correct path to CA cert file.
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-2015-0191.html