Thanks @dnutan!
Shares working again with ACLs on my test VMs…
Thanks @dnutan
Just made sure:
Coffein level in system: OK
Rollback by duntan: Ready
Go !
And two production systems back running!
Thanks to all!
Therefore… if i am not using any kind of account provider… i can safely upgrade/update?
Yes.
But if you have have nethserver-samba installed, make sure to get the latest package which fix the read-only filesystem issue.
Still not installed. Therefore… yum update right now.
Thank you @dnutan for the great workaround!
I did a bit of research and this is what I’ve found:
I’ve create a new sssd-libwbclient
patched RPM.
Please, be sure to update everything from CentOS updates repository, than install the patch it using this commands:
yum --enablerepo=nethforge-testing update sssd-libwbclient
signal-event nethserver-samba-update
The patch works in our production environment; tested with following clients:
This is the associated issue:
If everything goes well, we can release it in nethforge repository, also we will do not need anymore the vault repository.
This will bring issue-free updates for all NethServers.
Please help me test this hack! /cc @Andy_Wismer @GG_jr @mrmarkuz @compsos @des @greavette
Tested and working on:
after resetting permissions.
let’s get it clear:
install fresh ns7 (without patches)
install sambaad
try to join domain
add your patch
try to join domain
??
The fix should work for new installation but also for currently broken ones.
So, install the patch on a new or old machine where shared folders authentication doesn’t work
It’s working!
Tested on joined/unjoined Win7/Win10 and on Raspbian with smbclient…
Can I safely upgrade my production system now or should I still wait?
It should be safe, we have the fix on our production server.
If nobody finds any error, I plan to release the fix tomorrow.
Ok, I’ll wait till tomorrow, just to be sure.
Thanks
Tested on NS 7.3.1611 (DC-AD-FS) -> PASSED!
How I tested:
After all tests, can we tell that we have NS 7.4?
Almost! I’m preparing all repositories and start building the ISO
when it’s safe to upgrade, can someone please update the title of this topic? Or post another ‘pinned’ topic? Otherwise the first BIG message on this forum is NOT to upgrade, and only after reading this whole topic you realize it’s already fixed…
That’s a great idea,
if @giacomo is ready with his work we can change the title I think.
Something like SOLVED in front of the title.
That’s huge man. You saved so many lives
That works!!! I still running tests after doing the donwgrade, but the server apparently is working. Thanks. Now I am worried about next updates… And how do I solve the mess after doing manual downgrade (When the problem is solved)