Bug 1714604

Summary:	Puppet certs not getting signed automatically on provisioned host
Product:	Red Hat Satellite	Reporter:	Nikhil Kathole <nkathole>
Component:	Provisioning	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Nikhil Kathole <nkathole>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.6.0	CC:	dvoss, ekohlvan, inecas, oprazak, spetrosi, sshtein
Target Milestone:	6.6.0	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:	Puppet certificates are not getting signed automatically on a provisioned host.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-22 12:47:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nikhil Kathole 2019-05-28 12:42:50 UTC

Description of problem:

Puppet certs not getting signed automatically on provisioned host.


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


How reproducible:
always

Steps to Reproduce:
1. Create host with puppet configurations (In my case provisioned on libvirt)
2. Login to provisioned host
3. puppet agent -t
Exiting; no certificate found and waitforcert is disabled

Actual results:
Puppet certs are not signed automatically after provisioning.

Expected results:
Certs should be signed automatically.

Additional info:
Regression.

Comment 8 Ondřej Pražák 2019-09-02 14:14:09 UTC

This is already fixed, could QE verify?

Comment 9 Nikhil Kathole 2019-09-03 05:39:51 UTC

VERIFIED

Version tested:
Satellite 6.6.0 snap 18

Certs signed automatically on provisioned hosts.

Comment 11 errata-xmlrpc 2019-10-22 12:47: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-2019:3172