Bug 806302

Summary: Syntax error on line 200326 jockey_cache_t [type=IDENTIFIER]
Product: [Fedora] Fedora Reporter: Antonio T. (sagitter) <anto.trande>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 17CC: anto.trande, dominick.grift, dwalsh, jreiser, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-04 13:53:36 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:

Description Antonio T. (sagitter) 2012-03-23 12:03:42 UTC
Description of problem:
This error appears during the installation of policycoreutils-python package.

Version-Release number of selected component (if applicable):
policycoreutils-python.x86_64 0:2.1.10-29.fc17  

How reproducible: 
# yum reinstall policycoreutils-python

  
Actual results:

...
policycoreutils-python-2.1.10-29.fc17.x86_64.rpm    
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : policycoreutils-python-2.1.10-29.fc17.x86_64 
/usr/share/selinux/devel/include/apps/jockey.if: Syntax error on line 200326 jockey_cache_t [type=IDENTIFIER]
/usr/share/selinux/devel/include/apps/jockey.if: Syntax error on line 200326 jockey_cache_t [type=IDENTIFIER]
  Verifying  : policycoreutils-python-2.1.10-29.fc17.x86_64 

Installed:
  policycoreutils-python.x86_64 0:2.1.10-29.fc17

Comment 1 Miroslav Grepl 2012-03-23 13:05:54 UTC
It was fixed in the latest policy.

$ yum update selinux-policy-targeted --enablerepo=updates-testing

Comment 2 Antonio T. (sagitter) 2012-03-23 14:28:47 UTC
My Fedora 17 is just updated (updates-testing repo actived).

selinux-policy-targeted-3.10.0-104.fc17.noarch

Comment 3 Miroslav Grepl 2012-03-26 09:01:47 UTC
Please try to again, the latest build has been pushed to the testing repo finally.

Comment 4 Antonio T. (sagitter) 2012-03-26 09:57:00 UTC
Fixed with selinux-policy-targeted-3.10.0-106.fc17.
Thanks.

Comment 5 John Reiser 2012-03-26 16:30:49 UTC
I still see this error in -policy (not -targeted):
  Updating   : selinux-policy-3.10.0-106.fc17.noarch                            46/358 
/usr/share/selinux/devel/include/apps/jockey.if: Syntax error on line 181990 jockey_cache_t [type=IDENTIFIER]

Comment 6 Daniel Walsh 2012-03-27 19:14:23 UTC
John run

# sepolgen-ifgen

Do you still see it?

Comment 7 John Reiser 2012-03-27 19:31:43 UTC
No, running "sepolgen-ifgen" [as root, with no parameters] does not show the message, and gives shell exit code 0 (success).  So why did the complaint appear during %post processing as part of the update?

Comment 8 Daniel Walsh 2012-03-27 20:01:25 UTC
Race condition.  I think updating policycoreutils could trigger this before the updated selinux-policy, but anyways it should not happen again.

Comment 9 Fedora End Of Life 2013-07-04 07:45:13 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.