Bug #6257
closed
JS to update puppet classes tab does not fire when not using Content Views
Description
On the New Host form, when using the direct-access puppet method (where lifecycle is left blank and content-view lists puppet environments) the puppet classes tab does not react to changes.
To reproduce:
1) Import some puppet modules into Foreman
2) Click New Host
3) Leave Lifecycle blank and select your puppet env in Content View
Expected behaviour:
Puppet Classes tab now allows selecting classes from that env
Actual Behaviour
Puppet Classes still shows "Please select an environment"
As a workaround, one can save the new host in the puppet env, and then go back to #edit and select classes correctly. As such, I think it's just the JS not updating that tab on change of environment.
Updated by Eric Helms almost 10 years ago
- Target version set to 48
- Difficulty set to easy
- Triaged changed from No to Yes
Updated by Eric Helms over 8 years ago
- translation missing: en.field_release set to 86
Updated by Eric Helms about 8 years ago
- translation missing: en.field_release changed from 86 to 144
Updated by Eric Helms almost 8 years ago
- translation missing: en.field_release changed from 144 to 168
Updated by Eric Helms almost 8 years ago
- translation missing: en.field_release changed from 168 to 114
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.