Bug 1406910 - SSUI lets you save a retirement date from the past
Summary: SSUI lets you save a retirement date from the past
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - Service
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: 5.8.0
Assignee: Josh Langholtz
QA Contact: Nandini Chandra
URL:
Whiteboard: ssui
Depends On:
Blocks: 1414583
TreeView+ depends on / blocked
 
Reported: 2016-12-21 19:51 UTC by Nandini Chandra
Modified: 2017-06-12 16:16 UTC (History)
5 users (show)

Fixed In Version: 5.8.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1414583 (view as bug list)
Environment:
Last Closed: 2017-06-12 16:16:28 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)
screen shot of service with past retirement date (51.03 KB, image/png)
2016-12-21 19:51 UTC, Nandini Chandra
no flags Details

Description Nandini Chandra 2016-12-21 19:51:13 UTC
Created attachment 1234475 [details]
screen shot of service with past retirement date

Description of problem:
-----------------------
SSUI lets you save a retirement date from the past.
See attached screen shot.The service was created on Dec 15, 2016.It let me save Dec 11, 2016 as the Retirement date.


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


How reproducible:
-----------------
Always


Steps to Reproduce:
-------------------
1.Provision a service on SSUI.
2.Select the service from 'My Services'.
3.Click the 'Retire' button.Then click 'Schedule Retirement'. Select a date from the past.


Actual results:
---------------
SSUI lets you save a retirement date from the past.


Expected results:
-----------------
SSUI should not allow you to save a retirement date from the past.

Additional info:
----------------

Comment 2 Chris Kacerguis 2016-12-21 19:53:00 UTC
Didn't we already fix this here:

https://github.com/ManageIQ/manageiq-ui-service/pull/336

Comment 3 Nandini Chandra 2016-12-21 19:56:16 UTC
I just noticed that the service got retired a few minutes after I accidentally set a retirement date from the past and I don't intend to retire the service :).

Setting the severity to High.

Comment 4 Chris Kacerguis 2016-12-21 20:21:46 UTC
Regarding below, that's the expected behavior.  The system sees that the retirement date has passed, and so it shuts off the service.  I think the real issue is that it was allowed to be set in the past (which we had fixed, but not sure either (1) it got back ported, or (2) you are testing with the latest version.

(In reply to Nandini Chandra from comment #3)
> I just noticed that the service got retired a few minutes after I
> accidentally set a retirement date from the past and I don't intend to
> retire the service :).
> 
> Setting the severity to High.

Comment 5 Josh Langholtz 2017-01-16 14:52:36 UTC
Chris is correct, this was fixed but not backported:
https://github.com/ManageIQ/manageiq-ui-service/pull/336

Backporting that commit will fix the issue.

Comment 7 Nandini Chandra 2017-03-15 20:34:34 UTC
Verified in 5.8.0.4


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