Bug 467276

Summary: RuntimeError: couldn't determine security context for `/home/guest': Invalid argument
Product: [Fedora] Fedora Reporter: James Laska <jlaska>
Component: libuserAssignee: Miloslav Trmač <mitr>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: jturner, mitr, tcallawa, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-24 21:23:53 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: 467217    
Bug Blocks: 438943, 466514    

Description James Laska 2008-10-16 16:47:06 UTC
Description of problem:

Trying to create a new user from firstboot gui tracebacks due to selinux denial.

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

firstboot-1.100-1.fc10.i386
selinux-policy-3.5.12-2.fc10.noarch

How reproducible:


Steps to Reproduce:
1. Boot into a freshly installed system
2. Proceed through graphical firstboot to the user creation module
3. Add a new user (guest, "Guest User")
  
Actual results:

A traceback occurs:

# cat /tmp/firstboot-Nv4Kqq 
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/firstboot/interface.py", line 102, in _nextClicked
    self.advance()
  File "/usr/lib/python2.5/site-packages/firstboot/interface.py", line 147, in advance
    result = module.apply(self, self.testing)
  File "/usr/share/firstboot/modules/create_user.py", line 148, in apply
    self.admin.addUser(userEnt, mkhomedir=mkhomedir)
RuntimeError: couldn't determine security context for `/home/guest': Invalid argument

Expected Results:

No traceback

Additional info:

# setenforce 0 

Works around the problem.

Comment 1 Chris Lumens 2008-10-21 22:11:11 UTC
James - I believe this was a problem with the policy package that has been addressed.  Care to try again?

Comment 2 Tom "spot" Callaway 2008-10-24 21:23:53 UTC
Confirmed that this is fixed in rawhide, closing. James, if you can reproduce, please re-open.

Comment 3 James Laska 2008-10-31 14:00:14 UTC
VERIFIED in -53 (rawhide-20081030).