Project

General

Profile

Actions

Bug #31625

closed

Puppet Environments are not listed properly in the SCP details page

Added by Tomer Brisker over 3 years ago. Updated over 3 years ago.

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

Description

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

Description of problem:
The Puppet Environments are not listed properly in Smart Class Parameters details page, based on the selected Organization taxonomy.

Version-Release number of selected component (if applicable):
6.8.2, 6.9.0

How reproducible:
always

Steps to Reproduce:
1. Have a Satellite with two or more organizations and two or more puppet environments containing a class with parameters
2. Go to Configure > Classes > select some class with params > tab "Smart Class Parameter"
3. See the Puppet Environments field and try to change the Organization scope

Actual results:
environments are not listed properly, for example:
", common, and production"
"KT_abc_Library_def_1, common, and"
", , and KT_abc_Library_def_1"

Expected results:
better phrasing

Additional info:
see the attached screenshots

Actions #1

Updated by The Foreman Bot over 3 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Tomer Brisker
  • Pull request https://github.com/theforeman/foreman/pull/8247 added
Actions #2

Updated by The Foreman Bot over 3 years ago

  • Pull request https://github.com/theforeman/foreman/pull/8248 added
Actions #3

Updated by Tomer Brisker over 3 years ago

  • Pull request deleted (https://github.com/theforeman/foreman/pull/8248)
Actions #4

Updated by Ondřej Ezr over 3 years ago

  • Category changed from PuppetCA to Puppet integration
Actions #5

Updated by The Foreman Bot over 3 years ago

  • Fixed in Releases 2.4.0 added
Actions #6

Updated by Tomer Brisker over 3 years ago

  • Status changed from Ready For Testing to Closed
Actions #7

Updated by Tomer Brisker over 3 years ago

  • Fixed in Releases 2.3.4 added
Actions #8

Updated by Tomer Brisker over 3 years ago

  • Fixed in Releases deleted (2.3.4)
Actions #9

Updated by Lukas Zapletal about 3 years ago

  • Related to Bug #31631: Booting to anaconda with bond configured run into timeout added
Actions #10

Updated by Tomer Brisker about 3 years ago

  • Related to deleted (Bug #31631: Booting to anaconda with bond configured run into timeout)
Actions

Also available in: Atom PDF