Solved: Re: VRA with VIO as a Endpoint

dalo · ‎05-08-2019

We try to connect our VIO 5.1 as a endpoint to VRA 6.7. Its not in the support Matrix, but we have a statement from vmware that this combination is working.

We want to connect via a DEM worker and not set VRA as a Keystone Identity Provider as described in the VIO documentation.

We could connect other (native) openstack implementation without a problem, but with VIO we failed with the following error in iaas:

2019-05-08T08:17:35.246Z VRA-IAAS-01 vcac: [component="iaas:DynamicOps.DEM.exe" priority="Error" thread="3644"] [sub-thread-Id="19" context="" token=""] Invalid HTTP response code 417:ExpectationFailed <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

<title>417 Expectation Failed</title>

</head><body>

<h1>Expectation Failed</h1>

<p>The expectation given in the Expect request-header

field could not be met by this server.

The client sent<pre>

Expect: 100-continue

</pre>

</p><p>Only the 100-continue expectation is supported.</p>

<hr>

<address>Apache/2.4.18 (Ubuntu) Server at viohost.domain Port 5000</address>

</body></html>

Has anybody a clue why they could not talk to each other?

sbeaver · ‎05-12-2019

I have come across this and have an answer for you. The fix is to edit and add a value to the worker configuration so what I did and recommend is to create another worker and tag this worker with all the openstack task. Check out this URL -- http - Supporting the "Expect: 100-continue" header with ASP.NET MVC - Stack Overflow

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**

View solution in original post

sbeaver · ‎05-12-2019

I have come across this and have an answer for you. The fix is to edit and add a value to the worker configuration so what I did and recommend is to create another worker and tag this worker with all the openstack task. Check out this URL -- http - Supporting the "Expect: 100-continue" header with ASP.NET MVC - Stack Overflow

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**

dalo · ‎05-21-2019

Thank you! In the meantime vmware support could help us with this too, the answer from them for future reference:

For similar behavior with VIO, in previous cases adding the following line,

expect100Continue="false"

in the config file 'DynamicOps.DEM.exe' at location "C:\Program Files (x86)\VMware\vCAC\Distributed Execution Manager\DEM\" , resolved the datacollection issue.

This will look something like :

-----------------

<system.net>

</settings>

</system.net>

-----------------

This worked for our "expect 100 error" but now we stuck with:

Endpoint Data Collection failed for endpoint OpenStack [Workflow Instance Id=8283]

(https://172.31.93.25:5000/v2.0/tokens): The resource could not be found.

Invalid HTTP response code 404:NotFound {"error": {"message": "(https://172.31.93.25:5000/v2.0/tokens): The resource could not be found.", "code": 404, "title": "Not Found"}}

We are still working with support for a solution for this and I will update this thread, but if someone knows a shortcut, that would be great.

All

VRA with VIO as a Endpoint