Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
Created attachment 1558982[details]
Correct error message
Verified on Sat 6.5 Snap 25. Unsuccessful connection to a capsule ends with a more helpful message:
Failed to fetch a free IP from Capsule capsule.example.com (https://capsule.example.com:9090): ERF12-8202 [ProxyAPI::ProxyException]: Unable to retrieve unused IP ([RestClient::Forbidden]: 403 Forbidden) for Capsule https://capsule.example.com:9090/dhcp
See the attached image
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:1222
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.