#3830 Printing incorrect information about domain with sssctl utility
Closed: Fixed Opened by pbrezina.

Ticket was cloned from Red Hat Bugzilla: Bug 1628122

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:
Printing incorrect information about domain with sssctl utility.
Version-Release number of selected component (if applicable):
sssd-2.0.0-2.el8
How reproducible:
Always.
Steps to Reproduce:
1. Configure sssd and make typo in ldap_uri to make sssd offline.
2. Check the domain status using ‘sssctl domain-status LDAP -o’.
Actual results:
Printing ‘Online status: Online’ when backend is offline
Expected results:
sssctl should print appropriate domain status
Additional info:
From log,
./sssd_LDAP.log:(Wed Sep 12 05:13:41 2018) [sssd[be[LDAP]]]
[be_check_online_done] (0x0400): Backend is offline
./sssd_LDAP.log:(Wed Sep 12 05:13:50 2018) [sssd[be[LDAP]]]
[sbus_issue_request_done] (0x0040): sssd.dataprovider.getAccountInfo: Error
[1432158212]: SSSD is offline
# cat /etc/sssd/sssd.conf
[sssd]
config_file_version = 2
domains = LDAP
services = nss, pam
[domain/LDAP]
ldap_search_base = dc=example,dc=com
debug_level = 9
id_provider = ldap
auth_provider = ldap
ldap_uri = ldap://typo.server.redhat.com
ldap_tls_cacert = /etc/openldap/certs/cacert.pem
use_fully_qualified_names = True
[nss]
[pam]

Metadata Update from @pbrezina:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1628122

Metadata Update from @pbrezina:
- Issue assigned to pbrezina

  • master: dfa7bf1133f002a9fbbd3495a70909913db25b16

Metadata Update from @jhrozek:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.1

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:
- https://github.com/SSSD/sssd/issues/4824

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.

Metadata