Project

General

Profile

Actions

Bug #636

closed

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

Added by Paul Kelly over 13 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Facts
Target version:
Difficulty:
Triaged:
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 2 (1 open1 closed)

Related to Foreman - Feature #416: Report on inconsistant factsNew10/25/2010Actions
Has duplicate Foreman - Bug #1016: Environement may be altered via another source but this is not reflected in Foreman configRejectedPaul Kelly06/30/2011Actions
Actions #1

Updated by Paul Kelly over 13 years ago

  • Status changed from New to Ready For Testing
Actions #2

Updated by Paul Kelly over 13 years ago

Rebased and mailed

Actions #3

Updated by Jacob McCann over 13 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.

Actions #4

Updated by Ohad Levy over 13 years ago

  • Status changed from Ready For Testing to Need more information
Actions #5

Updated by Paul Kelly about 13 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

Actions #6

Updated by Paul Kelly about 13 years ago

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

Updated by Ohad Levy about 13 years ago

  • Target version set to 0.4
Actions

Also available in: Atom PDF