Project

General

Profile

Actions
Copy link

action #48095

closed

[functional][y] Assure that installing a system with a non-available default systemd target mode shows a proper error

Added by SLindoMansilla about 5 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
oorlov
Category:
New test
Target version:
SUSE QA - Milestone 30
Start date:
2019-02-19
Due date:
2020-03-10
% Done:

0%

Estimated time:
8.00 h
Difficulty:

Description

Motivation

When a user installs a system without Gnome/Xwindow and still force the system to boot to graphic mode. That will cause the system hanging up at first boot because systemd cannot find the display.service.
We suppose an obvious warning message is better than current warnings.

A warning message was implemented: https://github.com/yast/yast-services-manager/pull/187

An autoyast profile can be mocked up to reproduce this issue with:

<services-manager>
<default_target>not_found_default</default_target>
<services config:type="list"/>
</services-manager>

Let's limit the scope and enable in at least one graphical installation and one textmode installation.

systemd target is set by system role.

Acceptance criteria

  • AC: A test suite can reproduce the issue and assert the warning message.

Further information

Related bug: https://bugzilla.suse.com/show_bug.cgi?id=1046083

Actions
Copy link
 #1

Updated by okurz about 5 years ago

  • Target version set to Milestone 25
Actions
Copy link
 #2

Updated by riafarov almost 5 years ago

  • Target version changed from Milestone 25 to Milestone 30+

This test makes sense for SLE/leap 15 and TW, moving to 28+.

Actions
Copy link
 #3

Updated by riafarov over 4 years ago

  • Due date set to 2019-12-03
Actions
Copy link
 #4

Updated by riafarov over 4 years ago

  • Due date changed from 2019-12-03 to 2019-12-17
Actions
Copy link
 #5

Updated by riafarov over 4 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Estimated time set to 8.00 h
Actions
Copy link
 #6

Updated by riafarov over 4 years ago

  • Due date changed from 2019-12-17 to 2020-02-11
Actions
Copy link
 #7

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 30+ to Milestone 30

bulk moved to M30 for revisiting

Actions
Copy link
 #8

Updated by riafarov about 4 years ago

  • Due date changed from 2020-02-11 to 2020-02-25
Actions
Copy link
 #9

Updated by oorlov about 4 years ago

  • Status changed from Workable to In Progress
  • Assignee set to oorlov
Actions
Copy link
 #10

Updated by oorlov about 4 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #11

Updated by JERiveraMoya about 4 years ago

  • Due date changed from 2020-02-25 to 2020-03-10

Agreed with Alex to check for verification in next sprint and resolve it.

Actions
Copy link
 #12

Updated by oorlov about 4 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF