⚲

Project

General

Profile

Home
Projects
Help

Search:

openQA Tests

All Projects

openQA Tests

Overview
Activity
Roadmap
Issues
Gantt
Calendar
Wiki

Custom queries

All open Feature tests
openQA Infrastructure Project
openqa-review - Closed tickets last updated by openqa-review, last 30 days
QA roadmap long-term
QA SLE functional
QA SLE Functional - closed in last 14 days
QA SLE Functional - High, need to be refined
QA SLE Functional - over cycle time median
QA SLE u
QA SLE y
QA tools (tag not necessary in openQA and subprojects)
QA tools tag (tag not necessary in openQA and subprojects; excluding tickets in "Ready" version as they are already on the backlog)
QAC - Backlog
QAM
QE tools team - backlog (dev)
QE tools team - backlog (ready issues)
QE tools team - backlog SLA high
QE tools team - backlog SLA immediate
QE tools team - backlog SLA no immediate/urgent in feedback/blocked
QE tools team - backlog SLA normal
QE tools team - backlog SLA urgent
QE tools team - backlog SLO high
QE tools team - backlog SLO normal
QE tools team - backlog SLO urgent
QE tools team - backlog, high-level view (epics and higher)
QE tools team - backlog, non-reactive work, needs parent
QE tools team - backlog, top-level view (all sagas)
QE tools team - closed within last 14 days
QE tools team - closed within last 60 days
QE tools team - closed yesterday
QE Tools Team - Collaborative Session
QE tools team - due date forecast
QE tools team - exceeding due-date
QE tools team - infrastructure backlog
QE tools team - next - sorted by update time
QE tools team - next issues
QE tools team - non-estimated (unblocked) issues (dev)
QE tools team - non-estimated (unblocked) issues (infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - SLO high forecast
QE tools team - update forecast
QE tools team - updated by priority
QE tools team - what members of the team are working on - Feedback (not-low)
QE Tools Team Backlog By Assignee
SLE15 Migration Open Tickets
SLE15 SP1 Migration Open Tickets
SLE15SP3 Migration open ticket
SLE15SP3 Security open ticket
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

Actions

Copy link

action #167260

closed

[security] Do not require FIPS_ENABLED variable for FIPS install tests

Added by emiler about 1 month ago. Updated 26 days ago.

Status:

Resolved

Priority:

Normal

Assignee:

amanzini

Category:

Target version:

Start date:

2024-09-24

Due date:

% Done:

100%

Estimated time:

4.00 h

Difficulty:

Description

Our FIPS install tests now, with a new logic, require FIPS_ENABLED variable set in order to execute fips_setup.pm cleanly. Having this variable on the install tests seems redundant though, since FIPS is not really enabled for the install jobs. Perhaps we could skip this requirement in this case.

If the logic gets changed, we should revert https://gitlab.suse.de/qe-security/osd-sle15-security/-/merge_requests/295 to clean up unused vars.

Related issues 1 (0 open — 1 closed)

Related to openQA Tests - action #167206: [security][x86-64][15-sp{4-6}] test fails in fips_setup: missing FIPS_ENABLED=1

Resolved

emiler

2024-09-24

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by emiler about 1 month ago

Related to action #167206: [security][x86-64][15-sp{4-6}] test fails in fips_setup: missing FIPS_ENABLED=1 added

Actions

Copy link

Updated by amanzini about 1 month ago

Priority changed from Low to Normal

considering also https://suse.slack.com/archives/C044KDGKW58/p1727179296187759 I'm for dropping at least the first variable checks, if not both :)

before the fix, the check was (by mistake) basically a no-op, so a system with FIPS_ENABLED=1 and BOOT_HDD_IMAGE=0 would have FIPS installed. Now these checks prevents it for no real reason.

see also question at https://progress.opensuse.org/issues/167063#note-2

Actions

Copy link

Updated by tjyrinki_suse about 1 month ago

Status changed from New to Workable

Seems correct, as ensure_fips_enabled anyway checks if FIPS was correctly enabled, that failing will instruct enough whether one should allow fips_setup to do the enabling in one's tests or if one should specify FIPS_INSTALLATION parameter to skip the setup and only check FIPS was already enabled by the installation.

Actions

Copy link