[jira] [Closed] (DTACLOUD-60) "uninitialized constant Deltacloud::BackendError" when RHEV-M backend is down

["Ronelle Landy (Closed) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DTACLOUD-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ronelle Landy closed DTACLOUD-60.
---------------------------------

    Resolution: Fixed

Closing out this JIRA based on DTACLOUD-127 where testing was done for checking credentials:

Using an invalid provider and valid credentials for RHEVM
curl -X GET --user 'xx:xx' "http://hp-dl360g5-02.rhts.eng.bos.redhat.com:3005/api/images?format=xml"
<error status='500' url='/api/images?format=xml'>
  <kind>backend_error</kind>
  <backend driver='rhevm' provider='xxx'>
    <code>500</code>
  </backend>
  <message><![CDATA[Unhandled exception or status code (getaddrinfo: Name or service not known)]]></message>
  <backtrace>
    <![CDATA[/usr/lib/ruby/1.8/net/http.rb:560:in `initialize'
    /usr/lib/ruby/1.8/net/http.rb:560:in `open'
    ...... 
                
> "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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira