Project

General

Profile

Actions

action #137666

open

[security] Installation_ntlm_s390x_zkvm doesn't boot in any product

Added by JERiveraMoya 7 months ago. Updated 2 months ago.

Status:
Blocked
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2023-10-10
Due date:
% Done:

0%

Estimated time:
8.00 h
Difficulty:
Tags:

Description

Observation

This test suite doesn't really boot in any product, we need to compare with similar test suite if any and distinguish if it one of those s390x problem that recently hit us (perhaps not, because same issue was seen a lot of time ago in another QU build) or it is related with misconfiguration.

QU SLE 15 SP5: https://openqa.suse.de/tests/12426768#step/bootloader_start/40
QU SLE 15 SP4: https://openqa.suse.de/tests/11657277#step/bootloader_start/40
Product: https://openqa.suse.de/tests/12426861#step/bootloader_start/40


Related issues 1 (0 open1 closed)

Related to openQA Tests - action #138488: [qe-core] Create production proxy connected to QE-Core AD server to allow ntlm authorization for installations from openQAResolvedrfan12023-10-25

Actions
Actions #1

Updated by tjyrinki_suse 7 months ago

  • Status changed from New to Workable
Actions #2

Updated by JERiveraMoya 7 months ago

  • Status changed from Workable to In Progress
  • Assignee set to JERiveraMoya
Actions #3

Updated by JERiveraMoya 7 months ago

  • Related to action #138488: [qe-core] Create production proxy connected to QE-Core AD server to allow ntlm authorization for installations from openQA added
Actions #4

Updated by JERiveraMoya 7 months ago

  • Status changed from In Progress to Blocked
  • Assignee deleted (JERiveraMoya)

Blocked by #138488
(see description of this ticket for the investigation)

Actions #5

Updated by openqa_review 6 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: installation_ntlm_
https://openqa.suse.de/tests/11657277#step/bootloader_start/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions #6

Updated by openqa_review 5 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: installation_ntlm_
https://openqa.suse.de/tests/12842120#step/bootloader_start/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.

Actions #7

Updated by openqa_review 3 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: installation_ntlm_
https://openqa.suse.de/tests/11657277#step/bootloader_start/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 112 days if nothing changes in this ticket.

Actions #8

Updated by tjyrinki_suse 2 months ago

  • Estimated time set to 8.00 h
Actions

Also available in: Atom PDF