Project

General

Profile

action #91947

[qe-core][qem] prevent regression in cifs-utils like bsc#1184815

Added by hurhaj 3 months ago. Updated 19 days ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

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: network/cifs.pm is testing mounting with krb as indicated in the bug, 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

History

#1 Updated by tjyrinki_suse 3 months ago

  • Subject changed from [qem] prevent regression in cifs-utils like bsc#1184815 to [qe-core][qem] prevent regression in cifs-utils like bsc#1184815
  • Category set to Enhancement to existing tests
  • Priority changed from Normal to Urgent
  • Target version set to QE-Core: Ready
  • Start date deleted (2021-04-29)

#2 Updated by tjyrinki_suse 3 months ago

  • Status changed from New to Workable

#3 Updated by tjyrinki_suse 3 months ago

  • Description updated (diff)

#4 Updated by szarate 3 months ago

  • Description updated (diff)

#5 Updated by maritawerner about 1 month ago

If nothing was done so far is that ticket really urgent?

#6 Updated by szarate about 1 month ago

  • Priority changed from Urgent to Normal

maritawerner wrote:

If nothing was done so far is that ticket really urgent?

I agree

#7 Updated by dvenkatachala about 1 month ago

  • Assignee set to dvenkatachala

#8 Updated by dvenkatachala 27 days ago

  • Status changed from Workable to In Progress

#9 Updated by dvenkatachala 21 days ago

  • Status changed from In Progress to Workable
  • Assignee changed from dvenkatachala to szarate

#10 Updated by szarate 19 days ago

  • Status changed from Workable to Feedback

Waiting to get more info on setup strategies/config files and proper procedure to add it to the test suite.

Also available in: Atom PDF