I don't think we can or should do this. If you clean the cache, then no offline logins would be possible after the upgrade.

Wouldn't it be better to see what 'broke' in the cache during the upgrade and fix those issues?

I agree with jhrozek. We can not clean/remove the cache in postinstall script.

What I see from reports, it's like a format was changed or something like this. Is it possible? Quite hard to catch proper log files due to the situation is not that predictable.

shaman007: Is this happening after an update? If the cache format changes we run a sysdb update function that changes the old format to new (this only happnes once after an update only if the cache format was changed)

The information that we would need is:
- what sssd version are you upgrading from and to what new version
- sssd logs

Without the above it will be difficult to find what is wrong.

OK, then we will work around with our Puppet. You can close the issue, if I would have files I would provide them, but 99% we would not be able to collect them.

Ok, thanks for the report anyway. Feel free to reopen the issue or file a new one once you have the logs or more info. For now I am closing this as worksforme.

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4819

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.