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:
Will investigate in next sprint.
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
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