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.

Bug 1124597

Summary: Unable to register a host with 'subscription-manager': "Unable to verify server's identity:"
Product: Red Hat Satellite Reporter: Esa Varemo <esa>
Component: RegistrationAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED NOTABUG QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: NightlyCC: bbuckingham, esa, sthirugn, tomckay
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-01 15:22:18 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:
Attachments:
Description Flags
/etc/rhsm/rhsm.conf none

Description Esa Varemo 2014-07-29 21:26:31 UTC 
Created attachment 922354 [details]
/etc/rhsm/rhsm.conf

Description of problem:


Version-Release number of selected component (if applicable):
Trying to use 'subscription-manager' to register an existing host end up with "Unable to verify server's identity:"



How reproducible: Always



Steps to Reproduce:
1. Run `yum -y --nogpgcheck install http://foretello.ikioma/pub/katello-ca-consumer-foretello-1.0-1.noarch.rpm`
2. Run `subscription-manager register --org="ikioma" --activationkey="Centos6-x86_64"` or `subscription-manager register --org="ikioma" --environment="Library"`



Actual results:
Username prompt if --activationkey not specified.

The following error:
Unable to verify server's identity:



Expected results:
Host registers with foretello.


Additional info:


# foreman-debug


 HOSTNAME: foretello.ikioma
       OS: redhat
  RELEASE: CentOS release 6.5 (Final)
  FOREMAN: 1.6.0-develop
     RUBY: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
   PUPPET: 3.6.2
  DENIALS: 366


A debug file has been created: /tmp/foreman-debug-GH8YC.tar.xz (232428 bytes)

You may want to upload the tarball to our public server via rsync. There is a
write only directory (readable only by Foreman core developers) for that. Note
the rsync transmission is UNENCRYPTED:

  rsync /tmp/foreman-debug-GH8YC.tar.xz rsync://theforeman.org/debug-incoming

Do you want to do this now? [y/N] y
Uploading...
The tarball has been uploaded, please contact us on mailing list or IRC.



# rpm -q foreman
foreman-1.6.0-0.develop.201407231606git49f11eb.el6.noarch

# rpm -q katello
katello-1.5.0-14.201407251440git86d0337.el6.noarch

# rpm -q candlepin
candlepin-0.9.21-1.el6.noarch

# rpm -qa |grep pulp
pulp-katello-0.3-3.el6.noarch
python-kombu-3.0.15-11.pulp.el6.noarch
createrepo-0.9.9-21.2.pulp.el6.noarch
pulp-nodes-common-2.4.0-0.24.beta.el6.noarch
python-isodate-0.5.0-1.pulp.el6.noarch
pulp-puppet-tools-2.4.0-0.24.beta.el6.noarch
python-pulp-common-2.4.0-0.24.beta.el6.noarch
python-rhsm-1.8.0-1.pulp.el6.x86_64
pulp-server-2.4.0-0.24.beta.el6.noarch
pulp-nodes-parent-2.4.0-0.24.beta.el6.noarch
m2crypto-0.21.1.pulp-8.el6.x86_64
python-pulp-puppet-common-2.4.0-0.24.beta.el6.noarch
pulp-rpm-plugins-2.4.0-0.24.beta.el6.noarch
pulp-selinux-2.4.0-0.24.beta.el6.noarch
python-pulp-rpm-common-2.4.0-0.24.beta.el6.noarch
mod_wsgi-3.4-1.pulp.el6.x86_64
pulp-puppet-plugins-2.4.0-0.24.beta.el6.noarch
python-pulp-bindings-2.4.0-0.24.beta.el6.noarch
Comment 1 RHEL Program Management 2014-07-29 21:34:04 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Tom McKay 2014-07-30 18:31:47 UTC 
Looking at logs I see errors in production.log related to communicating with pulp and /var/log/messages seems to indicate that mongodb is unreachable.

Please confirm that 'katello-service status' shows that mongodb is running and listening.

Any further information on your setup may help (proxy? enforcing?).
Comment 4 Esa Varemo 2014-09-01 15:22:18 UTC 
The reason was that the database was on a partition that was not mounted. So no bug, just a user error.