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:
On satellite with short hostname and with setting "Append domain names to the host" set to NO configure cloud connector fails on
"Cloud connector setup has failed: Error: Request failed with status code 404"
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1.install satellite 6.10 with hostname setting of in /etc/hosts
192.168.122.209 sat610beta.snemeth.test sat610beta
2. administer -> settings -> Append domain names to the host" set to NO
3. configure -> inventory upload -> configure cloud connector
Actual results:
"Cloud connector setup has failed: Error: Request failed with status code 404"
Expected results:
Cloud connector configured
Additional info:
https://github.com/theforeman/foreman_rh_cloud/blob/69ab71d3581adc13c1102367968e709652c357dd/lib/foreman_rh_cloud.rb#L101
Is looking for fqdn entry but there is just short name in db without domain
not a regression since it is reproducible on 6.9 as well.
in foreman_rh_cloud.rb
def self.foreman_host
@foreman_host ||= ::Host.unscoped.friendly.find(ENV['SATELLITE_RH_CLOUD_FOREMAN_HOST'] || ::SmartProxy.default_capsule.name)
end
to
def self.foreman_host
@foreman_host ||= ::Host.unscoped.friendly.find(`hostname -s`.chomp) || ::Host.unscoped.friendly.find(`hostname -f`.chomp)
end
it looks like that it now works for both options, if you have short name or fqdn.
Comment 8Lukáš Hellebrandt
2021-10-25 10:38:02 UTC
Verified with Sat 6.10.0 snap 23.0.
Used reporoducer from OP, cloud connector configured correctly, the service is running.
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 (Moderate: Satellite 6.10 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/RHSA-2021:4702