Bug 1500951

Summary: Can't Save Role when Enabling All Product Features for Ansible folder of a CloudForms Role
Product: Red Hat CloudForms Management Engine Reporter: myoder
Component: UI - OPSAssignee: lgalis
Status: CLOSED ERRATA QA Contact: Landon LaSmith <llasmith>
Severity: medium Docs Contact:
Priority: high    
Version: 5.8.0CC: cpelland, hkataria, jhardy, llasmith, mpovolny, obarenbo, simaishi
Target Milestone: GAKeywords: ZStream
Target Release: 5.8.4   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-25 14:17:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Ansible
Bug Depends On:    
Bug Blocks: 1551709    
Description Flags
ansible_role none

Description myoder 2017-10-11 20:02:54 UTC
Created attachment 1337409 [details]

Description of problem:
When editing the product features of a role, if you select the check box for the Ansible folder under Automation (Automation => Ansible) you are unable to save.  If you select the Ansible folder (so everything beneath is selected) you can remove a check box anywhere (including any box underneath the Ansible folder) and you will then be able to save the role.

Version-Release number of selected component (if applicable):
Seeing this on 5.8.0,

How reproducible:

Steps to Reproduce:
1. Create or copy a role
2. Edit the role
3. Select the checkbox next to the Ansible folder

Actual results:
Save button is grayed out and user cannot save.

Expected results:
Save button should be blue, and user should be able to save.

Additional info:
Attaching a video showing the bug

Comment 5 Landon LaSmith 2018-04-19 16:13:51 UTC
VERIFIED in I was able to enable the Automation->Ansible role and save the changes.

Comment 7 errata-xmlrpc 2018-06-25 14:17:08 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.