RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1379972 - Need detailed information about config-check option
Summary: Need detailed information about config-check option
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: SSSD Maintainers
QA Contact: Steeve Goveas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-28 09:41 UTC by Steeve Goveas
Modified: 2020-05-02 18:31 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-18 14:45:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 4241 0 None None None 2020-05-02 18:31:08 UTC

Description Steeve Goveas 2016-09-28 09:41:11 UTC
Description of problem:
This bug was found by Shridhar, during the sssd test day for RHEL 7.3 features
Need detailed information about config-check option. Something like what kind of testing/analysis would be done by tool. What kind of mistakes it would report. It would be helpful to have detailed section on this option in the man page of sssctl. Instead of 'sssctl help'
Answer (Michal): File a BZ or upstream ticket for this.

Version-Release number of selected component (if applicable):
sssd-1.14.0-43.el7.x86_64.rpm

Comment 2 Michal Zidek 2016-09-29 09:45:58 UTC
IIRC the man sssctl was made minimalistic on purpose for easier maintenance and more detailed information on sssctl commands should be retrieved with --help for each specific command.

That being said I do agree that the --help is less helpful then it should be, so we need to enhance that, but I am not sure if we want to expand the man page.

Michal

Comment 3 Jakub Hrozek 2016-09-29 14:11:25 UTC
Upstream ticket:
https://fedorahosted.org/sssd/ticket/3208

Comment 4 Jakub Hrozek 2017-03-28 08:09:43 UTC
This bugzilla still needs work upstream. Because we are nearing the development freeze of RHEL-7.4 and the work is not finished yet, I'm reproposing the bug to RHEL-7.5.

Please push back if you disagree.

Comment 7 Jakub Hrozek 2017-08-08 09:53:55 UTC
(In reply to Jakub Hrozek from comment #5)
> https://jhrozek.wordpress.com/2016/12/09/restrict-the-set-of-groups-the-user-
> is-a-member-of-with-sssd/

Sorry, this comment was for a different bug..

Comment 8 Jakub Hrozek 2017-08-08 09:54:18 UTC
Since fixing this bug requires work in the upstream SSSD project which is not scheduled for the immediate future, I added a conditional development nack, pending upstream availability.

Comment 9 Jakub Hrozek 2018-04-18 14:45:23 UTC
Let's track is upstream only to avoid rolling the bug report from one release to another.

If you disagree with closing this bug, please just reopen it.


Note You need to log in before you can comment on or make changes to this bug.