Bug #31625
Puppet Environments are not listed properly in the SCP details page
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
Associated revisions
History
#1
Updated by The Foreman Bot about 2 years ago
- Assignee set to Tomer Brisker
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/8247 added
#2
Updated by The Foreman Bot about 2 years ago
- Pull request https://github.com/theforeman/foreman/pull/8248 added
#3
Updated by Tomer Brisker about 2 years ago
- Pull request deleted (
https://github.com/theforeman/foreman/pull/8248)
#4
Updated by Ondřej Ezr about 2 years ago
- Category changed from PuppetCA to Puppet integration
#5
Updated by The Foreman Bot about 2 years ago
- Fixed in Releases 2.4.0 added
#6
Updated by Tomer Brisker about 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|55f57d372ba68508f319ff49f3c394df01c27572.
#7
Updated by Tomer Brisker almost 2 years ago
- Fixed in Releases 2.3.4 added
#8
Updated by Tomer Brisker almost 2 years ago
- Fixed in Releases deleted (
2.3.4)
#9
Updated by Lukas Zapletal almost 2 years ago
- Related to Bug #31631: Booting to anaconda with bond configured run into timeout added
#10
Updated by Tomer Brisker almost 2 years ago
- Related to deleted (Bug #31631: Booting to anaconda with bond configured run into timeout)
Fixes #31625 - Correctly display environments for class params
In case there is a taxonomy scope active and a certain param is present
in an environment that isn't in the current scope, the field showing
environments will display empty strings for this envirionment.