Project

General

Profile

Actions
Copy link

action #108019

closed

[sle][security][backlog][Leap] Leap 15.4 issue with bash oneliner in oscap_remediating_online (leads to unexpected out)

Added by lkocman almost 3 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
shawnhao
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-03-08
Due date:
% Done:

30%

Estimated time:
24.00 h
Difficulty:

Description

Observation

Hello team,

seems like the oneliner in openscap testing needs bit tweaking it does seem that not all of the out is expected.

openQA test in scenario opensuse-15.4-DVD-aarch64-openscap@aarch64 fails in
oscap_remediating_online

Test suite description

Maintainer: wnereiz.

Test openSCAP tool with an existing disk image.

Reproducible

Fails since (at least) Build 119.3

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by llzhao almost 3 years ago

@lubos.kocman@suse.com I noticed this poo in #discuss-openQA-triage channel, may I ask some questions as some poos are Security QE team's test cases:

  1. Which team is adding Security cases into Leap15.4 job group?
  2. Which team will review these openQA runs?
  3. If opened poos on Leap15.4 which team is fixing them? Thanks in advance.
Actions
Copy link
 #2

Updated by llzhao almost 3 years ago

  • Subject changed from Leap 15.4 issue with bash oneliner in oscap_remediating_online (leads to unexpected out) to [sle][security][sle15sp4][Leap] Leap 15.4 issue with bash oneliner in oscap_remediating_online (leads to unexpected out)
  • Assignee set to shawnhao
  • Estimated time set to 24.00 h
Actions
Copy link
 #3

Updated by lkocman almost 3 years ago

Hello,

so for bugs we do have a security team that handles them, processes audit etc. Johannes Segitz or Marcus meissner would be good point of contact. For issues in this particular queue, I'm not really sure if anybody from security team looks into these. We (or you) can raise it on security team's mailing list.

Hope it helps

Actions
Copy link
 #4

Updated by llzhao almost 3 years ago

lkocman wrote:

Hello,

so for bugs we do have a security team that handles them, processes audit etc. Johannes Segitz or Marcus meissner would be good point of contact. For issues in this particular queue, I'm not really sure if anybody from security team looks into these. We (or you) can raise it on security team's mailing list.

Hope it helps

Thanks for the info, for the progress issues Security QE would like to take/fix currently.

Actions
Copy link
 #5

Updated by openqa_review over 2 years ago

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

This bug is still referenced in a failing openQA test: openscap
https://openqa.opensuse.org/tests/2265402#step/oscap_remediating_online/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
Copy link
 #6

Updated by openqa_review over 2 years ago

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

This bug is still referenced in a failing openQA test: openscap
https://openqa.opensuse.org/tests/2316400#step/oscap_remediating_online/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
Copy link
 #7

Updated by shawnhao over 2 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 30

Currently need more info from Alex.

Actions
Copy link
 #8

Updated by llzhao over 2 years ago

  • Subject changed from [sle][security][sle15sp4][Leap] Leap 15.4 issue with bash oneliner in oscap_remediating_online (leads to unexpected out) to [sle][security][backlog][Leap] Leap 15.4 issue with bash oneliner in oscap_remediating_online (leads to unexpected out)
Actions
Copy link
 #9

Updated by openqa_review over 2 years ago

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

This bug is still referenced in a failing openQA test: openscap
https://openqa.opensuse.org/tests/2362359#step/oscap_remediating_online/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
Copy link
 #10

Updated by openqa_review over 2 years ago

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

This bug is still referenced in a failing openQA test: openscap
https://openqa.opensuse.org/tests/2389275#step/oscap_remediating_online/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
Copy link
 #11

Updated by shawnhao over 2 years ago

  • Status changed from In Progress to Rejected

Our team will no longer be responsible for this poo soon. Please reassign this poo to another if it is necessary to reopen this poo

Actions
Copy link
 #12

Updated by openqa_review over 2 years ago

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

This bug is still referenced in a failing openQA test: openscap
https://openqa.opensuse.org/tests/2389275#step/oscap_remediating_online/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
Copy link

Also available in: Atom PDF