Bug 755357 - Receive "Internal Server Error" when creating Kickstart profile
Summary: Receive "Internal Server Error" when creating Kickstart profile
Keywords:
Status: CLOSED DUPLICATE of bug 752425
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 1.5
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space16
TreeView+ depends on / blocked
 
Reported: 2011-11-20 21:55 UTC by Dan Burkland
Modified: 2012-03-06 09:17 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-21 10:10:53 UTC
Embargoed:


Attachments (Terms of Use)

Description Dan Burkland 2011-11-20 21:55:25 UTC
Description of problem: I receive an "Internal Server Error" error message when attempting to creating a Kickstart profile. I am running the latest stable Spacewalk version (1.5) on CentOS 6.0 x86_64. 


Version-Release number of selected component (if applicable): Spacewalk 1.5 on CentOS 6.0 x86_64


How reproducible: Go to Kickstart->Profiles in the Spacewalk interface and create a new Kickstart profile. This issue occurs everytime
  
Actual results: Receive "Internal Server Error" message. SELINUX errors show up:

type=AVC msg=audit(1321825793.626:1941): avc:  denied  { getattr } for  pid=9668 comm="cobblerd" path="/var/lib/rhn/kickstarts/wizard/ks-centos-x86_64-server-6--2.cfg" dev=dm-3 ino=2330 scontext=unconfined_u:system_r:cobblerd_t:s0 tcontext=unconfined_u:object_r:var_lib_t:s0 tclass=file
type=SYSCALL msg=audit(1321825793.626:1941): arch=c000003e syscall=4 success=no exit=-13 a0=7f210c233480 a1=7f210bffc900 a2=7f210bffc900 a3=65632d736b2f6472 items=0 ppid=1 pid=9668 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=205 comm="cobblerd" exe="/usr/bin/python" subj=unconfined_u:system_r:cobblerd_t:s0 key=(null)

Expected results: Kickstart profile created without issues

Comment 1 Michael Mráka 2011-11-21 10:10:53 UTC

*** This bug has been marked as a duplicate of bug 752425 ***


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