Bug 1723795 - GCE client connecting to the wrong Puppet CA
Summary: GCE client connecting to the wrong Puppet CA
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - GCE
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: 6.6.0
Assignee: Kavita
QA Contact: Jitendra Yejare
URL:
Whiteboard:
Depends On:
Blocks: 1721890
TreeView+ depends on / blocked
 
Reported: 2019-06-25 12:14 UTC by Jitendra Yejare
Modified: 2019-07-04 17:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-04 17:58:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jitendra Yejare 2019-06-25 12:14:17 UTC 
Description of problem:
On provisioning a client onto GCE, while performing template execution, the puppet-agent tries to connect to the incorrect/plain(HTTP:/puppet/) puppet CA instead of satellite or proxy.
And hence puppet-agent isn't able to apply puppet modules associated for that provisioned host.

Version-Release number of selected component (if applicable):
Satellite 6.6 snap 7

How reproducible:
Always

Steps to Reproduce:
1. Provision a client on GCE
2. Select satellite as puppet CA in host page while provisioning.

Actual results:
The client attempts to connect to the wrong puppet CA instead of satellite affecting facts gathering, puppet module apply.

Expected results:
The client should connect to correct puppet CA provided in GCE provisioning form.

Additional info:
Comment 5 Anurag Patel 2019-07-04 17:58:22 UTC 
Closing this bug as requested by Jitendra - the puppet run from provisioning template(while provisioning) is working as expected.
Note You need to log in before you can comment on or make changes to this bug.