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.
Bug 1160358 - subscription-manager from consumer doesn't know how to handle a satellite6 installed with cname
Summary: subscription-manager from consumer doesn't know how to handle a satellite6 in...
Keywords:
Status: CLOSED DUPLICATE of bug 1160344
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: 6.0.3
Hardware: All
OS: Linux
high
high
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-04 15:39 UTC by Dave Sullivan
Modified: 2021-12-10 14:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-10 18:16:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Dave Sullivan 2014-11-04 15:39:21 UTC 
Description of problem:

satellite fqdn: abc123-us.acme.com
satellite cname: satellite.nomura.com


I have installed my satellite 6 with CNAME “satellite.acme.com” and created all required certificates using 

katello-installer --foreman-db-password foreman --foreman-db-username foreman --katello-proxy-url http://applicationwebproxy.acme.com --katello-proxy-port 8080 --certs-ca-common-name "satellite.acme.com" --certs-node-fqdn "satellite.acme.com" --capsule-parent-fqdn "satellite.acme.com" --foreman-foreman-url="https://satellite.acme.com" --foreman-admin-password changeme

 

Now when I try to register consumer I am getting some error …  did I miss something ?
 

[root@xyz123 product]# subscription-manager register --org ACME --name=xyz123.acme.com

Username: admin

Password:

Peer certificate subjectAltName does not match host, expected abc123-us.acme.com, got DNS:satellite.nomura.com


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

This can be worked around by modifying /etc/rhsm/rhsm.conf on the consumer to point to the cname

hostname = satellite.acme.com
Comment 2 Mike McCune 2014-11-06 16:34:22 UTC 
We require a FQDN and not a CName for Satellite as noted in our Installation Guide:

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html-single/Installation_Guide/index.html#Prerequisites3

We are unlikely to change this in the near term and this could be considered an RFE if it is a feature we should evaluate. If you feel we should re-evaluate this bug as an RFE feel free to re-open with justification.
Comment 4 Dave Sullivan 2015-07-25 19:59:16 UTC 
If cluster is handling hostname/vip movement cnames are not necessarily needed dns A records could be used instead.

Which makes this a little less important.
Comment 7 Bryan Kearney 2016-07-08 20:20:41 UTC 
Per 6.3 planning, moving out non acked bugs to the backlog
Note You need to log in before you can comment on or make changes to this bug.