Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1685726 - Unhelpful error message when "Suggest IP" fails due to SSL verify error
Summary: Unhelpful error message when "Suggest IP" fails due to SSL verify error
Status: ON_QA
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Branding
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
medium vote
Target Milestone: 6.5.0
Assignee: satellite6-bugs
QA Contact: Radovan Drazny
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-05 22:18 UTC by Perry Gagne
Modified: 2019-03-09 01:33 UTC (History)
4 users (show)

Fixed In Version: tfm-rubygem-foreman_theme_satellite-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)
Screen shot of error in interfaces tab (deleted)
2019-03-05 22:20 UTC, Perry Gagne
no flags Details

Description Perry Gagne 2019-03-05 22:18:03 UTC
Description of problem:
I ran the installer using an IP address for `--foreman-proxy-dhcp-server` instead of a hostname 

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

How reproducible: Always

Steps to Reproduce:
1. Setup infoblox with a cert that only has host name, not IP address.( This seems to be the case with the using the built in Infoblox self-signed cert).
2. Run installer with `--foreman-proxy-dhcp-server` using IP of infoblox appliance, instead of hostname
3. Configure subnet in infoblox and satellite. Ensure "IPAM" set to DHCP
3. Create a new host with the subnet, got into interface tab. 

Actual results:
Auto suggest fails with error (see also attached screen shot:
"Failed to fetch a free IP from Capsule %{Capsule}: %{message}"

Expected results:
Fails with a more helpful message. 

Additional info:
This error seems to be printed for other SSL verify issues too. Ex. if the certificate was updated, and the updated trust info was not added to the satellite.

Comment 2 Perry Gagne 2019-03-05 22:20:55 UTC
Created attachment 1541167 [details]
Screen shot of error in interfaces tab

Comment 4 Lukas Zapletal 2019-03-06 09:57:25 UTC
Branding replacement issue, fixed.

Note You need to log in before you can comment on or make changes to this bug.