Project

General

Profile

Bug #5478

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

Added by Justin Sherrill about 5 years ago. Updated 12 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Orchestration
Target version:
Difficulty:
medium
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

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.

History

#1 Updated by Justin Sherrill about 5 years ago

Step 4 should say:

4. Publish a new version of the content view

#2 Updated by Justin Sherrill about 5 years ago

The key here is that the 2 modules need to have the same name, but the 2nd module needs to be missing some set of classes.

#3 Updated by Eric Helms about 5 years ago

  • Difficulty set to medium
  • Triaged changed from No to Yes

#4 Updated by Eric Helms over 3 years ago

  • Legacy Backlogs Release (now unused) set to 114

Also available in: Atom PDF