Bug 1594015 - Non-required Dialog Field Returns Required in API POST
Summary: Non-required Dialog Field Returns Required in API POST
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.9.6
Assignee: eclarizi
QA Contact: Parthvi Vala
URL:
Whiteboard:
Depends On:
Blocks: 1595269 1622587
TreeView+ depends on / blocked
 
Reported: 2018-06-21 21:10 UTC by Saif Ali
Modified: 2022-03-13 15:09 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-12-05 15:22:01 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Saif Ali 2018-06-21 21:10:28 UTC
Description of problem:
The attached dialog is for a service request. Upon adding the 'template_info' field, the API request now returns the below error if the field is not included:

{"error"=>{"kind"=>"bad_request", "message"=>"Failed to order Service Template id:12 name:'DEV VMware Provision' - VMware Server/VM Information/Template Information is required", "klass"=>"Api::BadRequestError"}}


Version-Release number of selected component (if applicable):
5.9

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Saif Ali 2018-06-21 21:13:38 UTC
Version: 5.8.2.3

Comment 7 eclarizi 2018-09-17 18:39:05 UTC
Is this still a problem in the latest 5.9.z?

Comment 18 dmetzger 2018-10-10 15:42:26 UTC
Moving to 5.9.6, need a reproducer environment before development can move further on this ticket.

Comment 21 Sudhir Mallamprabhakara 2018-10-26 14:08:35 UTC
Parthvi - Can you try to re-create this and provide a env for Dev pls?

Comment 25 Parthvi Vala 2018-10-31 08:01:36 UTC
Hey Erik, I tested again on the same appliance, and it works fine.

You mentioned you made some changes to the appliance, what changes did you make? Because I tried sending the request in a fresh appliance and got the same errors.

And even I can't seem to reproduce the error mentioned in the original comment.

Comment 26 eclarizi 2018-10-31 19:33:04 UTC
I basically changed the code to reflect the changes I made in https://github.com/ManageIQ/manageiq-api/pull/504.

At this point I would like to know if the customer is still experiencing this issue, and maybe I can get on a customer call with them and support to see this first-hand. Otherwise, simply upgrading after a 5.9 release is cut that includes the above PR should fix the issue.


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