Project

General

Profile

Bug #330

Import hosts_and_facts rakejob resets environments to "production"

Added by Josh Baird about 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Puppet integration
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

When I run the following rakejob:

rake puppet:import:hosts_and_facts RAILS_ENV=production

It re-imports all of my hosts and resets their environments to "production," even though they have a custom environment defined in the fact file:

root@fc-pupm01:/var/lib/puppet/yaml/facts$ grep fcprod *
cobtest.corp.follett.com.yaml: environment: fcprod
fc-cobbler01.corp.follett.com.yaml: environment: fcprod
...

Example fact file is attached.

cobtest.corp.follett.com.yaml cobtest.corp.follett.com.yaml 2.73 KB Josh Baird, 06/24/2010 04:56 PM

Associated revisions

Revision 4dd00cbc (diff)
Added by Ohad Levy almost 9 years ago

fixes #330 - Import hosts_and_facts rakejob resets environments to production

Revision 7a989ce5 (diff)
Added by Ohad Levy almost 9 years ago

fixes #330 - Import hosts_and_facts rakejob resets environments to production

History

#1 Updated by Jakub Heichman almost 9 years ago

I'm seeing the same thing - this prevents me from managing environments from foreman

#2 Updated by Ohad Levy almost 9 years ago

  • Category set to Puppet integration
  • Assignee set to Ohad Levy
  • Target version set to 0.1-6

does this happens as well when using the push_facts script instead?

#3 Updated by Ohad Levy almost 9 years ago

  • Status changed from New to Ready For Testing
  • % Done changed from 0 to 100

#4 Updated by Ohad Levy almost 9 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF