Project

General

Profile

Actions
Copy link

action #124736

closed

[qe-core] PED-3144 - Y2K38 Epochalypse

Added by szarate about 2 years ago. Updated over 1 year ago.

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

100%

Estimated time:
(Total: 0.00 h)
Difficulty:
Sprint:
QE-Core: April Sprint 23 (Apr 05 - May 03)
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 2 (0 open — 2 closed)

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

Actions
action #127130: [qe-core] Implement a prototype for a time-shifted test environment on TWResolvedrfan12023-03-08

Actions

Related issues 2 (0 open — 2 closed)

Related to openQA Tests (public) - action #127970: [qe-core][microOS]test fails in year_2038_detectionResolvedrfan12023-04-19

Actions
Copied to openQA Tests (public) - action #162002: [qe-core] PED-3144 - Y2K38 Epochalypse - run on Tumbleweed with extra testsResolvedrfan12023-03-08

Actions
Actions
Copy link
 #1

Updated by szarate about 2 years ago

  • Sprint set to QE-Core: March Sprint (Mar 08 - Apr 05)
Actions
Copy link
 #2

Updated by ph03nix about 2 years ago

  • Status changed from New to Workable
Actions
Copy link
 #3

Updated by rfan1 about 2 years ago

  • Assignee set to rfan1
Actions
Copy link
 #4

Updated by rfan1 about 2 years 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
Actions
Copy link
 #5

Updated by rfan1 about 2 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #6

Updated by szarate about 2 years ago

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

Updated by szarate about 2 years ago

  • Tracker changed from action to coordination
  • Target version set to QE-Core: Ready
Actions
Copy link
 #8

Updated by szarate about 2 years ago

  • Status changed from Feedback to Blocked
Actions
Copy link
 #9

Updated by rfan1 about 2 years ago

  • Tracker changed from coordination to action
  • Status changed from Blocked to Resolved
Actions
Copy link
 #10

Updated by szarate almost 2 years ago

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

Updated by xgonzo over 1 year ago

szarate wrote:

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.

Have you thought about setting up cron jobs for a time after Y2K38?

Maybe blog of Thorsten Kukuk provides some more ideas for testing:
https://www.thkukuk.de/blog/Y2038_glibc_utmp_64bit/

Actions
Copy link
 #12

Updated by szarate over 1 year ago

xgonzo wrote in #note-11:

szarate wrote:

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.

Have you thought about setting up cron jobs for a time after Y2K38?

Maybe blog of Thorsten Kukuk provides some more ideas for testing:
https://www.thkukuk.de/blog/Y2038_glibc_utmp_64bit/

We will follow up with the Year 2037 too :)

Actions
Copy link
 #13

Updated by jstehlik 11 months ago

  • Copied to action #162002: [qe-core] PED-3144 - Y2K38 Epochalypse - run on Tumbleweed with extra tests added
Actions
Copy link

Also available in: Atom PDF