yahoo-eng-team team mailing list archive

[Santiago Baldassin <santiago.b.baldassin@xxxxxxxxx>]

I'm not sure we want to fix this one. The uptime is displayed that way because we are applying a "time_since" filter to the "created_at" field returned by nova. We are not changing the value at all, just displaying it in a more user friendly way. Bottom line, metering and billing should be ok.
Maybe we could stop applying the filter so no matter what the user does with the system time settings, the column will always displayed the value returned by nova, but again...I would not fix this one :)

** Changed in: horizon
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1322952

Title:
  Uptime in Overview and Instance tab change if system time changes.

Status in OpenStack Dashboard (Horizon):
  Opinion

Bug description:
  If the system time of server running Horizon is changed, the uptime of
  instances in overview and instances tab change accordingly.

  Steps to Reproduce

  1) Launch an instance and leave it for few minutes.
  2) Check if uptime is changed.
  3) Log in to the server where horizon is started and change the time.
  4) Scenario 1: Change it backward by few minutes but not less than the total uptime at the moment.
       Eg: If current uptime is 1 hour, decrease the time by 30 minutes only.
       The uptime is shows 30 minutes after refreshing the page.
  5) Scenario 2: Change it backward by few minutes greater than the total uptime at the moment.
       Eg: If current uptime is 1 hour, decrease the time by 2 hour 30 minutes.
       The uptime shows 0 minutes in instances page and sometimes instance disappears from overview page.
  6) Scenario 3: Change it forward by few minutes.
       Eg: If current uptime is 1 hour, increase the time by 30 minutes only.
       uptime is modified to 1 hour 30 minutes.

  The above mentioned bug may affect the metering and billing if uptime is considered for calculation
  Scenario 3 (By some mistake if system time is modified to future) can infact affect the end users by overcharging them, which would break the SLA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1322952/+subscriptions