Bug 1746581

Summary: Gem loading error when enabling infoblox plugins
Product: Red Hat Satellite Reporter: Perry Gagne <pgagne>
Component: Infoblox integrationAssignee: Lukas Zapletal <lzap>
Status: CLOSED ERRATA QA Contact: Perry Gagne <pgagne>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.6.0Keywords: Regression, Triaged
Target Milestone: 6.6.0   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: smart_proxy_dhcp_infoblox-0.0.15 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 12:47:58 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: 1720200    

Description Perry Gagne 2019-08-28 20:24:17 UTC
Description of problem: When configuring infoblox plugins using the installer an error occurs when trying to load the infoblox gem. 


Version-Release number of selected component (if applicable): 6.6. snap 17


How reproducible: Always


Steps to Reproduce:
1. Run installer with infoblox options 

Actual results:
Installer error with:
Aug 28 14:20:12 satellite.example.com smart-proxy[4369]: /usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext/output.rb:13:in `strict_err': Gem loading error: Could not find 'infoblox' (>= 2.0.4, ~> 2.0) - did find: [infoblox-3.0.0] (RuntimeError)

Expected results:
Installer success. 

Additional info:
Attached foreman debug.

Comment 4 Lukas Zapletal 2019-08-30 09:08:57 UTC
BLOCKER, fixed in smart_proxy_dhcp_infoblox-0.0.15 (DNS should be fine).

Comment 5 Perry Gagne 2019-09-09 19:02:59 UTC
Verified fix in sat 6.6 snap 19. 

Was able to configure infoblox plugin on both satellite and external capsule.

Comment 7 errata-xmlrpc 2019-10-22 12:47:58 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://access.redhat.com/errata/RHSA-2019:3172