deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michal Fojtik (JIRA)" <>
Subject [jira] [Resolved] (DTACLOUD-330) Openstack driver - Deltacloud requires credentials for any request
Date Tue, 02 Oct 2012 12:37:08 GMT


Michal Fojtik resolved DTACLOUD-330.

    Resolution: Fixed

commit caf973290b9c9e585fda92ebd800f8c8f8cbf2d1
Author: Michal Fojtik <>
Date:   Thu Sep 27 14:15:39 2012 +0200

    Openstack: Capture missing username as 401 error (DTACLOUD-330)
    Signed-off-by: Michal fojtik <>

commit d5aa10ed660f1011888d505f45362e2a7c9a6e60
Author: Michal Fojtik <>
Date:   Thu Sep 27 12:45:05 2012 +0200

    Client: Send API_PROVIDER when changing driver
    Because OpenStack driver now require authentication
    for discover_entrypoint, we need to send API_PROVIDER string
    together with new credenials.
    This patch should fix the problem.
    Signed-off-by: Michal fojtik <>
> Openstack driver - Deltacloud requires credentials for any request
> ------------------------------------------------------------------
>                 Key: DTACLOUD-330
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>         Environment: deltalcoud-core from master branch (last commit 97db199f908eb9fcd7780d904e7161fb7c60bac5)
>            Reporter: Jan Provaznik
>            Assignee: Michal Fojtik
> Conductor keeps providers and provider accounts separately. This means that at first
step a user adds a provider (ec2, rhevm, openstack), then he can add multiple accounts for
this provider.
> When adding a provider, Conductor checks if the provider is valid by doing dc connect
with nil credentials:
>, nil, url)
> The problem is that this call always fails for Openstack driver with 
> Deltacloud::ExceptionHandler::BackendError - Unhandled exception or status code (Must
supply a :username):
> 	/usr/local/share/gems/gems/openstack-1.0.6/lib/openstack/connection.rb:74:in `initialize'
> 	/usr/local/share/gems/gems/openstack-1.0.6/lib/openstack/connection.rb:60:in `new'
> 	/usr/local/share/gems/gems/openstack-1.0.6/lib/openstack/connection.rb:60:in `create'
> 	/home/jprovazn/devel/deltacloud/server/lib/deltacloud/drivers/openstack/openstack_driver.rb:357:in
`block in new_client'
> 	/home/jprovazn/devel/deltacloud/server/lib/deltacloud/drivers/exceptions.rb:199:in `call'
> 	/home/jprovazn/devel/deltacloud/server/lib/deltacloud/drivers/exceptions.rb:199:in `safely'
> 	/home/jprovazn/devel/deltacloud/server/lib/deltacloud/drivers/openstack/openstack_driver.rb:352:in
> 	/home/jprovazn/devel/deltacloud/server/lib/deltacloud/drivers/openstack/openstack_driver.rb:47:in
> 	/home/jprovazn/devel/deltacloud/server/lib/deltacloud/server.rb:52:in `block in <class:API>'
> From what I know DC requries openstack credentials to be able to connect to openstack
api and check if some bucket is supported or not.
> Is it possible to offer some unauthenticated connection which can be used just to check
that a provider is accessible?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message