Learn more about these different git repos.
The sss_log message we emit when configuration can't be loaded does not include the reason why. We might want to include error and strerror(errno) there.
milestone: NEEDS_TRIAGE => SSSD 1.10.0
type: defect => enhancement
summary: Improve syslog message when configuration cannot be loaded => [RFE] Improve syslog message when configuration cannot be loaded
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=839664
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=839664 839664]
owner: somebody => arielb
status: new => assigned
proposed_priority: => Nice to have
Cleaning the 1.10 milestones before putting tickets into it.
milestone: SSSD 1.10.0 => Temp milestone
Moving planned features and bug fixes into the 1.10 bucket.
milestone: Temp milestone => SSSD 1.10.0
Moving all the features planned for 1.10 release into 1.10 beta.
milestone: Temp milestone => SSSD 1.10 beta
selected: => Not need
Moving tickets that are not a priority for SSSD 1.10 into the next release.
milestone: SSSD 1.10 beta => SSSD 1.11 beta
Patch by Ariel on the list. We can move this ticket to 1.10 beta.
design_review: => 0
milestone: SSSD 1.11 beta => SSSD 1.10 beta
patch: 0 => 1
review: => 0
resolution: => fixed
status: assigned => closed
changelog: => There is an improved syslog message when configuration cannot be loaded.
design: => N/A (trivial)
Metadata Update from @jhrozek:
- Issue assigned to arielb
- Issue set to the milestone: SSSD 1.10 beta
to comment on this ticket.