fog/fog-openstack

Fog for OpenStack Platform

Gilles Dubreuil

@gildub

Could you please add those lines at the top of your snippet:

gem 'fog-core', '1.45.0'
gem 'fog-openstack', '0.2.0'

Jonas Wielicki

@horazont

same issue

Gilles Dubreuil

@gildub

Is your environment accesible?

Jonas Wielicki

@horazont

what do you mean by accessible?

Gilles Dubreuil

@gildub

Can I log in and debug?

Jonas Wielicki

@horazont

unfortunately not

this is my local work machine

we’re having this issue on all of our chef-using machines though; based on chefdk 1.6.1 (rather old, I know)

so you might be able to recreate by installing chefdk 1.6.1 and using chef exec ruby test.rb

(chefdk comes with a bundled ruby)

Gilles Dubreuil

@gildub

So chefdk 1.6.1 has fog-openstack wrapped within bundler, correct?

Jonas Wielicki

@horazont

I’m not sure what that means. I manage the installed gems with chef gem {install,uninstall,list}

Gilles Dubreuil

@gildub

fog-openstack gem is managed by chef using bundle. Just trying to locate the gem in question and look inside it's the right one

Jonas Wielicki

@horazont

the ruby environment bundled by chefdk is in /opt/chef/embedded/lib/ruby, that much I know. when using chef gem {install,uninstall}, gems end up/get removed from there

Gilles Dubreuil

@gildub

Okay, let's put chef on the side for a minute.

Jonas Wielicki

@horazont

right

would it help if I tried to recreate the issue within a clean ubuntu:16.04 docker container or something like that?

Gilles Dubreuil

@gildub

If you use a blank (new) user, (assuming it has access to ruby and gem), you should be able to gem install fog-openstack and run your snippet.

Jonas Wielicki

@horazont

I can reproduce this with a fresh ubuntu 16.04 (via docker)

I start to suspect that this might have to do with how the endpoints on that openstack are defined

Gilles Dubreuil

@gildub

Could you please print the catalog? openstack catalog list

Or at least the endpoint for the Identity service?

Jonas Wielicki

@horazont

| keystone       | identity        | f1a                                                                                                  |
|                |                 |   public: https://identity-f1a.cloudandheat.com:5000/v3                                              |
|                |                 | f1a                                                                                                  |
|                |                 |   internal: https://identity-f1a.cloudandheat.com:5000/v3                                            |
|                |                 | f1a                                                                                                  |
|                |                 |   admin: https://identity-f1a.cloudandheat.com:35357/v3                                              |
|                |                 |                                                                                                      |

Gilles Dubreuil

@gildub

Ok, so I added a patch to work around 'versionned' endpoints. Let me check.

Could you set openstack_auth_url: using your endpoint value?

https://identity-f1a.cloudandheat.com:5000/v3

Jonas Wielicki

@horazont

like, openstack_auth_url: "https://identity-f1a.cloudandheat.com:5000/v3"?

Gilles Dubreuil

@gildub

Yes

Jonas Wielicki

@horazont

same issue

should I have had updated something inbetween?

Gilles Dubreuil

@gildub

I don' t think so, the auth_url should be the same value as the endpoint. So that's good

Now the fact that it contains 'v3' is filtered by 0.2.0

I've just checked that

But I need to test with a 'versionned' endpoint, hold on.

And I can recreate the issue!

Jonas Wielicki

@horazont

\o/

Gilles Dubreuil

@gildub

Thanks for bringing it!

Jonas Wielicki

@horazont

you’re welcome ;-)

should I file a proper issue for this?

for tracking

Gilles Dubreuil

@gildub

If you like to, although I'm going to work on it ASAP. More likely tomorrow because it's late for me down under.

Jonas Wielicki

@horazont

it would help us to track it, so I’ll do that

Gilles Dubreuil

@gildub

Absolutely.

A work around in the meantime is to remove the 'v3' from the endpoint. Normally Identity endpoint is version less and that's the default now.

Jonas Wielicki

@horazont

right… this might be some legacy from the time of the v2/v3 transition

Gilles Dubreuil

@gildub

Exactly

Jonas Wielicki

@horazont

I’ll have us look into whether we should remove it altogether of if that breaks anything for us

Gilles Dubreuil

@gildub

Fair enough

Jonas Wielicki

@horazont

FYI: fog/fog-openstack#420

Where communities thrive

People

Repo info

Activity