Project

General

Profile

Actions

Bug #20769

open

Changed default of Puppet parameter not visible on smart parameter edit page

Added by Sebastian Gräßl almost 7 years ago. Updated almost 7 years ago.

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

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1334521

Description of problem:
If I import a new version of a module, with a different default for one of it's parameters into a CV in a certain lifecycle environment, I would expect to be able to switch between environments on Satellite's smart parameter edit page (.../puppetclasses/157-bar/edit) and see the default change.

I only see the value of the first class that was imported though: the default never changes when selecting another environment, even though this is valuable information.

Version-Release number of selected component (if applicable):
6.2.0 SNAP 10

How reproducible:

Steps to Reproduce:
1. Upload / import a module, make sure it ends up in a published CV
2. Change a default parameter value for the module, upload / import it again and make sure it ends up in a published CV; make sure the two CVs are in different life cycle environments, so the second one doesn't overwrite the first one
3. Go to .../puppetclasses/157-bar/edit for this module

Actual results:
Switching the environment shows no change in the default value field of the parameter

Expected results:
Switching the environment shows that you changed the default value of the parameter

Additional info:
Modules that use a params.pp aren't touched by this, but there are enough modules out there that do not have all default values in a params.pp

Actions #1

Updated by Sebastian Gräßl almost 7 years ago

  • Subject changed from Changed default of Puppet parameter not visible on smart parameter edit page to Changed default of Puppet parameter not visible on smart parameter edit page
  • Category set to Puppet integration
Actions #2

Updated by Marek Hulán almost 7 years ago

Sebastian, it seems the report is about puppet modules in content views. While some work would be required on Foreman side too, should this ticket be moved to Katello project which introduced content views?

Actions

Also available in: Atom PDF