Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 794864

Summary: RFE: Remove avahi
Product: [Retired] oVirt Reporter: Perry Myers <pmyers>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: acathrow, cshao, dallan, dyasny, fdeutsch, gouyang, jboggs, leiwang, mburns, ovirt-bugs, ovirt-maint, ycui
Target Milestone: ---Keywords: FutureFeature, Reopened
Target Release: 3.4.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 2.4.0 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-14 13:35:29 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:    
Bug Blocks: 829023    

Description Perry Myers 2012-02-17 19:40:14 UTC 
avahi is included by libvirt, but this can be disabled manually and the dependency removed.

So, need to remove avahi from the images via package blacklisting and configure libvirt to not look for avahi

* add mdns_adv = 0 to libvirtd.conf
* rpm --erase --force avahi* in the blacklisting section of the
  kickstart
Comment 1 Fabian Deutsch 2012-03-28 09:06:32 UTC 
libvirtd is linked against files in avahi-libs, so I don't see that we can just remove those libs, even if we disable mdns support in the conf.

$ ldd /usr/sbin/libvirtd | grep avahi
	libavahi-common.so.3 => /usr/lib64/libavahi-common.so.3 (0x0000003a06a00000)
	libavahi-client.so.3 => /usr/lib64/libavahi-client.so.3 (0x0000003a08e00000)

Did you have other thoughts?

At least we can disable avahi in the conf.
Comment 2 Mike Burns 2012-03-28 12:07:14 UTC 
Dave, 

You confirmed that avahi isn't used by libvirt at all anymore right?  Is there a reason it's still linked?  Can we drop the package completely from ovirt-node or should we keep the package and only disable the service.
Comment 3 Dave Allan 2012-03-28 13:51:53 UTC 
It's still linked against avahi because the user can turn on avahi if they wish, so avahi-libs can't be removed.  The daemon can be, however.
Comment 4 Fabian Deutsch 2012-03-28 15:15:06 UTC 
The avahi daemon is already removed from node thus I'm closing this.
Comment 5 Fabian Deutsch 2012-03-28 16:06:06 UTC 
Sorry for the noise.
There is still this small patch wich disables avahi in libvirt:
http://gerrit.ovirt.org/3171