Bug #330
Import hosts_and_facts rakejob resets environments to "production"
| Status: | Closed | Start: | 06/24/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | % Done: | 100% |
||
| Category: | Puppet integeration | |||
| Target version: | 0.1-6 | |||
| Backlog: | Difficulity: | |||
| Votes: | 0 |
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.
Associated revisions
Revision 4dd00cbc2ff9493af7b5290650e64f7c8258dff1
fixes #330 - Import hosts_and_facts rakejob resets environments to production
Revision 7a989ce50ef656c13a69478ddffb0caa58d4d34c
fixes #330 - Import hosts_and_facts rakejob resets environments to production
History
Updated by Jakub Heichman over 1 year ago
I'm seeing the same thing - this prevents me from managing environments from foreman
Updated by Ohad Levy over 1 year ago
- Category set to Puppet integeration
- Assigned to set to Ohad Levy
- Target version set to 0.1-6
does this happens as well when using the push_facts script instead?
Updated by Ohad Levy over 1 year ago
- Status changed from New to Ready For Testing
- % Done changed from 0 to 100
Applied in changeset 4dd00cbc2ff9493af7b5290650e64f7c8258dff1.
Updated by Ohad Levy over 1 year ago
- Status changed from Ready For Testing to Closed
