Project

General

Profile

Actions
Copy link

Bug #5478

closed

Puppet Environment importing doesn't seem to handle module removal/changing

Added by Justin Sherrill about 11 years ago. Updated almost 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Orchestration
Target version:
-
Difficulty:
medium
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

fang64 in #katello hit an error where a change in a module was not properly imported into the environment:

1. Upload puppet module 'foo' with classes A, B, & C
2. Create a content and publish it to Library
3. upload a different puppet module 'foo' with classes X, Y, Z (or some subset of A, B, C)
4. Publish the new content view

Results: Under "Configuration" > Environments > Library Content View environment > Classes

the old puppet classes A, B, C will still be shown.

Actions
Copy link

Also available in: Atom PDF