Project

General

Profile

Actions

Bug #5171

closed

When editing a puppetclass parameter, wrong parameter information is displayed

Added by Anonymous over 10 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Web Interface
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

When you click on a puppet class to edit, and then navigate to the 'Smart Class Parameter' tab, the first parameter in the list is selected. However, the information on the right is for another parameter. Image attached.


Files


Related issues 2 (1 open1 closed)

Related to Foreman - Tracker #4470: Usability of parameters and overridesNew

Actions
Has duplicate Foreman - Bug #5872: smart class parameter display bugDuplicate05/22/2014Actions
Actions #1

Updated by Stephen Benjamin over 10 years ago

  • Related to Feature #4469: Overriding or setting parameter values should show available values based on type and validator added
Actions #2

Updated by Stephen Benjamin over 10 years ago

  • Related to Tracker #4470: Usability of parameters and overrides added
Actions #3

Updated by Stephen Benjamin over 10 years ago

  • Related to deleted (Feature #4469: Overriding or setting parameter values should show available values based on type and validator)
Actions #4

Updated by Dominic Cleal over 10 years ago

I've never seen this before.. it may be worth re-testing on 1.5/nightly as the UI here has been improved a bit. There's a chance whatever issue this is/was may have been fixed in the process.

Actions #5

Updated by Stephen Benjamin over 10 years ago

I see it in nightly, too.

The left panel highlights the first parameter alphabetically, while the right panel shows the first overridable parameter.

Actions #6

Updated by Dominic Cleal over 10 years ago

  • Category set to Web Interface
Actions #7

Updated by Dominic Cleal over 10 years ago

  • Has duplicate Bug #5872: smart class parameter display bug added
Actions #8

Updated by Alexandre Barth over 10 years ago

this problem still remains in 1.6.0 develop (nightly builds)

Actions #9

Updated by Alexandre Barth almost 10 years ago

do not have this problem anymore since 1.7

Actions #10

Updated by Dominic Cleal almost 10 years ago

  • Status changed from New to Resolved

Thanks for confirming!

Actions

Also available in: Atom PDF