Bug 1501143 - Remove resources field is always saved with Yes in Ansible Playbook catalog item
Summary: Remove resources field is always saved with Yes in Ansible Playbook catalog item
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.9.0
Hardware: All
OS: All
high
high
Target Milestone: GA
: cfme-future
Assignee: Harpreet Kataria
QA Contact: Kedar Kulkarni
URL:
Whiteboard: ansible:service:ui
Depends On:
Blocks: 1437945 1438846 1439667 1449624
TreeView+ depends on / blocked
 
Reported: 2017-10-12 07:14 UTC by Dmitry Misharov
Modified: 2018-02-08 19:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-03 08:44:22 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:
kkulkarn: automate_bug+

Attachments (Terms of Use)

Description Dmitry Misharov 2017-10-12 07:14:04 UTC 
Description of problem:
It's not possible to have "Remove resources?" field with "No" value in Ansible Playbook catalog item


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

How reproducible:
Always

Steps to Reproduce:
1. Open creation screen of Ansible Playbook catalog item.
2. Fill required fields.
3. Open Retirement tab.
4. Fill "Remove resources?" field with "No" value.
5. Press "Save" button.

Actual results:
In details screen of the catalog item "Remove resources?" has "Yes".

Expected results:
"Remove resources" should have correct value.
Note You need to log in before you can comment on or make changes to this bug.