|
Bugzilla – Full Text Bug Listing |
| Summary: | [Build 26.1] openQA test fails in installation - service 'sshd' was not found during autoyast installation | ||
|---|---|---|---|
| Product: | [openSUSE] PUBLIC SUSE Linux Enterprise Server 15 SP6 | Reporter: | yutao wang <yuwang> |
| Component: | AutoYaST | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED INVALID | QA Contact: | AutoYaST Maintainers <autoyast-maintainers> |
| Severity: | Normal | ||
| Priority: | P2 - High | CC: | leli, riccardo.ceragioli, richard.fan |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SLES 15 | ||
| URL: | https://openqa.suse.de/tests/12413881/modules/installation/steps/35 | ||
| Whiteboard: | |||
| Found By: | openQA | Services Priority: | |
| Business Priority: | Blocker: | Yes | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
autoyast profile
yast 2log Screenshot with warning pop-up "Service 'sshd' not found" |
||
|
Description
yutao wang
2023-10-07 06:35:16 UTC
Created attachment 869981 [details]
yast 2log
Again, this bug description is completely inadequate; it leaves us to guess and to reverse engineer what you did which keeps costing us way too many developer hours. Please read https://en.opensuse.org/openSUSE:How_to_Write_a_Good_Bugreport The <software> section of the AutoYaST profile used here:
<software>
<instsource/>
<packages config:type="list">
<package>dconf</package>
<package>girepository-1_0</package>
<package>grub2-snapper-plugin</package>
<package>gxditview</package>
<package>libXaw7</package>
<package>libXmu6</package>
<package>libbtrfs0</package>
<package>libdconf1</package>
<package>libgirepository-1_0-1</package>
<package>snapper</package>
<package>snapper-zypp-plugin</package>
<package>ucode-intel</package>
<package>xbitmaps</package>
<package>yast2-nis-client</package>
<package>yast2-printer</package>
<package>yast2-snapper</package>
</packages>
<patterns config:type="list">
<pattern>minimal_base</pattern>
<pattern>base</pattern>
</patterns>
<products config:type="list">
<product>SLES</product>
</products>
<remove-packages config:type="list">
<package>glibc-32bit</package>
<package>libncurses5-32bit</package>
<package>gtk2-branding-SLED</package>
<package>gtk2-lang</package>
<package>gtk2-metatheme-adwaita</package>
<package>gtk2-theming-engine-adwaita</package>
<package>gtk2-tools</package>
<package>libQt5Core5</package>
<package>libQt5DBus5</package>
<package>libQt5Gui5</package>
<package>libQt5Widgets5</package>
<package>libQt5X11Extras5</package>
<package>libbz2-1-32bit</package>
<package>libdb-4_8-32bit</package>
<package>libgcc_s1-32bit</package>
<package>libgdbm4-32bit</package>
<package>libgtk-2_0-0</package>
<package>libmtdev1</package>
<package>libpcre16-0</package>
<package>libpython3_4m1_0</package>
<package>libstdc++6-32bit</package>
<package>libxcb-icccm4</package>
<package>libxcb-image0</package>
<package>libxcb-randr0</package>
<package>libxcb-render-util0</package>
<package>libxcb-shape0</package>
<!-- <package>libxcb-sync1</package> -->
<package>libxcb-util1</package>
<package>libxcb-xkb1</package>
<package>libxkbcommon0</package>
<package>libyui-qt-pkg6</package>
<package>libyui-qt6</package>
<package>libz1-32bit</package>
<package>metatheme-adwaita-common</package>
<package>perl-32bit</package>
<package>perl-Test-Simple</package>
</remove-packages>
</software>
I don't see package 'sshd' being explicitly requested, and the patterns are 'minimal-base' and 'base'. So why would 'sshd' be installed?
So you got a warning (!) pop-up dialog telling you that service 'sshd' was not found; which sounds totally plausible since it was not part of the set of installed packages.
2023-10-07 04:21:07 <2> linux(4249) [Ruby]
clients/services-manager_finish.rb(write):23
Service 'sshd' was not found.
2023-10-07 04:21:07 <0> linux(4249) [Ruby]
binary/Yast.cc(ycp_module_call_ycp_function):401
Append parameter
`HBox(... `VBox(...
`Heading ("Warning"))
`RichText("<ul><li>Service 'sshd' was not found.</li></ul>")
...
`ButtonBox (
`PushButton (`id (`ok), `okButton), "&OK")
Created attachment 869996 [details] Screenshot with warning pop-up "Service 'sshd' not found" This is what you should have attached to the bug to make clear what this is all about. The relevant information (which is missing from the bug description) is: - There was a warning pop-up - It was not a crash, you can continue if you confirm the pop-up - (Optional) It happened after package installation, in or near stage "Copy files to installed system" See also https://en.opensuse.org/openSUSE:How_to_Write_a_Good_Bugreport If you configure 'sshd' in your AutoYaST profile, make sure that 'sshd' is installed. Even if that happened without you explicitly specifying that package in your AutoYaST profile, that might have been coincidence; one of the patterns that you installed might have contained it in the past, or one of the other packages that you explicitly installed might have required it. But those things change, so please don't make assumptions; make sure that you get all the packages that the target system needs. This is not the responsibility of the installer. I have added 'openssh' package to the software part at autoyast profile. It can work now. https://openqa.suse.de/tests/12439149# But I still have one question, this profile was used for several builds, it doesn't need this 'openssh' package at autoyast profile. But why this build26.1 need this package. I think maybe product design changed to install some default packages. So this change is by design or a bug? I will try to fix the autoyast configuration file based on your kindly suggestion. (In reply to yutao wang from comment #7) > But I still have one question, this profile was used for several builds, it > doesn't need this 'openssh' package at autoyast profile. But why this > build26.1 need this package. You might have gotten that package installed by coincidence; for example, because a pattern contained it, or because some other package suggested or required it. That's what I meant in comment #6: It is entirely possible that you were simply lucky in the past, and some other package or pattern caused it to be installed. But relying on that kind of luck is not something that you can rely on; as dependencies of those other packages or patterns change, your luck may run out. And that is very likely what happened here. |