Project

General

Custom queries

Profile

Actions
Copy link

Bug #13911

open

puppet cert is not revoked when host is deleted if ':unattended: false' is set

Added by Matt Cahill about 9 years ago. Updated almost 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
PuppetCA
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
1347242
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

If :unattended: is set to true and a particular host is managed by foreman then when deleting the host from foreman the associated puppet certificate will be removed as well.

When :unattended: is set to false there is no way to manage a host in the UI and as a result deleting a host from foreman never triggers foreman-proxy to remove the puppet cert.

I think expected behaviour should be that when :unattended: is false management of puppetca proxy elements should only depend on the state of the 'Manage PuppetCA' UI setting.

Foreman 1.10.2
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]
Ubuntu 14.04.4 LTS
Puppet 3.8.6

Related issues 1 (1 open — 0 closed)

Related to Foreman - Feature #8271: ON delete host, delete also unmanaged certificates from puppet CANew11/04/2014Actions
Actions
Copy link
 #1

Updated by Dominic Cleal about 9 years ago

  • Related to Feature #8271: ON delete host, delete also unmanaged certificates from puppet CA added
Actions
Copy link
 #2

Updated by Dominic Cleal about 9 years ago

  • Subject changed from foreman does not initiate puppet cert revoke and destroy when host is deleted if ':unattended: false' is set in /etc/foreman/settings.yaml to puppet cert is not revoked when host is deleted if ':unattended: false' is set
  • Category set to PuppetCA
Actions
Copy link
 #3

Updated by Bryan Kearney almost 9 years ago

  • Bugzilla link set to 1347242
Actions
Copy link

Also available in: Atom PDF