Project

General

Profile

Actions

Bug #5478

closed

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

Added by Justin Sherrill almost 10 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Orchestration
Target version:
-
Difficulty:
medium
Triaged:
Yes
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.

Actions #1

Updated by Justin Sherrill almost 10 years ago

Step 4 should say:

4. Publish a new version of the content view

Actions #2

Updated by Justin Sherrill almost 10 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.

Actions #3

Updated by Eric Helms almost 10 years ago

  • Difficulty set to medium
  • Triaged changed from No to Yes
Actions #4

Updated by Eric Helms over 8 years ago

  • translation missing: en.field_release set to 114
Actions #5

Updated by John Mitsch over 4 years ago

  • Status changed from New to Rejected
  • Target version deleted (Katello Backlog)

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Actions

Also available in: Atom PDF