Bug 1995147 - [RFE] provide option to define date in the past to which a cost model change becomes applied in the cost numbers
Summary: [RFE] provide option to define date in the past to which a cost model change ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Hybrid Cloud Console (console.redhat.com)
Classification: Red Hat
Component: Cost Management
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Kevan Holdaway
QA Contact: luke couzens
Karie
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-18 14:19 UTC by bernd.himmelsbach.ext
Modified: 2021-10-20 13:30 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-20 13:30:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description bernd.himmelsbach.ext 2021-08-18 14:19:25 UTC
Description of problem:
when updating a cost model, the cost numbers become only updated back to the first of the current month

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


Steps to Reproduce:
1. open cost models page, select/open a cost model
2.change a cost models rate from Metric = CPU & Measurement = Request (core-hours) to Metric = memory & Measurement = Request (GB-hours) 


Actual results:
numbers in cost explorer do only get updated with the results of the changed cost model until the 1st of the current month.


Expected results/behavior:
when changing a cost model an additional dialog should appear which allows to define a date in the past (a date before the first of the current month)  until which the cost data should get updated with the new cost model rule set/calculations

Comment 2 aaiken 2021-10-20 13:30:35 UTC
Hey Bernd, 

We opened up a JIRA ticket to evaluate this RFE at https://issues.redhat.com/browse/COST-1992. Feel free to follow along to track any updates.


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