Red Hat Bugzilla – Bug 894689
[ovirt-log-collector] Can not use log-collector due to certificate issues
Last modified: 2014-07-10 20:09:32 EDT
Description of problem:
Can not use log-collector due to certificate issues.
the way optparse works is to first try and find an exact match of the param (that is to match "engine" with "engine"), and if there's no match, it will check whether "engine" could be an abbreviation of another param (that is there's only one parameter that begins with "engine") , and in this case "engine_ca" matches. This causes "engine_ca" param to get value of "engine" from the configuration file, and thus supply incorrect value to the API object creation.
Fix is to replace "engine_ca" -> "ca_file"/"cert_file"/"certificate"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Patch posted for review: http://gerrit.ovirt.org/#/c/11024/1
Verified on sf7
This bug is currently attached to errata RHEA-2013:14554. 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:
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.