Project

General

Profile

action #11442

Feature 317970: Remove creation of autoyast profile during installation

Added by maritawerner about 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Start date:
2016-04-01
Due date:
% Done:

100%

Estimated time:
Difficulty:
Duration:

Description

For details see https://fate.suse.com/317970

Feature status is "done".

With SLES10/SLES11, we did create an autoyast profile at the end of the installation. With both products doing a full system configuration during installation, this did made sense.

With SLES12, most things are no longer configureable during installation and we suggest to the customer to configure it later in the running system. So a lot of config entries are missing from this autoyast profile. And the resulting autoyast profile is different then if you create it later in the running system.

Thus we should stop creating the autoyast profile during installation and only concentrate on doing it later in the running system.

History

#1 Updated by mkravec about 4 years ago

  • Assignee set to mkravec

#2 Updated by RBrownSUSE about 4 years ago

  • Target version set to 168

#3 Updated by okurz about 4 years ago

  • Target version changed from 168 to Milestone 3

#4 Updated by RBrownSUSE almost 4 years ago

  • Priority changed from Normal to Urgent

#5 Updated by mkravec almost 4 years ago

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

#6 Updated by okurz almost 4 years ago

despite of what mkravec achieved. Why do we automate such test cases? Removing a feature should have a one-shot test. Why do we fear that the feature will reappear?

#7 Updated by mkravec almost 4 years ago

From rbrown explanation: there was regression several times (thanks okurz, I also thought this is useless test)
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1521

#8 Updated by okurz almost 4 years ago

PR got merged.

Verified working in sle-12-SP2-Server-DVD-x86_64-Build1991-gnome@64bit: https://openqa.suse.de/tests/478020#step/installation_overview/5

It does not seem to work well in migration scenarios: https://openqa.suse.de/tests/478054#step/installation_overview/11 as well as https://openqa.suse.de/tests/477961 https://openqa.suse.de/tests/478055 https://openqa.suse.de/tests/478056 https://openqa.suse.de/tests/478057 https://openqa.suse.de/tests/478061
I labeled the fails accordingly, please take a look.

#9 Updated by mkravec almost 4 years ago

I found better way to test this, there is "export configuration" button if feature is enabled, will change needles today

#10 Updated by mkravec almost 4 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

Also available in: Atom PDF