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.

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:

Closing this bug as requested by Jitendra - the puppet run from provisioning template(while provisioning) is working as expected.