Bug 1216019

Summary: [Build 26.1] openQA test fails in handle_reboot - with minial pattern installation, after reboot, system cannot be connected
Product: [openSUSE] PUBLIC SUSE Linux Enterprise Server 15 SP6 Reporter: yutao wang <yuwang>
Component: YaST2Assignee: E-mail List <yast2-maintainers>
Status: RESOLVED WORKSFORME QA Contact:
Severity: Normal    
Priority: P5 - None CC: richard.fan
Version: unspecified   
Target Milestone: ---   
Hardware: S/390   
OS: SLES 15   
URL: https://openqa.suse.de/tests/12409148/modules/handle_reboot/steps/11
Whiteboard:
Found By: openQA Services Priority:
Business Priority: Blocker: Yes
Marketing QA Status: --- IT Deployment: ---
Attachments: yast 2 log

Description yutao wang 2023-10-07 07:05:07 UTC 
Created attachment 869982 [details]
yast 2 log

Hardware: s390x
Software: SLE-15-SP6-Online-s390x-Build26.1-Media1.iso
****************************************************************
## Observation

openQA test in scenario sle-15-SP6-Online-s390x-minimal+base_yast@s390x-zVM-vswitch-l3 fails in
[handle_reboot](https://openqa.suse.de/tests/12409148/modules/handle_reboot/steps/11)

## Test suite description
Select a minimal textmode installation by starting with the default and unselecting all patterns except for "base" and "minimal". Not to be confused with the new system role "minimal" introduced with SLE15.


## Reproducible

Fails since (at least) Build [16.1](https://openqa.suse.de/tests/11953095)
*******************************************************************
Test steps:
1. Install sles15sp6 with ISO: SLE-15-SP6-Online-s390x-Build26.1-Media1.iso
2. Select system role: 'text mode'
3. Selected patterns: minimal base system and Enhance Base system
4. After installation reboot the system
Got error message:
Error connecting to <root@s390qa106.qa.suse.de>: No route to host
Comment 1 Richard Fan 2023-10-07 07:40:19 UTC 
Hi Yutao, 

https://openqa.suse.de/tests/12409148#step/select_patterns/93

The ssh port is blocked, please open it at first.

I would close this bug, and please re-open it once you can reproduce it with ssh port open.