Project

General

Profile

Actions

Feature #20827

open

Support for single puppet CA

Added by Ondřej Pražák almost 7 years ago. Updated almost 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
PuppetCA
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

1. What is the nature and description of the request?

[Foreman]<<-->>[Capsule]<<-->>Clients

All the clients are registered to capsule server and the puppet agents running in those clients are able to communicate properly. However, managing this capsule server as puppet agent and main foreman server as puppet master is not possible as the issue over here is, capsule server cannot connect to foreman server for puppet CA as both the capsule and foreman has their own independent CA for puppet.

2. Why does the user need this? (List the business requirements here)
To manage capsule node as puppet agent

Actions #1

Updated by Ondřej Pražák almost 7 years ago

  • Subject changed from Support for single puppet CA to Support for single puppet CA
  • Category set to PuppetCA
  • Priority changed from High to Normal
Actions

Also available in: Atom PDF