Project

General

Profile

Actions

Bug #7301

closed

promises are not regenerated when a node is transformed into a relay

Added by Vincent MEMBRÉ over 6 years ago. Updated over 6 years ago.

Status:
Released
Priority:
2
Category:
Server components
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:

Description

After calling rudder-node-to-relay promises are note generated straight away, we should trigger a policy reload from api at the end of the script

Actions #1

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from New to In progress
Actions #2

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to Matt Ungaro
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/766
Actions #3

Updated by Vincent MEMBRÉ over 6 years ago

  • Assignee changed from Matt Ungaro to Benoît PECCATTE
Actions #4

Updated by Janos Mattyasovszky over 6 years ago

Why not use http://localhost:8080/ directly?
You could make sure you hit the rudder API...
I am just asking because we for example modified rudder's vhost config to listen on https only on a dedicated Service IP instead of *:443, as there are also other services running on https on that host...

Actions #5

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 2.10.19 to 2.10.20
Actions #6

Updated by Benoît PECCATTE over 6 years ago

  • Status changed from Pending technical review to Discussion
  • Assignee changed from Benoît PECCATTE to Vincent MEMBRÉ
Actions #7

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from Discussion to Pending release
  • % Done changed from 0 to 100
Actions #9

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.20, 2.11.17, 3.0.12 and 3.1.5 which were released today.

Actions

Also available in: Atom PDF