Red Hat Bugzilla – Bug 999336
rhevm-log-collector does not respect "--insecure"
Last modified: 2015-09-22 09:09 EDT
Description of problem: rhevm-log-collector does not appear to respect --insecure. Version-Release number of selected component (if applicable): any version >= 3.2.0 How reproducible: 100% 1. On remote system: rhevm-log-collector --insecure -u user@rhevm.example.com -r rhevm.example.com list Actual results: ERROR: Problem connecting to the REST API. Is the service available and does the CA certificate exist? Additional info: This bug will be solved as in bug #886525 and bug #951100 , aligning the method that initialize the API with rhevm-iso-uploader.
For QE steps to verification. From the remote host run: engine-log-collector --insecure -u admin@internal -r remote_hostname list
Varified on rhevm 3.3 Is15. cmd: engine-log-collector --insecure -u admin@internal -r slitmano-rhevm.scl.lab.tlv.redhat.com list after entering password got the following result: Host list (datacenter=None, cluster=None, host=None): Data Center | Cluster | Hostname/IP Address DC1 | cluster1 | 10.35.0.186 DC1 | cluster1 | rose07.qa.lab.tlv.redhat.com So no problem with connection to the REST API.
This bug is currently attached to errata RHBA-2013:15255. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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. http://rhn.redhat.com/errata/RHBA-2014-0039.html