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

Bug 1048596

Summary: First VDSM verb returns blank lastClient, lastClientIface
Product: Red Hat Enterprise Virtualization Manager Reporter: Assaf Muller <amuller>
Component: vdsmAssignee: Assaf Muller <amuller>
Status: CLOSED ERRATA QA Contact: Martin Pavlik <mpavlik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: amuller, bazulay, danken, gklein, iheim, lpeer, mpavlik, myakove, nyechiel, sbonazzo, ybronhei, yeylon, zdover
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: ovirt-3.4.0-beta2 Doc Type: Bug Fix
Doc Text:
Previously, installing a host from the engine caused the engine to send "getVdsCaps". "getVdsCaps" uses "lastClientIface" to determine where to put the management bridge ("ovirtmgmt"). Because VDSM reports the last client IP for the previous connection (not the current one), the initial connection returns "0.0.0.0". This cased a failure in the automatic creation of the management network. The first VDSM verb now returns the correct lastClient IP and the correct lastClientIface.
Story Points: ---
Clone Of:
: 1055557 (view as bug list) Environment:
Last Closed: 2014-06-09 13:27:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1055557, 1078909, 1142926    

Description Assaf Muller 2014-01-05 16:20:44 UTC
Description of problem:
When installing a host from the engine, the engine sends a getVdsCaps which uses 'lastClientIface' to know on which device to place the management bridge ('ovirtmgmt'). However, since VDSM reports the last client IP for the *previous* connection and not the current one, the first ever connection will always return '0.0.0.0'.

How reproducible:
100%

Steps to Reproduce:
1. Install VDSM
2. Start VDSM
3. Run getVdsCaps

Actual results:
The first invocation after VDSM start will return '0.0.0.0' for lastClient, 'lo' for lastClientIface

Expected results:
First invocation, like following ones, should return the correct lastClient IP and the correct lastClientIface.

Comment 4 Martin Pavlik 2014-02-12 09:34:19 UTC
verified 

[root@dell-r210ii-07 ~]# rpm -q vdsm
vdsm-4.14.1-3.el6.x86_64


lastClient = '10.34.66.71'
lastClientIface = 'em1'

Comment 7 errata-xmlrpc 2014-06-09 13:27:13 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-0504.html