#2976 sdap code can mark the whole sssd_be offline
Closed: worksforme a year ago Opened 3 years ago by jhrozek.

There is a case where, during connection, a low-lever sdap function can mark the whole back end unconditionally as offline.

We might want to instead try to infer the domain from the sdap_domain structure to be able to only disable subdomain instead of marking the whole domain as offline.


Moving to 1.13.4 as agreed on Mar-17 triage.

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
milestone: NEEDS_TRIAGE => SSSD 1.13.4
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

milestone: SSSD 1.13.4 => SSSD 1.13.5

Nobody touched this ticket for half a year. I suggest to move it to 1.15 Alpha (through triage) and then decide if it's something to fix in the stable branch as well. One goal of the refactoring might be to see if the situation can be improved even w/o many code changes.

Fields changed

milestone: SSSD 1.13.5 => NEEDS_TRIAGE

This ticket depends on ticket #1507. We need to first take a look at the sdap code and only once it's documented and tested, we can decide if it's possible to fix this bug without

blockedby: => 1507

Moving to the same milestone as #1507 in the meantime.

milestone: NEEDS_TRIAGE => SSSD 1.15 Alpha

Fields changed

milestone: SSSD 1.15.0 => SSSD 1.15 Beta

Fields changed

milestone: SSSD 1.15.3 => SSSD 1.15.2

Metadata Update from @jhrozek:
- Issue marked as depending on: #1507
- Issue set to the milestone: SSSD 1.15.2

2 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset
- Custom field mark reset
- Custom field patch reset
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset
- Issue close_status updated to: None
- Issue set to the milestone: SSSD 1.15.3 (was: SSSD 1.15.2)

2 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset
- Custom field mark reset
- Custom field patch reset
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset

2 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset
- Custom field mark reset
- Custom field patch reset
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset
- Issue set to the milestone: SSSD 1.15.4 (was: SSSD 1.15.3)

2 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue set to the milestone: SSSD 1.16.0 (was: SSSD 1.15.4)

2 years ago

Metadata Update from @fidencio:
- Issue assigned to fidencio

2 years ago

Since we are required to release a new upstream tarball no later than Friday Oct-20, I'm moving tickets that will not be closed by that date to the next milestone, 1.16.1

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)

a year ago

@fidencio btw shouldn't this ticket be just closed, based on your testing?

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)

a year ago

@jhrozek, please, let's close the ticket.

I didn't find any obvious place where it can actually happen and all patches related to this are already pushed (were already pushed for a long time).

Metadata Update from @fidencio:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)

a year ago

After investigation, the bug should no longer be present in 1.16.1. If you still see the issue in 1.16.1, please open a new ticket.

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)

a year ago

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue close_status updated to: worksforme
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata