Project

General

Profile

Actions

coordination #175515

open

coordination #102906: [saga][epic] Increased stability of tests with less "known failures", known incompletes handled automatically within openQA

[epic] incomplete jobs with "Failed to find an available port: Address already in use"

Added by okurz about 1 month ago. Updated 27 days ago.

Status:
Blocked
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2024-11-25
Due date:
% Done:

64%

Estimated time:
(Total: 0.00 h)

Subtasks 14 (5 open9 closed)

action #170209: [sporadic] auto_review:"Failed to find an available port: Address already in use":retry, produces incomplete jobs on OSD, multiple machines size:MResolvedmkittler2024-11-25

Actions
action #175464: jobs incomplete with auto_review:"setup failure: isotovideo can not be started"Resolvedokurz2025-01-15

Actions
action #175470: jobs incomplete with auto_review:"setup failure: isotovideo can not be started"Rejectedokurz2025-01-15

Actions
openQA Infrastructure (public) - action #175473: OpenQA Jobs test - Incomplete jobs (not restarted) of last 24h alert SaltResolvedokurz2024-12-19

Actions
action #175482: jobs incomplete with auto_review:"setup failure: isotovideo can not be started" - why did no tests prevent this to be deployed on both o3+osd?Rejectedokurz2025-01-15

Actions
action #175485: jobs incomplete with auto_review:"setup failure: isotovideo can not be started" - why did osd-deployment trigger even though openQA-in-openQA as already showing incompletes? size:SResolvedokurz2025-01-15

Actions
action #175488: jobs incomplete with auto_review:"setup failure: isotovideo can not be started" - unable to login with ssh key on root@kerosene.qe.nue2.suse.orgResolvedtinita2025-01-15

Actions
openQA Infrastructure (public) - action #175494: [openQA][worker][ipmi] isotovideo can not be startedRejected2025-01-15

Actions
action #175518: Conduct "lessons learned" with Five Why analysis for "jobs incomplete with setup failure: isotovideo can not be started" size:SResolvedlivdywan2025-01-24

Actions
action #176139: Make o3 deployments dependant on openQA-in-openQA tests passingNewokurz2025-01-24

Actions
action #176142: Re-consider staging instancesNew2025-01-24

Actions
action #176145: Preserve package cache on worker hostsNewokurz2025-01-24

Actions
action #176148: Ensure https://github.com/openSUSE/Mojo-IOLoop-ReadWriteProcess/ has 100% passing unit tests in CINew2025-01-24

Actions
action #176151: [spike][timeboxed:10h] Explore tooling for checking of deployed versions and bisecting of problematic packages git across multiple repos can tell us what is being usedNewokurz2025-01-24

Actions
Actions #1

Updated by okurz about 1 month ago

  • Subtask #170209 added
Actions #2

Updated by okurz about 1 month ago

  • Subtask #175464 added
Actions #3

Updated by okurz about 1 month ago

  • Subtask #175473 added
Actions #4

Updated by okurz about 1 month ago

  • Subtask #175482 added
Actions #5

Updated by okurz about 1 month ago

  • Subtask #175470 added
Actions #6

Updated by okurz about 1 month ago

  • Subtask #175494 added
Actions #7

Updated by okurz about 1 month ago

  • Subtask #175518 added
Actions #8

Updated by okurz about 1 month ago

  • Subtask #175485 added
Actions #9

Updated by okurz about 1 month ago

  • Subtask #175488 added
Actions #10

Updated by okurz about 1 month ago

  • Status changed from New to Blocked
  • Assignee set to okurz
Actions #11

Updated by livdywan about 1 month ago

  • Subtask #176139 added
Actions #12

Updated by livdywan about 1 month ago

  • Subtask #176142 added
Actions #13

Updated by livdywan about 1 month ago

  • Subtask #176145 added
Actions #14

Updated by livdywan about 1 month ago

  • Subtask #176148 added
Actions #15

Updated by livdywan about 1 month ago

  • Subtask #176151 added
Actions #16

Updated by okurz 27 days ago

  • Target version changed from Ready to future
Actions

Also available in: Atom PDF