Bug 999336

Summary:	rhevm-log-collector does not respect "--insecure"
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	ovirt-engine-log-collector	Assignee:	Kiril Nesenko <knesenko>
Status:	CLOSED ERRATA	QA Contact:	sefi litmanovich <slitmano>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.3.0	CC:	aberezin, acathrow, dfediuck, iheim, knesenko, kroberts, oschreib, Rhev-m-bugs, yeylon
Target Milestone:	---
Target Release:	3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:	rhevm-log-collector-3.3.0-1.el6ev	Doc Type:	Bug Fix
Doc Text:	Previously rhevm-log-collector did not appear to respect the --insecure option. It was impossible to work with the insecure option, except with https. Now, specifying --insecure mode will work with http.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-21 16:59:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1019461

Description Sandro Bonazzola 2013-08-21 07:56:42 UTC

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.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.

Comment 1 Kiril Nesenko 2013-09-03 13:25:39 UTC

For QE steps to verification. From the remote host run:

engine-log-collector --insecure -u admin@internal -r remote_hostname list

Comment 3 sefi litmanovich 2013-09-22 14:36:45 UTC

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.

Comment 4 Charlie 2013-11-28 01:16:59 UTC

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.

Comment 5 errata-xmlrpc 2014-01-21 16:59:58 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.

http://rhn.redhat.com/errata/RHBA-2014-0039.html