Project

General

Profile

Actions
Copy link

Feature #1503

closed

When creating a host, it should be possible to define a Puppet CA and a Puppet Master to use

Added by Ashley Penney about 13 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ohad Levy
Category:
Puppet integration
Target version:
1.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Hi,

We have a single puppetmaster acting as the certificate master (don't ask). Right now Foreman will try to autosign.conf whichever puppetmaster is set as the current proxy - even if it lacks the CA role.

I would like Foreman at the minimum to refuse to set build status on a machine pointing at a Puppetmaster without CA.
Better would be if Foreman could set cert master and puppetmaster seperately and do the right thing based on that.

Related issues 1 (0 open — 1 closed)

Has duplicate Foreman - Bug #1439: Foreman can only use Puppetmaster's via smartproxy that expose "Puppet CA"DuplicateAshley Penney01/09/2012Actions
Actions
Copy link
 #1

Updated by Ohad Levy about 13 years ago

  • Category set to Puppet integration
  • Assignee set to Ohad Levy
  • Target version set to 1.0
Actions
Copy link
 #2

Updated by Ohad Levy about 13 years ago

  • Tracker changed from Bug to Feature
  • Subject changed from Puppet tries to write to autosign on the Puppetmaster you set regardless of proxy roles. to When creating a host, it should be possible to define a Puppet CA and a Puppet Master to use
Actions
Copy link
 #3

Updated by Ohad Levy about 13 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF