Today I updated from TW 20220908 to 20221101 and SMB no longer works

I use SMB to access my linux server from both Windows and Linux guest network machines.

This configuration has worked fine for years with no issues.

Today after updating to TW 20221101 neither the Windows or Linux guests can access the network shares.

Samba is running and on the Windows machine when I map to one of the shares it maps the drive but then when i try to access the mapped drive it gets Access Denied.

There have been no configuration changes to the system for SMB in years

It is not a permission issue on the drive because the user that maps to the SMB share on the Linux machine has full permissions rwx on Linux and Full Control on Linux.

I believe the problem is related to apparmour changes for samba but I am unsure how to resolve the issue.

Here are the messages that are appearing for the smb service.

            Nov 03 19:59:44 update-apparmor-samba-profile[9984]: + test No == Yes
            Nov 03 19:59:44 update-apparmor-samba-profile[9984]: + test -e /etc/apparmor.d/local/usr.sbin.smbd-shares
            Nov 03 19:59:44 update-apparmor-samba-profile[9984]: + grep -q 'update-apparmor-samba-profile 1.3' /etc/apparmor.d/local/usr.sbin.smbd-shares
            Nov 03 19:59:44 update-apparmor-samba-profile[9984]: + test /etc/samba/smb.conf -nt /etc/apparmor.d/local/usr.sbin.smbd-shares
            Nov 03 19:59:44 update-apparmor-samba-profile[9984]: + silentexit 'smb.conf is older than the AppArmor profile sniplet'
            Nov 03 19:59:44 update-apparmor-samba-profile[9984]: + exit 0
            Nov 03 19:59:44 smbd[9988]: [2022/11/03 19:59:44.703896,  0] ../../source3/smbd/server.c:1741(main)
            Nov 03 19:59:44 smbd[9988]:   smbd version 4.17.2-git.273.a55a83528b9SUSE-oS15.9-x86_64 started.
            Nov 03 19:59:44 smbd[9988]:   Copyright Andrew Tridgell and the Samba Team 1992-2022

I suspect that the problem it is because it is complaining about smb.conf being different than what apparmour has but that config has not been changed since I originally set it up.

Note that I first updated one of the client machines from TW 20220908 to 20221101 and after that machine was updated both the Windows machine and that TW 20221101 client had no problem accessing the TW 20220908 Linux server and SMB shares.

Once the TW 20220908 server was updated to 22021101 then the linux clients and windows cllients could no longer access the TW 20221101 server.

Is this a known issue?

What are my options?   I'd prefer to not have to rollback the machines but I also need a working SMB environment.