Bug 15295 - winbind AD server connection state machine stuck disconnected
Summary: winbind AD server connection state machine stuck disconnected
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Winbind (show other bugs)
Version: 4.15.13
Hardware: All All
: P5 major (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-30 02:04 UTC by Matthew Grant
Modified: 2023-01-30 02:04 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Grant 2023-01-30 02:04:38 UTC 
After the switches at work got segmented over the weekend, one of our Samba 4.15  filesservers had trouble with 'getent passwd username' not returning any user information, even though winbind -u was returning a list of users.  'wbinfo --user-info username' was returning error about not being connected to a DC.

This was after the network was restarted and I could log into machines again.

Had to wipe samba (/var/lib/samba contents), and reinstall and rejoin the Domain which was easy becuase just implementing Ansible devops at work.

This should not be happening though.  winbind AD connection state machine should be retrying and not getting stuck in a failed connection state like this.