-
Notifications
You must be signed in to change notification settings - Fork 252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TESTS: don't use deprecated sssd.conf::user option #7266
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see client.sssd.set_service_user(sssd_service_user) in the code which results in undefined variable.
E fixture 'sssd_service_user' not found
Currently when SSSD is built '--with-sssd-user=sssd' it's also configured to run under 'sssd' user by default via sssd.service, so that sssd.conf::user option is ignored anyway. Since sssd.conf::user is deprecated and will go away, it doesn't make much sense to put effort into testing it. What makes sense is to test sssd.service::User option, but this is out of scope of this patch.
4b79fe6
to
650f7df
Compare
LGTM. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I realized it might make sense to change implementation of |
Currently when SSSD is built '--with-sssd-user=sssd' it's also configured to run under 'sssd' user by default via sssd.service, so that sssd.conf::user option is ignored anyway.
Since sssd.conf::user is deprecated and will go away, it doesn't make much sense to put effort into testing it.
What makes sense is to test sssd.service::User option, but this is out of scope of this patch.