Project

General

Profile

Actions

Bug #8766

closed

Chef reports do not create host in correct environment

Added by Romain Vrignaud about 9 years ago. Updated almost 9 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
foreman_chef
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

It seems that when Foreman get a chef report from unknown host, it creates the host in the default Foreman environment.
It should instead use the chef environment of the host.


Related issues 2 (0 open2 closed)

Related to Chef - Feature #9843: Provide chef client environment as a factClosedMarek Hulán03/19/2015Actions
Related to Chef - Feature #9844: Add own fact parser that will parse all attributes except interfacesClosedMarek Hulán03/19/2015Actions
Actions #1

Updated by Marek Hulán almost 9 years ago

So we should probably first try to sync environments from the Chef and then we can map it in Foreman.

Actions #2

Updated by Marek Hulán almost 9 years ago

So I did a bit of research and chef_environment is not a part of attributes. So the only way we can get it into Foreman correctly is by asking Chef, which may be a bit time costly with every fact import. Maybe we could ask only if no environment is set. Romain, any other ideas?

EDIT: obviously environment wouldn't be updated on later change in Chef
EDIT2: I'll check if chef-handler-foreman could add this for us

Actions #3

Updated by Marek Hulán almost 9 years ago

  • Related to Feature #9843: Provide chef client environment as a fact added
Actions #4

Updated by Marek Hulán almost 9 years ago

  • Category set to foreman_chef
  • Status changed from New to Duplicate

Fixed as a part of more generic #9844, thanks for report.

Actions #5

Updated by Marek Hulán almost 9 years ago

  • Related to Feature #9844: Add own fact parser that will parse all attributes except interfaces added
Actions

Also available in: Atom PDF