Bug 1732488 - Template should include puppet service start instruction at the time of image provisioning
Summary: Template should include puppet service start instruction at the time of image...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning Templates
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.6.0
Assignee: Kavita
QA Contact: Jitendra Yejare
URL:
Whiteboard:
Depends On:
Blocks: 1721890
TreeView+ depends on / blocked
 
Reported: 2019-07-23 12:48 UTC by Kavita
Modified: 2019-10-22 19:49 UTC (History)
4 users (show)

Fixed In Version: foreman-1.22.0.10-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:49:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27297 0 None None None 2019-07-23 12:48:34 UTC

Description Kavita 2019-07-23 12:48:34 UTC
Description of problem:

In case of Google compute resource,
when user tries to provision a host with puppet enabled then puppet communication between client machine and server won't work.

After debugging, it is found that puppet service is down at the time of agent run through template.

Expected behavior - In case of image provisioning, template should include puppet service start instruction.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 Bryan Kearney 2019-10-22 19:49:34 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-2019:3172


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