Project

General

Profile

action #124736

[qe-core] PED-3144 - Y2K38 Epochalypse

Added by szarate 3 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
rfan1
Category:
-
Target version:
QA - QE-Core: Ready
Start date:
2023-03-08
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Difficulty:
Tags:
qe-core-march-sprint

Description

Business reason

See also

https://mailman.suse.de/mlarch/SuSE/research/2023/research.2023.02/msg00063.html

Suggestions

  • Boot an already installed system change the time to few minutes before Y2K38 time, observe
  • Install a system with few minutes before Y2K38 time, and observe (so the installation lands exactly during the moment)
  • Install a system with few minutes after Y2K38 time, and observe (so the installation lands exactly during the moment)
  • Boot an already installed system change the time to few minutes after Y2K38 time, and observe
  • Setup a multi-machine job, where the one that changes the new time is the NTP server.

Subtasks

action #125639: [qe-core] Explore possibilities for a time-shifted test environmentResolvedrfan1

action #127130: [qe-core] Implement a prototype for a time-shifted test environment on TWResolvedrfan1

Related issues

Related to openQA Tests - action #127970: [qe-core][microOS]test fails in year_2038_detectionResolved2023-04-19

History

#1 Updated by szarate 3 months ago

  • Sprint set to QE-Core: March Sprint (Mar 08 - Apr 05)

#2 Updated by ph03nix 3 months ago

  • Status changed from New to Workable

#3 Updated by rfan1 3 months ago

  • Assignee set to rfan1

#4 Updated by rfan1 2 months ago

  • Tracker changed from coordination to action
  • Status changed from Workable to In Progress
  • Boot an already installed system change the time to few minutes before Y2K38 time, observe Done - > I can hit the issue once the time goes to Y2K38 time.
  • Install a system with few minutes before Y2K38 time, and observe (so the installation lands exactly during the moment) N/A -> The latest time I can set is 2031/12/31
  • Install a system with few minutes after Y2K38 time, and observe (so the installation lands exactly during the moment) N/A -> The latest time I can set is 2031/12/31
  • Boot an already installed system change the time to few minutes after Y2K38 time, and observe Done - > I can hit the issue at once if I change the time
  • Setup a multi-machine job, where the one that changes the new time is the NTP server. N/A -> Seems I didn't find a right way to configure a NTP server without sync with internet time

#5 Updated by rfan1 about 2 months ago

  • Status changed from In Progress to Feedback

#6 Updated by szarate about 2 months ago

  • Sprint changed from QE-Core: March Sprint (Mar 08 - Apr 05) to QE-Core: April Sprint 23 (Apr 05 - May 03)

#7 Updated by szarate about 2 months ago

  • Tracker changed from action to coordination
  • Target version set to QE-Core: Ready

#8 Updated by szarate about 2 months ago

  • Status changed from Feedback to Blocked

#9 Updated by rfan1 about 1 month ago

  • Tracker changed from coordination to action
  • Status changed from Blocked to Resolved

#10 Updated by szarate 4 days ago

  • Related to action #127970: [qe-core][microOS]test fails in year_2038_detection added

Also available in: Atom PDF