[
https://issues.apache.org/jira/browse/DTACLOUD-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068929#comment-13068929
]
Hudson commented on DTACLOUD-60:
--------------------------------
Integrated in apache-deltacloud-core #234 (See
[https://builds.apache.org/job/apache-deltacloud-core/234/])
DTACLOUD-60: Removed obsoleted exception from valid_credetials in RHEV-M
driver
mfojtik : http://svn.apache.org/viewvc/?view=rev&rev=1149129
Files :
*
/incubator/deltacloud/trunk/server/lib/deltacloud/drivers/rhevm/rhevm_driver.rb
> "uninitialized constant Deltacloud::BackendError" when RHEV-M backend is down
> -----------------------------------------------------------------------------
>
> Key: DTACLOUD-60
> URL: https://issues.apache.org/jira/browse/DTACLOUD-60
> 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=127.127.127.127 ./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: http://www.atlassian.com/software/jira
