VMware Cloud Community
sboirie
Contributor
Contributor

VRO: Cannot execute the request: Circular redirect to http://...

Hello, not sure if it is the right place for my question :

I am using VRA7.6 + VRO7.6 and i am facing an issue with the HTTP REST plug-in (v2.3.2)

I have created a HOST and some HOST operations (GET) with workflows associated to retrieve values from an API

The HOST configuration is basic (no auth, no certificates, no proxy...). The workflows generated are working correctly when i run from the VRO console

But, when the same workflow is called from VRA (through EventBroker events) i get the error :
Cannot execute the request:  Circular redirect to http://...

Is someone already got the same problem ?

Thanks

Reply
0 Kudos
8 Replies
lnairn
VMware Employee
VMware Employee

Hi,

Do you see the errors in vRO workflow execution, or in vRA?

Are you using embedded vRO?

Regards,

Leandro.

Reply
0 Kudos
sboirie
Contributor
Contributor

Hi,

the error is displayed in VRO (when the Workflow is failed)

I am using the embedded VRO, in x3 clustered mode behind an NSX load balancer.

Reply
0 Kudos
Enter123
Enthusiast
Enthusiast

I am having the same problem and haven't found solution for this.

in my case, I am trying to check the status of an Ansible Workflow. First time I run it, it's fine, I get proper response. if I want to check the status again, it get that message, circular redirect.

Reply
0 Kudos
melvinlewis
Contributor
Contributor

Did you ever figure out a work around?

Reply
0 Kudos
xian_
Expert
Expert

Have you tried changing this option?

xian__0-1605649978052.png

 

Reply
0 Kudos
melvinlewis
Contributor
Contributor

My issue was the url of the REST Endpoint.  It was causing a redirect.  Once I corrected the issue, it started working.

Reply
0 Kudos
filosmith
Enthusiast
Enthusiast

Same here. When trying to get an ansible tower job status. I tried ansibleRestHost.setAutoUrlRedirect(false)

Reply
0 Kudos
filosmith
Enthusiast
Enthusiast

I didn't have the trailing / after /api/v2/jobs. Changing it to /api/v2/jobs/ fixed it for me.

Reply
0 Kudos