Project

General

Profile

Bug #6257

JS to update puppet classes tab does not fire when not using Content Views

Added by Greg Sutcliffe about 5 years ago. Updated about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Hosts
Target version:
Difficulty:
easy
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

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.

History

#1 Updated by Eric Helms about 5 years ago

  • Target version set to 48
  • Difficulty set to easy
  • Triaged changed from No to Yes

#2 Updated by Eric Helms about 5 years ago

  • Target version changed from 48 to 49

#3 Updated by Eric Helms about 5 years ago

  • Target version changed from 49 to 54

#4 Updated by Eric Helms about 5 years ago

  • Target version deleted (54)

#5 Updated by Eric Helms over 3 years ago

  • Legacy Backlogs Release (now unused) set to 86

#6 Updated by Eric Helms over 3 years ago

  • Legacy Backlogs Release (now unused) changed from 86 to 144

#7 Updated by Eric Helms about 3 years ago

  • Legacy Backlogs Release (now unused) changed from 144 to 168

#8 Updated by Eric Helms about 3 years ago

  • Legacy Backlogs Release (now unused) changed from 168 to 114

Also available in: Atom PDF