Project

General

Profile

Bug #636

Foreman doews not recognise a change in the environment when this is changed in a fact

Added by Paul Kelly over 8 years ago. Updated almost 8 years ago.

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

Description

Foreman sets the environment for a host just once. If is changes after that, then it is ignored.


Related issues

Related to Foreman - Feature #416: Report on inconsistant factsNew2010-10-25
Has duplicate Foreman - Bug #1016: Environement may be altered via another source but this is not reflected in Foreman configRejected2011-06-30

Associated revisions

Revision b187e885 (diff)
Added by Ohad Levy almost 8 years ago

wrong setting category - refs #636

Revision d3fbfd7e (diff)
Added by Paul Kelly almost 8 years ago

Fixes #636 - Update environment from facts

Signed-off-by: Paul Kelly <>

History

#1 Updated by Paul Kelly over 8 years ago

  • Status changed from New to Ready For Testing

#2 Updated by Paul Kelly over 8 years ago

Rebased and mailed

#3 Updated by Jacob McCann about 8 years ago

Is this fix simple enough for me to try and apply and test? I've ran into this issue and wouldn't mind testing a fix to address it until its released officially.

#4 Updated by Ohad Levy almost 8 years ago

  • Status changed from Ready For Testing to Need more information

#5 Updated by Paul Kelly almost 8 years ago

  • Status changed from Need more information to Ready For Testing

I have added a Setting to control the behavior so now the administrator can decide whether they want the environment fact to replace the foreman value

#6 Updated by Paul Kelly almost 8 years ago

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

#7 Updated by Ohad Levy almost 8 years ago

  • Target version set to 0.4

Also available in: Atom PDF