#2860 Add support for disabling netlink use
Closed: Fixed None Opened 6 years ago by nkondras.

SSSD uses netlink to monitor changes to routes/addresses/links and trigger certain actions. Unfortunately, socket_wrapper (which is necessary for setting up Samba integration tests as a non-root user) currently doesn't support netlink sockets.
Additionally, stability of integration tests will be increased if they didn't depend on the changes to hosts routes/addresses/links, especially since they don't concern the sssd instances running integration tests.

For that matter it would be good to implement a command-line option or an environment variable support for disabling netlink use.

Even though we might get a fix in socket_wrapper, the comment that something like DHCP lease renewal shouldn't tinker with offline status is real.

owner: somebody => pcech

This can be targetting 1.14 alpha for now, until we have integration tests that test offline behaviour.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14 alpha

Fields changed

rhbz: => 0

The 1.14 Alpha release should be small and targeted at stabilizing the refactoring and important fixes, therefore I'm demoting this ticket to the Beta milestone.

Chances are Lukas will have to implement this ticket in order to upstream the Samba tests, but we'll see what that happens. This ticket by itself shouldn't block the Alpha release.

milestone: SSSD 1.14 alpha => SSSD 1.14 beta

Too late for 1.14 beta, sorry..

milestone: SSSD 1.14 beta => SSSD 1.14 backlog

Fields changed

keywords: => easyfix


milestone: SSSD 1.14 backlog => SSSD 1.14.1
resolution: => fixed
status: new => closed

Metadata Update from @nkondras:
- Issue assigned to pcech
- Issue marked as blocked by: #2818
- Issue set to the milestone: SSSD 1.14.1

5 years ago

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/3901

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.

Login to comment on this ticket.