⚲

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 (ready issues)
QE tools team - backlog (w/o infra)
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 (w/o infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
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 #15926

closed

[sles][functional]fate#320215: Allow full LVM encryption with MSDOS-MBR

Added by okurz over 7 years ago. Updated about 7 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

dzedro

Category:

New test

Target version:

openQA Project - Milestone 6

Start date:

2017-01-13

Due date:

% Done:

100%

Estimated time:

Difficulty:

Description

https://fate.suse.com/320215

History
Notes
Property changes

Actions

Copy link

Updated by maritawerner over 7 years ago

Subject changed from fate#320215: Allow full LVM encryption with MSDOS-MBR to [sles][functional]fate#320215: Allow full LVM encryption with MSDOS-MBR

Actions

Copy link

Updated by okurz over 7 years ago

Target version set to Milestone 5

backlink on fate, inserted myself as QA reviewer. test automation in openQA suggested extending our current coverage to a more mixed variety of partition layouts, MBR/GPT, etc.

Actions

Copy link

Updated by dzedro over 7 years ago

Status changed from New to In Progress
Assignee set to dzedro

Actions

Copy link

Updated by okurz over 7 years ago

Project changed from 46 to openQA Tests
Category set to New test
Target version changed from Milestone 5 to Milestone 5

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2376 merged, please add test suite and provide link to verification run on production instance after passed.

Actions

Copy link

Updated by dzedro over 7 years ago

Status changed from In Progress to Resolved
% Done changed from 0 to 100

PR have been merged, thx to HuHa for detailed test instructions in fate
Test lvm-full-encrypt and related PBI

Actions

Copy link

Updated by okurz over 7 years ago

Status changed from Resolved to In Progress

please see checklist in https://progress.opensuse.org/projects/suseqa/wiki#feature-tests-Fate-requests e.g. add yourself as "QA tester" on the fate entry, link this progress ticket and a reference to the (passing) openQA job

Actions

Copy link

Updated by dzedro over 7 years ago

I added myself as QA tester ...
Why to add passing test when the test is gone after few builds ?

Actions

Copy link

Updated by okurz over 7 years ago

If you add a comment and it is linked to the fate issue and visited at least once from the fate issue (someone sees fate entry, clicks openqa link) then it is considered important and stays for way longer, possibly a year. Also, when you add a link to latest - same as for bug reports based on the reporting template - then it will stay valid.

Actions

Copy link