#2590 SSSD doesn't re-read resolv.conf if the file doesn't exist during boot
Closed: Fixed None Opened 6 years ago by jhrozek.

In the systemd-resolvd world, resolv.conf doesn't have to exist during boot. Therefore, sssd wouldn't succeed in setting the inotify watch and wouldn't know the file got actually created.

We should;
1) subscribe to the systemd dbus interface and re-set resolver if the state changes (sorry, no details atm)
2) if 1) is not available or even as an additional measure, poll for resolv.conf it it was missing and stop polling once resolv.conf appears.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 alpha

Stephen had additional idea today as well on #sssd. We might want to always fire the online checks in pairs if offline. If the first one was not successful, start a second one in 5 (or so) seconds to account for slow dhclient.

Listening to NM notifications is complementary to this.

This RFE is not visible in RHEL and also should not be tested on its own, rather through making sure online transitions work fine.

rhbz: => 0

Fields changed

owner: somebody => mzidek
sensitive: => 0

Work is ongoing, but will not block Alpha

milestone: SSSD 1.13 alpha => SSSD 1.13 beta

Fields changed

patch: 0 => 1

resolution: => fixed
status: new => closed

Fields changed

milestone: SSSD 1.13.1 => SSSD 1.13.0

Metadata Update from @jhrozek:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD 1.13.0

4 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/3631

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.