Project

General

Profile

Feature #1503

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

Added by Ashley Penney over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Puppet integration
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

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

Has duplicate Foreman - Bug #1439: Foreman can only use Puppetmaster's via smartproxy that expose "Puppet CA"Duplicate2012-01-09

Associated revisions

Revision ace6fbad (diff)
Added by Ohad Levy over 7 years ago

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

Revision de2ea8a9 (diff)
Added by Ohad Levy over 7 years ago

refs #1503 better handling of migrating to puppet proxies

Revision 86bdf09d (diff)
Added by Ohad Levy over 7 years ago

refs #1503, ensures that puppet proxy is not required if you are not provisioning

History

#1 Updated by Ohad Levy over 7 years ago

  • Category set to Puppet integration
  • Assignee set to Ohad Levy
  • Target version set to 1.0

#2 Updated by Ohad Levy over 7 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

#3 Updated by Ohad Levy over 7 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF