Created attachment 518776 [details]
VDC error message
Using the most recent RHEV 3 beta, and a couple of previous versions, I've had multiple RHEL host installs that post an error in the RHEV-M GUI stating:
"No route to VDC. Check switch/router
settings and try registration again."
So far, this error has appeared to not cause any problem... in each case, the host install succeeds anyway, and the host works just fine.
The error message, though, is disconcerting.
I've attached a screenshot of the error.
Doron's comments on rhev-beta regarding this were:
There may be a temporary connectivity break when
preparing the rhevm bridge, which is inerpreted as
an error by the installing script- vds_bootsrap.
Please open a BZ on it fot vdsm bootstrapping.
Sent from my Android phone.
From: James Rankin [email@example.com]
Received: Thursday, 18 Aug 2011, 1:10
To: Doron Fediuck [firstname.lastname@example.org]
Subject: Re: [rhev-beta] No route to VDC - during host install?
It's a RHEL host.
On 08/17/2011 05:09 PM, Doron Fediuck wrote:
> Is this a RHEL or RHEV-H host?
> Sent from my Android phone.
> -----Original Message-----
> From: James Rankin [email@example.com]
> Received: Thursday, 18 Aug 2011, 1:01
> To: firstname.lastname@example.org [email@example.com]
> Subject: [rhev-beta] No route to VDC - during host install?
> One more installation question... on my last few installs, I've seen a
> host install error that states: "No route to VDC. Check switch/router
> settings and try registration again."
> Example screenshot attached.
> Despite this error, the host still registers fine and works well.
> What does this error mean?
Redirecting to VDSM,
since it comes from the bootstrapping scripts, and not RHEV-M's vds_installer.
Author: Federico Simoncelli <firstname.lastname@example.org>
Date: Thu Aug 18 12:29:59 2011 +0000
BZ#731598 Use the correct port in waitRouteRestore
I don't see this error with either a fixed or an unfixed build. Unable to verify.
Unable to reproduce on ic145. Closing as verified.
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.