Bug 1361310 - Service retirement does not work from service details page
Summary: Service retirement does not work from service details page
Keywords:
Status: CLOSED DUPLICATE of bug 1344678
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.7.0
Assignee: Harpreet Kataria
QA Contact: Niyaz Akhtar Ansari
URL:
Whiteboard: service:retirement
Depends On:
Blocks: 1361690
TreeView+ depends on / blocked
 
Reported: 2016-07-28 18:30 UTC by Jeff Warnica
Modified: 2020-06-26 16:40 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1361690 (view as bug list)
Environment:
Last Closed: 2016-08-05 17:06:19 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jeff Warnica 2016-07-28 18:30:13 UTC 
Description of problem:

Service retirement does not work from service details page


How reproducible:
always

Steps to Reproduce:
1. Navigate to a service from /service/explorer in the classic UI
2. Lifecycle->Retire

Actual results:
"No services were selected for retire" displayed


Expected results:
Retirement begins

Additional info:
Retirement does seem to happen if one ore multiple services are selected from the list, and Lifecycle->Retire is triggered.
Comment 3 Jeff Warnica 2016-08-03 14:42:21 UTC 
The same problem happens with instance retirement. I guess this is the same layout and code so it makes sense it also fails.
Comment 4 Harpreet Kataria 2016-08-04 16:31:26 UTC 
Jeff,

Can you provide build information and if possible can i access your appliance to try and recreate the issue. This is not recreatable on upstream locally.

Thanks,
~Harpreet
Comment 5 Harpreet Kataria 2016-08-05 17:06:19 UTC 
This issue has already been fixed with fix for 
https://bugzilla.redhat.com/show_bug.cgi?id=1344678
https://bugzilla.redhat.com/show_bug.cgi?id=1349989

Thanks,
~Harpreet

*** This bug has been marked as a duplicate of bug 1344678 ***
Note You need to log in before you can comment on or make changes to this bug.