Bugzilla – Bug 1214329
[Build 10.3] Can not contact to samba server, the installation medium is avaliable
Last modified: 2023-12-12 08:30:08 UTC
Created attachment 868833 [details] y2log Installation SLES15SP6 build10.3 through the samba resource, it reports: Please make sure your installation medium is available. But the medium is available on the samba server: smb: \> ls SLE-15-SP6-Full-x86_64-Build10.3-Media1 SLE-15-SP6-Full-x86_64-Build10.3-Media1 D 0 Tue Aug 8 22:58:35 2023 10735331288 blocks of size 1024. 2734685752 blocks available And the samba server is reachable, I test SLES15SP6 build9.1 today, it works well. The issue happens since build10.3. Please find the openqa test result as below, thanks. https://openqa.suse.de/tests/11849445#step/setup_libyui/3 I attach y2log from the manual testing, well because the error appears in a quite early place, I can not collect any logs, so after the error appear, I chose to use http url to continue the installation until I could save logs. If the collected log is not valid, please kindly tell how I could collect logs for this bug report, thanks. ## Observation openQA test in scenario sle-15-SP6-Full-x86_64-gnome_smb@64bit fails in [setup_libyui](https://openqa.suse.de/tests/11849445/modules/setup_libyui/steps/3) ## Test suite description Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainer: jrivera. Install using http, https or samba as a repo source. For https suse.de has self-signed certificate, so it is required SKIP_CERT_VALIDATION=1 ## Reproducible Fails since (at least) Build [10.3](https://openqa.suse.de/tests/11849445) (current job) ## Expected result Last good: [9.1](https://openqa.suse.de/tests/11848298) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Full&machine=64bit&test=gnome_smb&version=15-SP6)
(In reply to Chenzi Cao from comment #0) > Created attachment 868833 [details] > y2log > > Installation SLES15SP6 build10.3 through the samba resource, it reports: > > Please make sure your installation medium is available. > > But the medium is available on the samba server: > smb: \> ls SLE-15-SP6-Full-x86_64-Build10.3-Media1 > SLE-15-SP6-Full-x86_64-Build10.3-Media1 D 0 Tue Aug 8 > 22:58:35 2023 > 10735331288 blocks of size 1024. 2734685752 blocks available > > And the samba server is reachable, I test SLES15SP6 build9.1 today, it works > well. The issue happens since build10.3. Please find the openqa test result > as below, thanks. > https://openqa.suse.de/tests/11849445#step/setup_libyui/3 > > I attach y2log from the manual testing, well because the error appears in a > quite early place, I can not collect any logs, so after the error appear, I > chose to use http url to continue the installation until I could save logs. > If the collected log is not valid, please kindly tell how I could collect > logs for this bug report, thanks. > > ## Observation > > openQA test in scenario sle-15-SP6-Full-x86_64-gnome_smb@64bit fails in > [setup_libyui](https://openqa.suse.de/tests/11849445/modules/setup_libyui/ > steps/3) > > ## Test suite description > Testsuite maintained at > https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainer: jrivera. > Install using http, https or samba as a repo source. > For https suse.de has self-signed certificate, so it is required > SKIP_CERT_VALIDATION=1 > > > ## Reproducible > > Fails since (at least) Build [10.3](https://openqa.suse.de/tests/11849445) > (current job) > > > ## Expected result > > Last good: [9.1](https://openqa.suse.de/tests/11848298) (or more recent) > > > ## Further details > > Always latest result in this scenario: > [latest](https://openqa.suse.de/tests/ > latest?arch=x86_64&distri=sle&flavor=Full&machine=64bit&test=gnome_smb&versio > n=15-SP6) I don't believe this is a samba problem the samba version hasn't changed between build 9.1 and 10.3 also looking in the boot.msg (from 10.1) has boot.msg:<5>[ 0.017677][ T0] Unknown kernel command line parameters "splash=silent install=smb://openqa.suse.de/inst/SLE-15-SP6-Full-x86_64-Build10.3-Media1 Y2DEBUG=1 regurl=http://all-10.3.proxy.scc.suse.de", will be passed to user space. boot.msg:<7>[ 2.574843][ T1] install=smb://openqa.suse.de/inst/SLE-15-SP6-Full-x86_64-Build10.3-Media1 boot.msg:<6>[ 3.816782][ T254] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt and linuxrc.log shows 08:20:07 <2>: scanning devices 08:20:08 <4>: url = smb://openqa.suse.de/inst/SLE-15-SP6-Full-x86_64-Build10.3-Media1 08:20:08 <2>: Downloading AutoYaST file: disk:/autoinst.xml?device=*label/OEMDRV&quiet=1 08:20:08 <2>: update_device_list(0) 08:20:08 <2>: rescanning devices 08:20:08 <2>: device not found (err = 0): *label/OEMDRV 08:20:08 <2>: url mount: trying disk:/?device=*label/OEMDRV (path = /) 08:20:08 <2>: url_setup_device: disk:/?device=*label/OEMDRV 08:20:08 <2>: Failed to download AutoYaST file. 08:20:08 <2>: dud url: disk:/?device=*usb*&all=1&quiet=1 08:20:08 <4>: url = disk:/?device=*usb*&all=1&quiet=1 this doesn't seem right (and similar entries are not seen in working build)
Thanks. I assign it to kernel team to take a look at it, thanks.
Doesn't it happen with SLE15-SP5? SLE15-SP6 didn't get any own kernel yet, hence it's identical with SLE15-SP5. If the same bug doesn't happen with the same version of SLE15-SP5 kernel, it's no kernel problem.
@Steffen: Seems that linuxrc is not able to find the media ... Could you investigate? Thanks.
Fix for TW: https://github.com/openSUSE/installation-images/pull/654
> SLE15-SP6 didn't get any own kernel yet, hence it's identical with SLE15-SP5. That's not true. SLE15-SP6 has the relocated cifs modules. Anyway, fixed here: https://github.com/openSUSE/installation-images/pull/655
(In reply to Steffen Winterfeldt from comment #6) > > SLE15-SP6 didn't get any own kernel yet, hence it's identical with SLE15-SP5. > > That's not true. SLE15-SP6 has the relocated cifs modules. SUSE:SLE-15-SP6:GA/kernel-source is exactly the same as SLE15-SP5 update kernel (5.14.21-150500.55.19).
This could well be and is bad, then. I've compared to the kernel from the GM medium (which is the last we released, afaik) - kernel-default-5.14.21-150500.53.2. This would mean this fix also needs to go into sle15-sp5:update. While we're at it, has this also been changed in sle15-sp4:update?
(In reply to Steffen Winterfeldt from comment #8) > While we're at it, has this also been changed in sle15-sp4:update? Yes, SLE15-SP4 (update) kernel also places under fs/smb/, too.
Fixes for - SLE15-SP5: https://github.com/openSUSE/installation-images/pull/656 - SLE15-SP4: https://github.com/openSUSE/installation-images/pull/657
Thank you for taking care of it, I verify it is already fixed, thanks. https://openqa.suse.de/tests/12118684#
SUSE-RU-2023:4721-1: An update that has one fix can now be installed. Category: recommended (moderate) Bug References: 1214329 Sources used: openSUSE Leap 15.4 (src): installation-images-SLES-16.57.27-150400.3.14.2 Basesystem Module 15-SP4 (src): installation-images-SLES-16.57.27-150400.3.14.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
SUSE-RU-2023:4720-1: An update that has two fixes can now be installed. Category: recommended (moderate) Bug References: 1214329, 1214688 Sources used: openSUSE Leap 15.5 (src): installation-images-SLES-16.58.8-150500.3.3.1 Basesystem Module 15-SP5 (src): installation-images-SLES-16.58.8-150500.3.3.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.