Bug 1610685
Summary: | Service Dialog CheckBox has null value when not ticked by default | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Nikhil Gupta <ngupta> | ||||
Component: | Automate | Assignee: | drew uhlmann <duhlmann> | ||||
Status: | CLOSED ERRATA | QA Contact: | Shveta <sshveta> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 5.9.3 | CC: | abellott, dmetzger, duhlmann, mkanoor, obarenbo, simaishi, smallamp, tfitzger | ||||
Target Milestone: | GA | Keywords: | ZStream | ||||
Target Release: | 5.9.4 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | 5.9.4.4 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2018-09-04 18:01:40 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Nikhil Gupta
2018-08-01 08:20:34 UTC
@Nikhil, could you please tell me if this is a regression? This works on master, and it also works if you set the field to have a default value of false. @Nikhil! Sorry about this, but could you please retest this on your appliance? I have a one line change made on that system in app/models/dialog_field_check_box.rb. I am seeing ==================== <AEMethod dialog_parser> dialog_options: {"dialog_check_box_1"=>nil, "dialog_textarea_box_1"=>"", "request"=>"clone_to_service", :service_action=>"Provision", "Service::Service"=>6} ========================= When the checkbox is not set to any value . It shows "nil " Is it supposed to show 'f' as stated in the issue ? Appliance : https://10.8.199.142 Service : catalog_item Hey Shveta. So the original bug for which this ticket was filed was about the backend code not setting the value correctly. The issue I'm seeing on your appliance is a different issue. I verified originally that the API payload had the right value -- f, just like you mentioned -- but on your appliance for some reason, the API isn't showing the same thing. Since Nikhil confirmed that my fix worked for the issue he was seeing, can you please verify this ticket and reopen a similar ticket on the API? You can assign that ticket to me, that's fine, but I'd like to be very clear that these are separate issues. Looking into the API issue further, I think you'll find that if you try to submit the dialog without changing the checkbox at all, the API payload doesn't even list the checkbox as a field. Created attachment 1477871 [details]
unrelated API issue -- payload without checkbox
Verifying based on above comment and opening new BZ for API issue https://bugzilla.redhat.com/show_bug.cgi?id=1620208 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-2018:2561 |