Uploaded image for project: 'Cost Management'
  1. Cost Management
  2. COST-848

Forecasting api returns predictions for incorrect days

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • 2021Q1
    • None
    • API
    • None
    • False
    • False
    • Undefined
    • COST Sprint 59

      Date used by forecasting seems to be "frozen" - it is equal to the date of the last commit to the project in CI, or date of starting the koku/masu container in case of local testing. if these dates are not equal to today, api returns forecasts for past days. For example, today is 2021-01-04, thus api should return forecasts from 2021-01-04 to 2021-01-31. But since the last commit to the project was 17 days ago, forecasting uses 2020-12-22 as today and api returns forecasts from 2020-12-22 to 2020-12-31. Consequently, forecast is not displayed in UI as there are no forecasting data available for January.

              blentz@redhat.com Brett Lentz (Inactive)
              rhn-support-esebesto Eva Šebestová
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: