Project

General

Profile

Actions

Bug #2394

open

Import Puppet Classes - deletes assigned classes

Added by Andrei Burd about 11 years ago. Updated about 10 years ago.

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

Description

checked on fresh install today:
Installed foreman on Debian squeeze with Postresql, Added Smart Proxy and imported classes.
Added class to new host, opened YAML and checked in database - class is assigned.
deleted class from repo, made new import - class deleted despite to it was assigned to host.
Update:
Foreman does not deletes the class if it was assigned on the host group, but he is deleting it if he was unassigned (good), or was assigned to host (bad).

Actions #1

Updated by Andrei Burd over 10 years ago

checked on 1.2.1 - still deletes assigned classes.

Actions #2

Updated by Andrei Burd over 10 years ago

Version 1.3.1- assigned class was deleted from class list - result collector class was removed from machine and 300 exported firewall resources been purged.

Actions #3

Updated by John Julien about 10 years ago

I might suggest adding to the UI a checkbox to allow classes to be deleted during an import, and then even a step further provide a preview/confirm. In fact, i would suggest the preview/confirm for all import runs. If your ENC is being used in production, you really want to verify any changes that are going to be made to it.

In a large environment with multiple puppet masters, it is possible that a proxy might incorrectly be returning the correct state of Puppet classes. Maybe something didn't get syncd right, or a filesystem is unmounted, etc.

This does seem like a very scary situation to have any classes not reported by a proxy automatically purged without warning.

Actions

Also available in: Atom PDF