Bug #9609

Cannot assign puppet classes to new host

Added by Bryce Nordgren about 4 years ago. Updated 9 months ago.

Target version:
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:


Running Katello 2.1 ; Foreman 1.7.2

When I create a new host and click on the "Puppet Classes" tab, I get a message: "WARNING! Please select an environment first". Yet on the front page, the environment is set to "production".

After the host is provisioned, I can edit it and add classes just fine.

Puppet classes have been imported into the environment prior to attempting the host creation.

This behavior is the same for bare metal hosts and openstack hosts.

I have not done anything with the Katello organizations/locations. Everything is "default."


#1 Updated by Ohad Levy about 4 years ago

  • Project changed from Foreman to Katello
  • Category changed from Host creation to 83
  • Triaged set to No

this does not happen in foreman itself, and is most likely related to how katello extends the foreman host form.

#2 Updated by Eric Helms about 4 years ago

  • Target version set to 67
  • Legacy Backlogs Release (now unused) set to 23
  • Triaged changed from No to Yes

#3 Updated by Eric Helms about 4 years ago

  • Legacy Backlogs Release (now unused) changed from 23 to 31

#4 Updated by Eric Helms about 4 years ago

  • Target version changed from 67 to 68

#5 Updated by Eric Helms almost 4 years ago

  • Target version deleted (68)

#6 Updated by Stephen Benjamin over 3 years ago

  • Priority changed from Normal to High
  • Legacy Backlogs Release (now unused) changed from 31 to 70

#7 Updated by Justin Sherrill over 3 years ago

  • Status changed from New to Rejected

I'm not able reproduce this in 2.4 and I believe it was resolved by the changes that occured in 2.2. If this is still occurring, please reopen and I'd be happy to take another look.

Also available in: Atom PDF