Bug 1833222

Summary: Metering Report YAML still has old starting and ending date
Product: OpenShift Container Platform Reporter: Yadan Pei <yapei>
Component: Management ConsoleAssignee: Zac Herman <zherman>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: medium    
Version: 4.5CC: aos-bugs, jokerman, yapei
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:36:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yadan Pei 2020-05-08 05:53:18 UTC 
Description of problem:
metering Report example yaml still use old start date 2019-01-01T00:00:00Z and end date 2019-12-30T23:59:59Z

Version-Release number of selected component (if applicable):
4.5.0-0.nightly-2020-05-07-144853

How reproducible:
Always

Steps to Reproduce:
1. admin user subscribe metering operator
2. Administration -> Chargeback -> click on 'Create Report' button


Actual results:
2. example YAML is 
apiVersion: metering.openshift.io/v1
kind: Report
metadata:
  name: namespace-memory-request
  namespace: openshift-metering
spec:
  query: namespace-memory-request
  reportingStart: '2019-01-01T00:00:00Z'
  reportingEnd: '2019-12-30T23:59:59Z'
  runImmediately: true


Expected results:
reportingStart should be '2020-01-01T00:00:00Z' and reportingEnd should be '2020-12-30T23:59:59Z'

Additional info:
Comment 1 Zac Herman 2020-05-08 21:55:13 UTC 
Will investigate in next sprint.
Comment 4 Yadan Pei 2020-05-13 02:33:34 UTC 
Now the metering report YAML is 

apiVersion: metering.openshift.io/v1
kind: Report
metadata:
  name: namespace-memory-request
  namespace: openshift-metering
spec:
  query: namespace-memory-request
  reportingStart: '2020-01-01T00:00:00Z'
  reportingEnd: '2020-12-31T23:59:59Z'
  runImmediately: true

Verified on 4.5.0-0.nightly-2020-05-12-195228
Comment 5 errata-xmlrpc 2020-07-13 17:36:10 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-2020:2409