Project

General

Profile

Bug #3030

Facter isn't loaded, but is referenced in DB migrations etc.

Added by Dominic Cleal over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Urgent
Category:
Packaging
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

The Facter library is no longer 'required' anywhere now that Puppet is no longer loaded due to #2414, but we still have quite a few references to it.

This causes DB migrations on a clean installation to fail:

uninitialized constant AddOwnerToHosts::Facter/var/lib/workspace/workspace/test_develop/database/mysql/ruby/1.8.7/db/migrate/20100419151910_add_owner_to_hosts.rb:12:in `up'

Other uses of it:

app/models/setting/auth.rb
app/models/setting/provisioning.rb
app/models/setting/general.rb
lib/tasks/reset_permissions.rake
db/migrate/20100628123400_add_internal_auth.rb
db/migrate/20100419151910_add_owner_to_hosts.rb

All of these should probably just require 'facter' until we can get rid of it too.


Related issues

Related to Foreman - Feature #2414: Remove Puppet from Foreman coreClosed2013-04-19

Associated revisions

Revision 8d4bcf4a (diff)
Added by Greg Sutcliffe over 9 years ago

Fixes #3030 - require facter where necessary

History

#1 Updated by Dominic Cleal over 9 years ago

  • Related to Feature #2414: Remove Puppet from Foreman core added

#2 Updated by Dominic Cleal over 9 years ago

  • Status changed from New to Ready For Testing

#3 Updated by Greg Sutcliffe over 9 years ago

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

Also available in: Atom PDF