Bug 1509664
| Summary: | Token creation results in HTTP code 201 where it should be 200 (for CFME) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-provider-ovn | Reporter: | Mor <mkalfon> | ||||
| Component: | provider | Assignee: | Dominik Holler <dholler> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mor <mkalfon> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 1.0.4 | CC: | alkaplan, bugs, danken, ylavi | ||||
| Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
|
||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | ovirt-provider-ovn-1.2-0.20171110095842.git22bbb0d.el7.centos.noarch.rpm | Doc Type: | No Doc Update | ||||
| Doc Text: |
undefined
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-12-20 10:52:36 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Isn't this a bug in CFME? Created attachment 1348170 [details]
logs
According to https://developer.openstack.org/api-ref/identity/v2/index.html#authenticate , OpenStack Identity API v2.0 specifies HTTP 200 as return code for successful token creation, so CFME seems to be right and the provider has to be changed. Verified on: ovirt-provider-ovn-1.2-0.20171110095842.git22bbb0d.el7.centos.noarch Logging: 2017-11-14 08:44:44,792 Starting new HTTPS connection (1): network-ge-2.scl.lab.tlv.redhat.com 2017-11-14 08:44:49,844 "POST /ovirt-engine/sso/oauth/token-info HTTP/1.1" 200 324 2017-11-14 08:44:49,850 Response code: 200 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. |
Description of problem: When creating a token the provider returns 201 ('Created') where it should return 200 ('OK') in order to support CFME connections. Version-Release number of selected component (if applicable): Version 4.2.0-0.0.master.20171103160151.gitcf446d9.el7.centos ovirt-provider-ovn-1.2-0.20171102153014.git7bfd256.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. Send a valid token request to the provider. 2. Get a response. Actual results: Provider returns HTTP code 201. Expected results: Provider should return HTTP code 200. Additional info: