Created attachment 1313999 [details] conf files and provider log Description of problem: When OVN provider is configured to work with HTTPS protocol, a post request to get a token from https://<host>:35357/v2.0/tokens: Body: { "auth" : { "passwordCredentials" : { "username" : "<user>", "password" : "<pass>" } } } results in URL's with incorrect HTTP protocol: { "endpoints_links": [ ], "endpoints": [ { "adminURL": "http://localhost:9696/v2.0/networks", "region": "RegionOne", "id": "00000000000000000000000000000001", "internalURL": "http://localhost:9696/v2.0/networks", "publicURL": "http://localhost:9696/v2.0/networks" } ], "type": "network", "name": "neutron" }, { "endpoints_links": [ ], "endpoints": [ { "adminURL": "http://localhost:35357/v2.0/tokens", "region": "RegionOne", "publicURL": "http://localhost:35357/v2.0/tokens", "internalURL": "http://localhost:35357/v2.0/tokens", "id": "00000000000000000000000000000002" } ], "type": "identity", "name": "keystone" } Version-Release number of selected component (if applicable): ovirt-provider-ovn-1.1-2.20170710074946.git5abef7f.el7.centos.noarch How reproducible: 100%
Verified on: ovirt-provider-ovn-1.1-2.20170901074127.gitaaaa5fa.el7.centos.noarch
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.