Bug 477923 - Incorrect repair guidance
Incorrect repair guidance
Product: Fedora
Classification: Fedora
Component: setroubleshoot (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Daniel Walsh
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-12-25 09:40 EST by John Mellor
Modified: 2009-12-18 02:23 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 02:23:49 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
setroubleshoot output showing the bad problem correction guidance (2.88 KB, text/plain)
2008-12-25 09:41 EST, John Mellor
no flags Details

  None (edit)
Description John Mellor 2008-12-25 09:40:42 EST
Description of problem:
Incorrect guidance to correct the problem

Version-Release number of selected component (if applicable):

How reproducible:
unknown, I see it every day while verifying bug 477922

Steps to Reproduce:
1.reproduce bug 477922
2.use setroubleshoot to show the guidance
3.run the suggested repair command
Actual results:
# restorecon -v 'inotify' 
restorecon:  stat error on inotify:  No such file or directory

Expected results:
problem correction

Additional info:
libinotify exists in F10, but no inotify utility is present to relabel.
Comment 1 John Mellor 2008-12-25 09:41:51 EST
Created attachment 327838 [details]
setroubleshoot output showing the bad problem correction guidance
Comment 2 Daniel Walsh 2008-12-27 07:17:31 EST
The problem here is that the only information we get is that a sshd is not allowed to read a directory.  The kernel does not give us the full path, so we grab a catchall plugin which is just about useless to the user.  In this case a different plugin match (catchall) would have told you to create a custom policy and submit a bug report would have been a better match.

Perhaps catchall_file should be removed so this could fall through.  We have a another plugin that will check the labeling if the kernel gives us a full path, to see if the label matches the system default.

Now if we could get the kernel to give us complete paths ...
Comment 4 Bug Zapper 2009-11-18 07:42:26 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 5 Bug Zapper 2009-12-18 02:23:49 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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