Bug 8339 - "Last updated" field in load shows incorrect value if more than a day
Summary: "Last updated" field in load shows incorrect value if more than a day
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Misc (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.17.0
Assignee: Frida Flodin
URL:
Keywords: prosaic, tobfa_tester
Depends on:
Blocks:
 
Reported: 2024-04-24 14:52 CEST by Frida Flodin
Modified: 2024-04-25 16:10 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:
MUST: - 'Last updated' in tlctl load and tlwebadm status/load must display proper values and units.

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Frida Flodin cendio 2024-04-24 14:52:43 CEST 
If an agent has not been updated for over a day it will start over and count from 0. In other words, the maximum seconds we show is 86399. This is true for both "tlctl load show" and on the status page in webadmin.
Comment 1 Frida Flodin cendio 2024-04-24 14:54:09 CEST 
This was fixed with bug 8253.
Comment 2 Tobias cendio 2024-04-25 16:10:54 CEST 
General
=======
Tested this bug using server builds #3552 (pre-fix) and #3566 (post-fix) on
Fedora 40.

These time attributes being tested here should never exhibit values beyond 40
seconds. Testing this bug therefor requires forcing a fictitious time difference
in some manner. This was achieved by simply altering the timestamp in the code
to represent a time greater than 24h.

In the pre-fix build, the 'Last updated' value in tlctl load and tlwebadm
status/load indeed wraps around after 24h and begins from zero. Conversely, in
the post-fix build, this value correctly transitions to 'day' units after 24h.

Acceptance criteria
===================
MUST:
> 'Last updated' in tlctl load and tlwebadm status/load must display proper values and units.
✅ They are.

Conclusion
==========

Working as intended, with AC fulfilled.

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