JS to update puppet classes tab does not fire when not using Content Views
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.
1) Import some puppet modules into Foreman
2) Click New Host
3) Leave Lifecycle blank and select your puppet env in Content View
Puppet Classes tab now allows selecting classes from that env
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.
#9 Updated by John Mitsch 9 months ago
- Target version deleted (
- Status changed from New to Rejected
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.