Bug 1202433 - No records displayed in "affect Services" table for set retirement dates
Summary: No records displayed in "affect Services" table for set retirement dates
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.6.0
Assignee: Brian McLaughlin
QA Contact: Aziza Karol
URL:
Whiteboard: service:retirement
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-16 15:28 UTC by Aziza Karol
Modified: 2016-06-29 14:52 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-29 14:52:53 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
snapshot (50.57 KB, image/png)
2015-03-16 15:28 UTC, Aziza Karol
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Description Aziza Karol 2015-03-16 15:28:09 UTC
Created attachment 1002363 [details]
snapshot

Description of problem:


Version-Release number of selected component (if applicable):
5.4.0.0.12.20150312013923_aa9b093 

How reproducible:
100%

Steps to Reproduce:
1. Navigate to services->My services
2. select few services and set retirements dates

Actual results:
No records displayed in affected services table. see attached screenshot

Expected results:
affected services should be displayed.

Additional info:

Comment 2 Brian McLaughlin 2016-03-21 20:24:03 UTC
I am unable to reproduce this issue in the latest 5.4.z, 5.5.z or upstream codebases.  Please confirm.

Comment 3 Aziza Karol 2016-04-19 10:23:16 UTC
Records displayed in "affect Services" table for set retirement dates.

Verified:5.6.0.1-beta2.20160413141124_e25ac0e

Comment 5 errata-xmlrpc 2016-06-29 14:52:53 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.

https://access.redhat.com/errata/RHBA-2016:1348


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