Bug 861565 - groupadd failed in PREIN scriptlet in 7:squid-3.2.0.16-1.fc17.x86_64
Summary: groupadd failed in PREIN scriptlet in 7:squid-3.2.0.16-1.fc17.x86_64
Keywords:
Status: CLOSED DUPLICATE of bug 844167
Alias: None
Product: Fedora
Classification: Fedora
Component: squid
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Luscon
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-29 08:05 UTC by Robin Lee
Modified: 2012-10-24 02:35 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-24 02:35:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Robin Lee 2012-09-29 08:05:22 UTC
Description of problem:
'yum install squid' failed:
Error in PREIN scriptlet in rpm package 7:squid-3.2.0.16-1.fc17.x86_64
error: %pre(squid-7:3.2.0.16-1.fc17.x86_64) scriptlet failed, exit status 1

If use rpm -Uvh to install squid, it says:
...
groupadd: failure while writing changes to /etc/group
...

Version-Release number of selected component (if applicable):
7:squid-3.2.0.16-1.fc17.x86_64

How reproducible:
yum install squid

Comment 1 Robin Lee 2012-09-29 08:10:00 UTC
Manually run
# groupadd -g 23 squid
is ok.

Comment 2 Tomas Mraz 2012-10-01 07:48:55 UTC
If manually running groupadd is fine, it might be either some other problem in the %pre squid scriptlet or perhaps a SELinux issue.

Comment 3 Michal Luscon 2012-10-18 13:08:19 UTC
Do you have any unusual SELinux settings on your system? I am not experiencing this problem with my f17.

Comment 4 Robin Lee 2012-10-19 01:55:21 UTC
I am not familiar with SELinux. How to find out if I have some unusual settings?

Squid PRE scriptlet seems a bit different since it hard codes the group id.

Comment 5 Robin Lee 2012-10-24 02:35:36 UTC
Tested with selinux-policy-3.10.0-156.fc17

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


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