Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1506713 - Update parameter types are not properly passed out on the /v2/catalog API
Update parameter types are not properly passed out on the /v2/catalog API
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker (Show other bugs)
3.7.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 3.7.0
Assigned To: Jason Montleon
Weihua Meng
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-10-26 11:42 EDT by Jason Montleon
Modified: 2017-11-28 17:19 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-28 17:19:38 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-28 21:34:54 EST

  None (edit)
Description Jason Montleon 2017-10-26 11:42:39 EDT
Description of problem:
Update parameters are all appearing as strings

Version-Release number of selected component (if applicable):
ansible-service-broker-1.0.11-1

How reproducible:
Always

Steps to Reproduce:
1. Run catasb and install OCP
2. curl -k -XGET -H "Authorization: Bearer $(oc whoami -t)" -H 'Content-Type: application/json'  https://asb-1338-ansible-service-broker.172.18.0.1.nip.io/ansible-service-broker/v2/catalog

Actual results:
Type for all update params appears as strings

Expected results:
Types are set correctly

Additional info:
Comment 4 Weihua Meng 2017-10-31 03:58:23 EDT
Not in latest image openshift3/ose-ansible-service-broker/images/v3.7.0-0.185.0.0
will check it later.

              "update": {
                "parameters": {
                  "$schema": "http://json-schema.org/draft-04/schema",
                  "additionalProperties": false,
                  "properties": {
                    "postgresql_version": {
                      "default": "9.5",
                      "title": "PostgreSQL Version",
                      "type": "string"
                    }
                  },
                  "required": [
                    "postgresql_version"
                  ],
                  "type": "object"
                }
              }
Comment 5 Jason Montleon 2017-11-02 08:40:06 EDT
Can you recheck this with v3.7.0-0.189.0.0?
Comment 6 Weihua Meng 2017-11-02 08:52:16 EDT
Not in ansible-service-broker-1.0.13-1.el7.x86_64
openshift3/ose-ansible-service-broker:v3.7.0-0.189.0.0

              "update": {
                "parameters": {
                  "$schema": "http://json-schema.org/draft-04/schema",
                  "additionalProperties": false,
                  "properties": {
                    "postgresql_version": {
                      "default": "9.5",
                      "enum": [
                        "9.5",
                        "9.4"
                      ],
                      "title": "PostgreSQL Version",
                      "type": "string"
                    }
                  },
                  "required": [
                    "postgresql_version"
                  ],
                  "type": "object"
                }
              }
Comment 7 Weihua Meng 2017-11-02 08:54:13 EDT
                      "enum": [
                        "9.5",
                        "9.4"
                      ],
means it is fixed, right?
Comment 8 Jason Montleon 2017-11-02 09:04:14 EDT
Correct
Comment 9 Weihua Meng 2017-11-02 09:10:37 EDT
Fixed in ansible-service-broker-1.0.13-1.el7.x86_64
openshift3/ose-ansible-service-broker:v3.7.0-0.189.0.0

Thanks, Jason
Comment 12 errata-xmlrpc 2017-11-28 17:19:38 EST
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://access.redhat.com/errata/RHSA-2017:3188

Note You need to log in before you can comment on or make changes to this bug.