Project

General

Profile

Actions

Bug #5699

closed

The "location_fact" setting does not actually look for a custom fact

Added by Simon Mügge almost 10 years ago. Updated almost 10 years ago.

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

Description

The new "location_fact" setting to automatically update a hosts location to the therein configured fact does not get evaluated.

It always and only looks for a fact named "location_fact", not for "foreman_location", which is the in-page default in the admin settings page, nor any other configured custom fact.

The issue seems to be this, as was pointed out in IRC today by either "Dominic" or "acidrainfall":
http://projects.theforeman.org/projects/foreman/repository/revisions/e88536b278c403ae2e0e34f0e0e2de457bf95383/entry/app/models/host/base.rb#L112


Related issues 1 (0 open1 closed)

Is duplicate of Foreman - Bug #5690: Taxonomy fact name not retrieved from settingsClosedStephen Benjamin05/13/2014Actions
Actions #2

Updated by Dominic Cleal almost 10 years ago

  • Is duplicate of Bug #5690: Taxonomy fact name not retrieved from settings added
Actions #3

Updated by Dominic Cleal almost 10 years ago

  • Status changed from New to Duplicate

Thanks for the report. stbenjam (Stephen) has reported it and filed a bug over at #5690, we'll try and have it in 1.5.1.

Actions

Also available in: Atom PDF