action #91947
open[qe-core][qem] prevent regression in cifs-utils like bsc#1184815
0%
Description
We had regression in cifs-utils: https://bugzilla.suse.com/show_bug.cgi?id=1184815 - mounting was broken when used with krb
This scenario could be made into automated test to prevent from happening again
Acceptance Criteria¶
AC1: To validate the assumption of what to test (sec=krb5), do a manual testing in a VM (any SLE version that was affected and then fixed) where the patch fixing the issue is reverted so that one can reproduce the original regression.
AC2: network/cifs.pm is testing with the same command from now on that was used in AC1 / indicated in the bug report, and the test is run across all maintenance releases
Suggestions¶
- Check what´s needed for the krb5 server to be configured, so that the following mount, either passes or fails (try first with a lower version of the package or SP?)
// Enable CIFS debug to get more info from dmesg
echo 'module cifs +p' > /sys/kernel/debug/dynamic_debug/control
echo 'file fs/cifs/* +p' > /sys/kernel/debug/dynamic_debug/control
echo 7 > /proc/fs/cifs/cifsFYI// Command to mount CIFS FS ( error 126 )
// mount -t cifs //dfs.moon.corner.tech/software/SAP /opt/software/share -o gid=sapsys,file_mode=0440,dir_mode=0775,sec=krb5,username=NG-CB-UBD201$,vers=3.0
mount error(126): Required key not available
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
- AC1: Provide two verification runs for 15-SP2, one with the version that passes and another with the version that fails.
- AC2: branch the changes to run unconditionally on 15-SP3
- AC3: Soft fail for openSUSE