#3166 sssctl config-check: Add path to files when pattern matching fails
Closed: Fixed None Opened 7 years ago by mzidek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1372258

Description of problem:
sssctl check-config is inconsistent when on the output:
Messages generated during configuration merging: 2
File /etc/sssd/conf.d/wrong-file-permissions.conf did not pass access check.
Skipping.
File configuration.conf.disabled did not match provided patterns. Skipping.

For the second item, only the file name is shown - without the full path.



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



Steps to Reproduce:
1. Add a file /etc/sssd/conf.d/configuration.conf.disabled
2. Run
   # sssctl config-check



Actual results:
File configuration.conf.disabled did not match provided patterns. Skipping.



Expected results:
File /etc/sssd/conf.d/configuration.conf.disabled did not match provided
patterns. Skipping.

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
owner: somebody => mzidek
priority: major => minor
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
owner: somebody => mzidek
priority: major => minor
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
owner: somebody => mzidek
priority: major => minor
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

patch: 0 => 1

Fields changed

patch: 0 => 1

Fields changed

patch: 0 => 1

I replied on the sssd-devel with my comment and proposal. I am not sure if it would not be lost so I want to mention it here.

I replied on the sssd-devel with my comment and proposal. I am not sure if it would not be lost so I want to mention it here.

I replied on the sssd-devel with my comment and proposal. I am not sure if it would not be lost so I want to mention it here.

ding-libs master:

  • 72ca1a3552fdc33b7fa7e832ecfc235dd685a7e7

status: new => assigned

ding-libs master:

  • 72ca1a3552fdc33b7fa7e832ecfc235dd685a7e7

status: new => assigned

ding-libs master:

  • 72ca1a3552fdc33b7fa7e832ecfc235dd685a7e7

status: new => assigned

Fields changed

milestone: NEEDS_TRIAGE => ding-libs 0.7.0
resolution: => fixed
status: assigned => closed

Fields changed

milestone: NEEDS_TRIAGE => ding-libs 0.7.0
resolution: => fixed
status: assigned => closed

Fields changed

milestone: NEEDS_TRIAGE => ding-libs 0.7.0
resolution: => fixed
status: assigned => closed

Metadata Update from @mzidek:
- Issue assigned to mzidek
- Issue set to the milestone: ding-libs 0.7.0

7 years ago

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/4199

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.

Login to comment on this ticket.

Metadata