Bug 636368
Summary: | SELinux is preventing /usr/lib/oracle/10.2.0.4/client/bin/sqlplus "search" access on /home. | ||
---|---|---|---|
Product: | [Community] Spacewalk | Reporter: | Frank Ybanez <fybanez> |
Component: | Server | Assignee: | Jan Pazdziora <jpazdziora> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 1.1 | CC: | akozlenko.kz, dwalsh, jpazdziora, mgrepl, msuchy, slukasik |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | setroubleshoot_trace_hash:bd5208f7799fda04ec5b3420d2ce65006509ffba0e28ac6fb28df459348a3565 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-11-19 16:16:13 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 623772 |
Description
Frank Ybanez
2010-09-22 00:24:43 UTC
Taking. When does this AVC happen? What actions were you doing when it happened? This occurs immediately following a complete installation of Spacewalk on F13. https://fedorahosted.org/spacewalk/wiki/OracleXeSetup#KnownIssues I'm betting the following packages need revision/to be updated to deal with this AVC exception: oracle-xe-selinux oracle-instantclient-selinux oracle-instantclient-sqlplus-selinux Or maybe Oracle is really doing something it shouldn't. (In reply to comment #3) > This occurs immediately following a complete installation of Spacewalk on F13. > > https://fedorahosted.org/spacewalk/wiki/OracleXeSetup#KnownIssues I'm confused. Is it after you've finished the steps at the OracleXeSetup page (but before you've installed the Spacewalk bits), or after all Spacewalk packages were installed? Or is it after the spacewalk-setup was run? Anyway, I believe that the issue was addressed in Spacewalk master ec440206d21021c2ba8fdedf3dc9e2b6f1f31386, when we fixed bug 626420 (it's actually a dupe thereof). Please use the Spacewalk 1.2 release candidate yum repo at http://koji.spacewalkproject.org/spacewalk/split/spacewalk-5E/server/spacewalk-5E-1.2/ http://koji.spacewalkproject.org/spacewalk/split/spacewalk-f12/server/spacewalk-f12-1.2/ http://koji.spacewalkproject.org/spacewalk/split/spacewalk-f13/server/spacewalk-f13-1.2/ http://koji.spacewalkproject.org/spacewalk/split/spacewalk-f14/server/spacewalk-f14-1.2/ (depending on your OS) to verify the bugzilla. Oops, append $basearch/os to the paths to get correct baseurl. With Spacewalk 1.2 released, marking as CLOSED CURRENTRELEASE. https://www.redhat.com/archives/spacewalk-list/2010-November/msg00111.html |