Bug 1695219

Summary: service provisioned with retirement_warn_offset_days sets the retirement_warn field as an integer : "1554310357"
Product: Red Hat CloudForms Management Engine Reporter: drew uhlmann <duhlmann>
Component: AutomateAssignee: drew uhlmann <duhlmann>
Status: CLOSED ERRATA QA Contact: Tasos Papaioannou <tpapaioa>
Severity: medium Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: medium    
Version: 5.10.0CC: dmetzger, gmccullo, mkanoor, mshriver, obarenbo, simaishi
Target Milestone: GAKeywords: Reopened
Target Release: 5.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.11.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-12 13:36:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dialog with retirement fields none

Description drew uhlmann 2019-04-02 16:38:03 UTC
Created attachment 1551084 [details]
dialog with retirement fields

Description of problem:
Service prov'd with dialog that has service_retires_in_days and retirement_warn_offset_days will provision service without the retirement_warn field set

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

How reproducible:


Steps to Reproduce:
1. provision service with attached dialog
2. 
3.

Actual results:
retirement_warn date isn't set

Expected results:
retirement_warn date should be set

Additional info:

Comment 2 drew uhlmann 2019-04-02 16:51:43 UTC
Nope just kidding. I can't name things right. Closing cause the issue is with the field naming on the dialog. Sorry people. Move along. Nothing to see here.

Comment 3 drew uhlmann 2019-04-02 16:54:18 UTC
The real bug is that the field value looks like this:  retirement_warn: 1554310357 which I'll open a ticket for in a minute.

Comment 4 Dave Johnson 2019-04-02 18:01:12 UTC
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set the severity to Low.

Comment 5 Dave Johnson 2019-04-02 20:01:11 UTC
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set the severity to Low.

Comment 6 drew uhlmann 2019-04-22 14:02:49 UTC
https://github.com/ManageIQ/manageiq/pull/18637

Comment 7 Tasos Papaioannou 2019-04-30 18:55:38 UTC
Verified on 5.11.0.1.

Comment 9 errata-xmlrpc 2019-12-12 13:36:21 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-2019:4199