ManageIQ can't contact openstack endpoint


#1

Hi,
I have issue on ManageIq with Openstack provider.
ManageIq can"t get data from openstack.

I use proxy for my public endpoint. But I have a rewriterule on proxy https://proxy/ ==> https://proxy/dashboard (for horizon).

For all endpoint I have https://proxy/compute ==> https://controller:8774, https://proxy/image ==> https://controller:9292, …

Internal and admin URL is https://controller:PortService.

But I have Error in ManageIQ fog.log =>

[----] E, [2016-04-04T08:19:05.292073 #3323:ed3988] ERROR – : excon.error #<Excon::Errors::Found: Expected([200, 204, 300]) <=> Actual(302 Found)
excon.error.response
:body => “\n\n302 Found\n\n

Found

\n

The document has moved <a href=“https://proxy/dashboard/”>here.

\n\n”
:headers => {
“Connection” => “close”
“Content-Length” => "215"
“Content-Type” => "text/html; charset=iso-8859-1"
“Date” => “Mon, 04 Apr 2016 12:19:05 GMT”
“Location” => “https://proxy/dashboard/
“Server” => “Apache”
}
:local_address => “10.121.204.151”
:local_port => 60405
:reason_phrase => “Found”
:remote_ip => “10.121.204.11”
:status => 302
:status_line => “HTTP/1.1 302 Found\r\n”

Why ManageIQ need to have access to / ?

Log from my proxy ==>

10.121.204.151 - - [04/Apr/2016:14:46:56 +0200] “GET / HTTP/1.1” 302 215 “-” “curl/7.29.0” 138
10.121.204.151 - - [04/Apr/2016:14:46:59 +0200] “GET /dashboard HTTP/1.1” 302 - “-” “curl/7.29.0” 14164
10.121.204.151 - - [04/Apr/2016:14:47:01 +0200] “GET /dashb HTTP/1.1” 403 1043 “-” “curl/7.29.0” 1380
10.121.204.151 - - [04/Apr/2016:14:47:04 +0200] “GET /dashboard/ HTTP/1.1” 302 - “-” “curl/7.29.0” 11175
10.121.204.151 - - [04/Apr/2016:14:47:10 +0200] “GET /compute/ HTTP/1.1” 200 185 “-” “curl/7.29.0” 24606
10.121.204.151 - - [04/Apr/2016:14:47:15 +0200] “GET / HTTP/1.1” 302 215 “-” “curl/7.29.0” 150

Thx for Help :slight_smile:


#2

@blomquisg can you review this question from @kodoku and forward to a SME if necessary.


#3

@Ladas, you might be able to answer this question quicker.


#4

We can close this one, it’s actually an issue in the fog-openstack gem. I talked to @kodoku on gitter, he will open issue there