Learn more about these different git repos.
Other Git URLs
We rely on dbus mapping of sender to UID. However, when the bus is restarted, we'd receive NameOwnerChanged which we should use to flush the hash table we keep the sender-UID relations in.
type: defect => enhancement
milestone: NEEDS_TRIAGE => SSSD 1.13 beta
priority: major => critical
rhbz: => 0
mark: => 0
On a meeting with Stef, we concluded this is important to get Objectmanager right.
Also, when the sysbus connection is dropped, we should just quit IFP completely and let dbus restart it when another request comes in.
This is critical for objectmanager, moving to needs_triage.
milestone: SSSD 1.13 beta => NEEDS_TRIAGE
milestone: NEEDS_TRIAGE => SSSD 1.12.3
This is needed for better integration, but no downstream is waiting for this ticket, lowering priority
priority: critical => major
I'm moving all D-Bus related tickets to 1.12.4. We are working on the interfaces in the 1.12 cycle, but as the interface won't be ready for 1.12.3 release anyway, it makes sense to realign all D-Bus tickets in 1.12.4
milestone: SSSD 1.12.3 => SSSD 1.12.4
The sbus-related patches are landing on the list, but we realized during review that they're too big for 1.12, at least for the time being. We're going to commit them to master only for now and backport on request to avoid breaking 1.12.
milestone: SSSD 1.12.4 => SSSD 1.13 alpha
owner: somebody => pbrezina
The dbus Bus sends a NameOwnerChanged signal. When that occurs for a name that you're keeping information about (such as UID info) you can clear that out of the cache.
patch: 0 => 1
resolution: => fixed
sensitive: => 0
status: new => closed
Metadata Update from @jhrozek:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.13 alpha
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:
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.
to comment on this ticket.