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 1478732 - Procedure to create new puppet environment
Summary: Procedure to create new puppet environment
Keywords:
Status: CLOSED DUPLICATE of bug 1478403
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Puppet Guide
Version: 6.2.10
Hardware: All
OS: Linux
unspecified
low
Target Milestone: Unspecified
Assignee: satellite-doc-list
QA Contact: satellite-doc-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-06 16:42 UTC by Alfredo Pizarro
Modified: 2017-08-06 16:47 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-06 16:47:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alfredo Pizarro 2017-08-06 16:42:52 UTC
Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html-single/puppet_guide/

Section Number and Name: 3.7. Puppet Environments ->  Creating Puppet Environments within Red Hat Satellite 

Describe the issue: When the procedure is followed as is, an error will arise when trying to register a new server via boostrap.py with a host group associated to this new environment recently create.

Suggestions for improvement: I'm not sure if is it a bug or missing information, but when I tried to follow the documentation it did not work. Instead, had to create a new environment creating manually a directory under /etc/puppet/environments/ and the import it from the portal. Once performed this procedure, it worked.

Additional information: When creating a new puppet environment trough satellite portal, the registration of a new server associated to this new environment trough bootstrap.py  would try to retrieve the puppet CA certificate, querying an address like this:
https://server.fqdn/https:8140/new_environment_created/certificate/ca?fail_on_404=true 
When I followed the instructions from the manual, it failed with an error "Environment not found". 
So the procedure I followed to  fix the issue was:
- I created a new directory in satellite under /etc/puppet/environments/ with the name of the new environment.
- After that, I went to Configure -> Environments -> Import from satellite. 
-  I associated the host group to the new environment 
- I re-run  boostrap.py in the server and it got registered with no issues.
Regards,
Alfredo Pizarro.

Comment 1 Alfredo Pizarro 2017-08-06 16:47:34 UTC

*** This bug has been marked as a duplicate of bug 1478403 ***


Note You need to log in before you can comment on or make changes to this bug.