Bug 486742
Summary: | satellite install, selinux denials osa-dispatcher | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | wes hayutin <whayutin> |
Component: | Installer | Assignee: | Jan Pazdziora <jpazdziora> |
Status: | CLOSED NOTABUG | QA Contact: | wes hayutin <whayutin> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 530 | CC: | bperkins, msuchy |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | na | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-03-16 13:08:32 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: | 457079 |
Description
wes hayutin
2009-02-21 16:35:13 UTC
*** This bug has been marked as a duplicate of bug 484653 *** The AVC denials are completely different. Reopening. What did you do after that installation? After the installer said * Deploying configuration files. * Update configuration in database. * Setting up Cobbler.. * Restarting services. Installation complete. Visit https://your-satellite.redhat.com to create the RHN Satellite administrator account. what other steps did you make? Could it be that you are not running the installer on a terminal but from some automation thing, and it's that thing which causes the problem? Generally, these look like leaked descriptors from whatever automation tool you are using. Please provide info about how exactly you run those installations. Jan and I chatted.. the differences we are seeing may be caused by running the installer in a "screen" session. Wes confirmed that the installation was run under screen and that re-running the installation without screen does not generate the AVC denials. So currently it looks like leaked file descriptor in screen. running w/ the correct version of screen did NOT produce this error.. I think we can close this. closing |