Project

General

Profile

Actions

action #32152

closed

[autoyast] verify that filesystem is assigned when <filesystem> tag is not defined

Added by riafarov almost 7 years ago. Updated 10 months ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Target version:
QA (public, currently private due to #173521) - future
Start date:
2018-02-22
Due date:
% Done:

0%

Estimated time:

Description

In autoyast for storage-ng, now missing tag is not a problem, and installer uses filesystem using control.xml file.
For example, for '/' it should be btrfs, as per proposal.

We need to create ay profile with partitioning which doesn't define filesystem for partitions, and verify that expected fs was used.
This also includes /boot, /boot/efi, /boot/zipl partitions.

Actions #1

Updated by okurz almost 7 years ago

  • Target version changed from Milestone 16 to Milestone 17

after GM

Actions #2

Updated by okurz over 6 years ago

  • Subject changed from [sle][functional][yast][autoyast] verify that filesystem is assigned when <filesystem> tag is not defined to [sle][functional][y][yast][autoyast] verify that filesystem is assigned when <filesystem> tag is not defined
Actions #3

Updated by okurz over 6 years ago

  • Target version changed from Milestone 17 to Milestone 21+
Actions #4

Updated by okurz over 6 years ago

  • Target version changed from Milestone 21+ to Milestone 21+
Actions #5

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 21+ to future
Actions #6

Updated by riafarov about 4 years ago

  • Project changed from openQA Tests (public) to qe-yam
  • Subject changed from [sle][functional][y][yast][autoyast] verify that filesystem is assigned when <filesystem> tag is not defined to [autoyast] verify that filesystem is assigned when <filesystem> tag is not defined
  • Category deleted (New test)
Actions #7

Updated by okurz about 3 years ago

  • Priority changed from Normal to Low

This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. The ticket will be set to the next lower priority of "Low" as discussed with qe-yast PO oorlov (https://suse.slack.com/archives/C02LECV2R0X/p1636974668013200)

Actions #8

Updated by JERiveraMoya 10 months ago

  • Status changed from New to Rejected

Backlog clean-up.

Actions

Also available in: Atom PDF