Bug 1352011 - Cannot specify security_protocol when creating a cloud provider via the API
Summary: Cannot specify security_protocol when creating a cloud provider via the API
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: API
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.6.1
Assignee: Šimon Lukašík
QA Contact: Martin Kourim
URL:
Whiteboard: provider:add:rest
Depends On: 1351253
Blocks: RHCS-CFME
TreeView+ depends on / blocked
 
Reported: 2016-07-01 12:13 UTC by John Prause
Modified: 2022-07-09 07:46 UTC (History)
6 users (show)

Fixed In Version: 5.6.1.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1351253
Environment:
Last Closed: 2016-08-18 17:53:57 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1634 0 normal SHIPPED_LIVE Important: CFME 5.6.1 security, bug fix, and enhancement update 2016-08-18 21:43:52 UTC

Comment 3 Šimon Lukašík 2016-07-14 13:05:06 UTC 
This has been darga/backported (https://github.com/ManageIQ/manageiq/pull/9570) moving to POST.
Comment 6 Martin Kourim 2016-07-28 14:01:57 UTC 
Verified by successfully creating a cloud provider via the API while specifying the security_protocol:

{
  "name" : "openstack test",
  "type" : "ManageIQ::Providers::Openstack::CloudManager",
  "hostname" : "x.x.x.x",
  "ipaddress" : "x.x.x.x",
  "security_protocol" : "ssl",
  "credentials" :  {
    "userid" : "id",
    "password" : "password"
  }
}
Comment 8 errata-xmlrpc 2016-08-18 17:53:57 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-1634.html
Note You need to log in before you can comment on or make changes to this bug.