Bug 1283902

Summary:	Remove krb5-server dependency on initscripts unless it is needed
Product:	Red Hat Enterprise Linux 7	Reporter:	Jan Pazdziora (Red Hat) <jpazdziora>
Component:	krb5	Assignee:	Robbie Harwood <rharwood>
Status:	CLOSED ERRATA	QA Contact:	Patrik Kis <pkis>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	7.2	CC:	dpal, jpazdziora, pkis
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	krb5-1.14.1-3.el7	Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-03 20:23:16 UTC	Type:	Bug
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:	1283777

Description Jan Pazdziora (Red Hat) 2015-11-20 08:24:50 UTC

Description of problem:

When installing krb5-server in minimal environment like a Docker container, initscripts are pulled in via rpm dependencies, plus another 4.5+ MB worth of dependencies.

It seems to be needed because of the

[ -x /etc/rc.d/init.d/krb5server ] && /sbin/chkconfig --del krb5server

in the postinstall scriptlet. But that part should no longer be needed on RHEL 7 installations.

Unless there is a strong reason to keep it, it'd be helpful to remove the dependency.

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

krb5-server-1.13.2-10.el7.x86_64

How reproducible:

Deterministic.

Steps to Reproduce:
1. docker run -ti rhel7.2 yum install krb5-server

Actual results:

--> Processing Dependency: initscripts >= 8.99-1 for package: krb5-server-1.13.2-10.el7.x86_64

and initscripts added to the transaction.

Expected results:

initscripts not pulled into the transaction.

Additional info:

Comment 8 errata-xmlrpc 2016-11-03 20:23:16 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2591.html