Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 950336

Summary:	[RHEVM] [rhevm-log-collector] Using -H option, hypervisor log is not collected for both ip address & fqdn
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Ilanit Stein <istein>
Component:	ovirt-engine-log-collector	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED ERRATA	QA Contact:	sefi litmanovich <slitmano>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.2.0	CC:	acathrow, iheim, jkt, knesenko, pstehlik, Rhev-m-bugs, sbonazzo, 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 when a hypervisor was added to the manager using its FQDN, specifying its IP address using the -H option caused an error "The following hosts are not listed as hypervisors". Now, providing an FQDN that resolves to IP vice versa, either one can be specified to add a hypervisor to the manager.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-21 16:59:24 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:
Embargoed:

Description Ilanit Stein 2013-04-10 06:35:03 UTC

Description of problem:
log-collector just filter the list of hypervisors provided by the engine, so if in the engine the hypervisor is listed as ip address, it will be collected only if you specify the same ip address. If the hypervisor is registered using the fqdn, it will match only fqdn in -H argument.
Need to add some logic on resolving fqdn and reverse resolving ip address.

Version-Release number of selected component (if applicable):
SF13

How reproducible:
always

Steps to Reproduce:
rhevm-log-collector -H <hypervisor>
Try hypervisor fqdn & IP - for one of these you'll get the message:
"INFO: No hypervisors were selected, therefore no hypervisor data will be collected."
depending on what how hypevisor was registered in the engine.
 
Additional info:
This bug is driven from bug 918020, comment #6.

Comment 2 Sandro Bonazzola 2013-09-05 15:26:58 UTC

Patch pushed upstream master.

previously if an hypervisor was added to the engine
using its FQDN specifying its IP address to -H (or
vice versa) caused an error like:
'The following host are not listed as hypervisors:...'

now provided that FQDN resolve to IP and IP reverse
resolve to FQDN you can specify indifferently one
of them

Comment 3 Sandro Bonazzola 2013-09-10 06:14:21 UTC

merged upstream 3.3 branch: http://gerrit.ovirt.org/gitweb?p=ovirt-log-collector.git;a=commit;h=c7301dbd292009bdcfbb3a3cd3efe9bd5e3b1e97

Comment 5 sefi litmanovich 2013-09-23 16:04:38 UTC

Verified on rhevm 3.3 IS15.
rhevm-log-collector-3.3.0-1.el6ev

Comment 6 Charlie 2013-11-28 01:16:40 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 7 errata-xmlrpc 2014-01-21 16:59:24 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