Description of problem: When using the customize request method (either amazon_customizerequest or openstack_customizerequest) from the RedHat domain and passing the security_group name as part of additional values Version-Release number of selected component (if applicable): 5.6 How reproducible: Always Steps to Reproduce: 1. Copy the "customize request" method to a writable domain and modify the mapping setting from mapping = 0 to mapping = 1. 2. Create a REST API call to provision an Amazon or OpenStack instance and pass the "security_group" value with the name in "additional_values" that you want to apply. 3. Check the request that was created and verify that the security group was not applied. Actual results: Specified security group is ignored. Expected results: Specified security group gets set. Additional info: Additional details https://bugzilla.redhat.com/show_bug.cgi?id=1297335#c18 The script from https://github.com/ManageIQ/manageiq/pull/8425 can be used to help build the Rest API call for provisioning. This can be corrected by changing: prov.set_option(:security_groups, [securitygroup.name]) to prov.set_option(:security_groups, [securitygroup.id])
New commit detected on cfme_productization/master: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme_productization.git;a=commit;h=169d47708dd133eb95be957ad7e4564cc0cdfc10 commit 169d47708dd133eb95be957ad7e4564cc0cdfc10 Author: william fitzgerald <wfitzger> AuthorDate: Mon May 22 17:45:24 2017 -0400 Commit: william fitzgerald <wfitzger> CommitDate: Mon May 22 17:45:24 2017 -0400 Automate - Changed security_groups to id in 2 custom request methods. Changed to "securitygroup.id" for both methods. https://bugzilla.redhat.com/show_bug.cgi?id=1335989 .../StateMachines/Methods.class/__methods__/amazon_customizerequest.rb | 2 +- .../Methods.class/__methods__/openstack_customizerequest.rb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
Verified in 5.9.0.5
*** Bug 1547249 has been marked as a duplicate of this bug. ***
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:0380