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

Bug 1782753

Summary: Disable goferd on RHV Host Images
Product: Red Hat Enterprise Virtualization Manager Reporter: Marko Myllynen <myllynen>
Component: ovirt-hostAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED DUPLICATE QA Contact: Lucie Leistnerova <lleistne>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.3.6   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-12 10:47:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marko Myllynen 2019-12-12 09:50:19 UTC 
Description of problem:
RH Satellite versions prior 6.2.11 used to require goferd for remote execution, however since RH Satellite 6.2.11 goferd is not required anymore and given that RH Satellite 6.3 is already unsupported there seems to be no reason to include or at least enable by default goferd on RHV Host Images. We have also seen goferd leaking memory once or twice leading to issues with a Host (but we haven't collected the required data for troubleshooting goferd) so running it needlessly is certainly unhelpful.

For more background information please see:

https://access.redhat.com/articles/3875321
https://access.redhat.com/articles/3154811
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html-single/managing_hosts/index#sect-Red_Hat_Satellite-Managing_Hosts-Host_Management_without_Goferd-Making_Host_Management_without_Goferd_the_System_Default

Please consider removing or at least disabling goferd by default on RHV Host Images.

Version-Release number of selected component (if applicable):
RHV 4.3.6
Comment 1 Marko Myllynen 2019-12-12 10:47:19 UTC 

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