Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Also affects Red Hat Enterprise Linux 6.
+++ This bug was initially created as a clone of Bug #483160 +++
Description of problem:
Updating from RHEL-5.2 to 5.3 installed and enabled avahi (because of cups update - cups depends on avahi-compat-libdns_sd which depends on avahi)
Version-Release number of selected component (if applicable):
0.6.16-1.el5
How reproducible:
always
Steps to Reproduce:
1."yum update" on RHEL-5.2 system that does not have avahi installed.
2. reboot
3.
Actual results:
avahi is installed and running after reboot to new kernel
Expected results:
avahi should not be required by the compat libary rpm, avahi-compat-libdns_sd, and should not be installed because of dependency chains on systems where it is not installed
Additional info:
Automatic installation of daemons that open network ports and initiate broadcast traffic is a security significant event, and is unacceptable on enterprise servers. I don't believe there's any reason avahi-compat-libdns_sd should require avahi, or if there is, avahi should not be configured to run by default.
--- Additional comment from lpoetter on 2009-12-17 13:48:07 EST ---
The reason why avahi-compat-libdns_sd requires avahi is because it links against the avahi libraries that are part of the avahi package.
The proper fix would be to split the avahi libraries off into a seperate package. That would be a non-trivial packaging change however, not sure if that is suitable for fastrack.
Splitting off the libraries is already being requested in bug 530087.
Comment 1RHEL Program Management
2010-06-03 08:55:30 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
Comment 2RHEL Program Management
2010-07-15 15:16:14 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 4RHEL Program Management
2011-04-04 02:03:57 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
This request was evaluated by Red Hat Product Management for inclusion in the
current release of Red Hat Enterprise Linux. Because the affected component is
not scheduled to be updated in the current release, Red Hat is unfortunately
unable to address this request at this time. It has been proposed for the next
release. If you would like it considered as an exception in the current
release, please ask your support representative.
Comment 7RHEL Program Management
2012-07-10 07:22:29 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 9RHEL Program Management
2012-07-10 23:05:37 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
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.
http://rhn.redhat.com/errata/RHBA-2013-0368.html