Bug 1769459

Summary: foreman-maintain backup failed on infoblox configured satellite/capsule
Product: Red Hat Satellite Reporter: Avijit Roy <avroy>
Component: Satellite MaintainAssignee: Suraj Patil <supatil>
Status: CLOSED ERRATA QA Contact: Lucie Vrtelova <lvrtelov>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.5.0CC: ahumbe, apatel, aupadhye, inecas, jpathan, kgaikwad, kkohli, lvrtelov, mbacovsk, pcreech
Target Milestone: 6.8.0Keywords: Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_maintain-0.6.6-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 12:38:21 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:

Description Avijit Roy 2019-11-06 16:43:28 UTC
Description of problem:

While taking backup with foreman-maintain on satellite which is configured with infoblox is failing with below error:

--------------------------------------------------------------------------------
Backup config files: 
- Collecting config files to backup                                   [FAIL]    
Couldn't find DHCP Configuration file
--------------------------------------------------------------------------------

This is quite obvious because if we configure external DHCP server or infoblox /etc/dhcp/dhcpd.conf file will not get created. Hence foreman-maintain is failing to backup dhcp config file. 

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

How reproducible:

100%
Steps to Reproduce:
1. Configure satellite with infoblox according https://access.redhat.com/documentation/en-us/red_hat_satellite/6.5/html/provisioning_guide/chap-infoblox-integration
2. Try to backup satellite 

# foreman-maintain backup offline -s --features all /var/satellite/backup
3.

Actual results:

Failed with below error:

--------------------------------------------------------------------------------
Backup config files: 
- Collecting config files to backup                                   [FAIL]    
Couldn't find DHCP Configuration file
--------------------------------------------------------------------------------

---------------------------------
D, [2019-11-06 10:24:08-0500 #6054] DEBUG -- : foreman proxy content module detected: foreman_proxy_content
E, [2019-11-06 10:24:08-0500 #6054] ERROR -- : Couldn't find DHCP Configuration file (RuntimeError)
/usr/share/gems/gems/foreman_maintain-0.3.4/definitions/features/foreman_proxy.rb:186:in `lookup_dhcpd_config_file'
/usr/share/gems/gems/foreman_maintain-0.3.4/definitions/features/foreman_proxy.rb:93:in `dhcpd_config_file'
/usr/share/gems/gems/foreman_maintain-0.3.4/definitions/features/foreman_proxy.rb:63:in `config_files'
/usr/share/gems/gems/foreman_maintain-0.3.4/definitions/procedures/backup/config_files.rb:32:in `config_files'
/usr/share/gems/gems/foreman_maintain-0.3.4/definitions/procedures/backup/config_files.rb:20:in `block in run'
/usr/share/gems/gems/foreman_maintain-0.3.4/lib/foreman_maintain/reporter/cli_reporter.rb:141:in `with_spinner'
/usr/share/gems/gems/foreman_maintain-0.3.4/definitions/procedures/backup/config_files.rb:19:in `run'

----------------------------

Expected results:

foreman-maintain should check if DHCP is configured with infoblox and act accordingly. 
Additional info:

Comment 5 Brad Buckingham 2019-11-08 21:42:10 UTC
*** Bug 1769461 has been marked as a duplicate of this bug. ***

Comment 8 Suraj Patil 2020-05-04 13:08:49 UTC
Created redmine issue https://projects.theforeman.org/issues/29687 from this bug

Comment 9 Bryan Kearney 2020-05-04 16:55:35 UTC
Upstream bug assigned to supatil

Comment 11 Bryan Kearney 2020-06-25 12:01:21 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/29687 has been resolved.

Comment 15 errata-xmlrpc 2020-10-27 12:38:21 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 (Satellite 6.8 Satellite Maintenance Release), 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://access.redhat.com/errata/RHBA-2020:4365