Learn more about these different git repos.
Other Git URLs
The subdomain users store FQDN in the name attribute. Some of the sysdb functions accept plain username and construct the FQDN internally and some of the functions rely on caller creating the FQDN. We should choose one or the other and stick with it.
milestone: NEEDS_TRIAGE => Interim Bucket
rhbz: => 0
type: defect => task
This is causing problems. We should get to this refactor sooner rather than later.
priority: major => critical
milestone: Interim Bucket => SSSD 1.12 beta
owner: somebody => mzidek
review: 0 => 1
Should be done together with the rest of the sysdb refactor Michal is working on.
milestone: SSSD 1.12 beta => SSSD 1.13 beta
mark: => 0
Too late for refactoring in 1.14
milestone: SSSD 1.13 beta => SSSD 1.14 beta
Michal has a first version of the patches, we should review and merge them.
milestone: SSSD 1.14 beta => SSSD 1.14 alpha
sensitive: => 0
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1328069 (Red Hat Enterprise Linux 7)
rhbz: 0 => [https://bugzilla.redhat.com/show_bug.cgi?id=1328069 1328069]
design: => https://fedorahosted.org/sssd/wiki/DesignDocs/SysdbFullyQualifiedNames
owner: mzidek => jhrozek
status: new => assigned
Needs review in Beta.
milestone: SSSD 1.14 alpha => SSSD 1.14 beta
We still need to upgrade the database format, bumping to dot-oh.
milestone: SSSD 1.14 beta => SSSD 1.14.0
patch: 0 => 1
Fixed in e6b6b9f..c88b63b
resolution: => fixed
status: assigned => closed
Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.14.0
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.