Bug 1449624 - Retirement tab is not shown for retired service if "Copy from Provisioning" was pressed
Summary: Retirement tab is not shown for retired service if "Copy from Provisioning" w...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.8.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: GA
: 5.9.0
Assignee: Harpreet Kataria
QA Contact: Dmitry Misharov
URL:
Whiteboard: ansible:ui:automate
Depends On: 1501143 1503438 1506796
Blocks: 1449810
TreeView+ depends on / blocked
 
Reported: 2017-05-10 11:37 UTC by Dmitry Misharov
Modified: 2018-03-06 14:39 UTC (History)
7 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1449810 (view as bug list)
Environment:
Last Closed: 2018-03-06 14:39:03 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screen shot showing retirement tab remove resources option. (35.84 KB, image/png)
2017-05-10 17:40 UTC, Tina Fitzgerald
no flags Details

Description Dmitry Misharov 2017-05-10 11:37:00 UTC
Description of problem:
Retirement tab is not shown for retired service if "Copy from Provisioning" was pressed during filling retirement tab in catalog item

Version-Release number of selected component (if applicable):
5.8.0.14-rc3.20170509175238_5dbf87a

How reproducible:
Always

Steps to Reproduce:
1. Enable Embedded Ansible role.
2. Wait until it will be enabled.
3. Navigate to Automation/Ansible.
4. Add some credential and repository with ansible playbook.
5. Navigate to Services/Catalogs/Catalog Items.
6. Create a catalog item, fill retirement tab using "Copy from Provisioning" button.
7. Provision a service from the catalog item.
8. Perform service retirement.

Actual results:
Retirement tab is missing.

Expected results:
Retirement tab should be shown.

Comment 3 Tina Fitzgerald 2017-05-10 17:37:36 UTC
The reason the retirement tab is not showing is because the Service has the wrong retirement entry point.

It's using a retired_basic retirement instance instead of a retired_advanced instance.

Comment 4 Tina Fitzgerald 2017-05-10 17:40:46 UTC
Created attachment 1277671 [details]
Screen shot showing retirement tab remove resources option.

Comment 5 Tina Fitzgerald 2017-05-10 17:44:36 UTC
The attached screen shot shows the Remove Resources value of "Yes" which is not a valid choice for a Service Catalog Item with a retirement playbook.

Comment 6 lgalis 2017-05-10 18:29:35 UTC
This PR is required https://github.com/ManageIQ/manageiq-ui-classic/pull/1246

Comment 8 Dmitry Misharov 2017-11-03 08:29:38 UTC
Fixed and verified in 5.9.0.5.20171102023815_209f732.


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