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.
Verified with Sat6.3 snap30.
Performed below steps:
1.Change the client hostname to shortname instead of FQDN( # hostname and #hostname -f o/p should be different)
~]# hostname
cloud-qe-09
[root@cloud-qe-09 ~]# hostname -f
cloud-qe-09.eng.bos.abc.com
2.Register the same to Satellite
]# subscription-manager register --org Default_Organization --activationkey 'ak_rhel7'
The system has been registered with ID: 338d7e45-b79e-4f35-9558-2af08c6f7f42
Installed Product Current Status:
Product Name: Red Hat Enterprise Linux Server
Status: Subscribed
3.Then, installed the puppet agent and make necessary changes to /etc/puppet/puppet.conf
[root@cloud-qe-09 yum.repos.d]# vi /etc/puppet/puppet.conf
[root@cloud-qe-09 yum.repos.d]# puppet agent -t
Info: Creating a new SSL key for cloud-qe-09.eng.bos.abc.com
Info: Caching certificate for ca
Info: csr_attributes file loading from /etc/puppet/csr_attributes.yaml
Info: Creating a new SSL certificate request for cloud-qe-09.idmqe.lab.eng.bos.redhat.com
Info: Certificate Request fingerprint (SHA256): E2:36:E6:CF:A7:B5:0A:A2:CC:3B:78:20:8E:FE:C9:37:4C:80:D2:C2:5C:AC:9C:62:88:7B:4D:A1:F2:A8:B6:96
Info: Caching certificate for ca
Exiting; no certificate found and waitforcert is disabled
4.Create the puppet client certificate by executing "puppet agent -t" and signed it in Satellite.
# puppet cert sign --all
Notice: Signed certificate request for cloud-qe-09.eng.bos.abc.com
Notice: Removing file Puppet::SSL::CertificateRequest cloud-qe-09.eng.bos.abc.com at '/var/lib/puppet/ssl/ca/requests/cloud-qe-09.eng.bos.abc.com.pem'
5. Again, execute below command on the client:
---
# puppet agent -t
Info: Caching certificate for cloud-qe-09.eng.bos.abc.com
Info: Retrieving pluginfacts
Info: Retrieving plugin
Notice: /File[/var/lib/puppet/lib/puppet]/ensure: created
Notice: /File[/var/lib/puppet/lib/puppet/provider]/ensure: created
::::::
Notice: /File[/var/lib/puppet/lib/puppet/parser/functions/validate_cmd.rb]/ensure: defined content as '{md5}78fd21cb3fc52efc3b53ba2b3301de18'
Info: Loading facts
Info: Caching catalog for cloud-qe-09.eng.bos.abc.com
Info: Applying configuration version '1514461504'
Info: Creating state file /var/lib/puppet/state/state.yaml
Notice: Finished catalog run in 0.03 seconds
I don't see duplicate Hosts under 'All hosts' , host was registered as cloud-qe-09.eng.bos.abc.com.
Comment 6Satellite Program
2018-02-21 16:54:37 UTC
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-2018:0336