incubator-deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michal Fojtik (JIRA)" <>
Subject [jira] [Assigned] (DTACLOUD-60) "uninitialized constant Deltacloud::BackendError" when RHEV-M backend is down
Date Thu, 21 Jul 2011 11:36:58 GMT


Michal Fojtik reassigned DTACLOUD-60:

    Assignee: Michal Fojtik  (was: David Lutterkort)

> "uninitialized constant Deltacloud::BackendError" when RHEV-M backend is down
> -----------------------------------------------------------------------------
>                 Key: DTACLOUD-60
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>         Environment: Latest source from git, using rhevm driver on F14
>            Reporter: Matt Wagner
>            Assignee: Michal Fojtik
>            Priority: Minor
> When running deltacloudd with the RHEV-M driver, the following error is raised in valid_credentials?
if the RHEV-M server is unreachable:
> NameError - uninitialized constant Deltacloud::BackendError:
>  ././lib/deltacloud/drivers/rhevm/rhevm_driver.rb:179:in `valid_credentials?'
> (This can be reproduced by starting with a bogus API_PROVIDER, e.g., "API_PROVIDER=
./bin/deltacloudd -i rhevm -p 3001" )
> It looks like the error we're trying to catch there is actually Deltacloud::ExceptionHandler::BackendError,
not Deltacloud::BackendError. I'm entering a JIRA instead of sending a trivial patch for this
particular bug because it looks like "Deltacloud::BackendError" is used in multiple places
(including other drivers), so this should probably be investigated by someone who knows the
code a lot better than I do.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message