Project

General

Profile

Actions

Bug #6040

closed

If i update or create a rule, all nodes that are in the target of this rule get the "pending" state

Bug #6040: If i update or create a rule, all nodes that are in the target of this rule get the "pending" state

Added by Nicolas CHARLES over 11 years ago. Updated over 11 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When I update/create a rule, or change a directive, all nodes that are targeted get the global status "Pending", in compliance mode, as we rely on the NodeConfigId that has been updated for this change

this is really super unfriendly :(


Subtasks 1 (0 open1 closed)

Bug #6046: broken tests after changing the logic of reportsReleasedFrançois ARMANDActions

Related issues 2 (0 open2 closed)

Related to Rudder - Bug #6021: Pending state is not managed as user could expect in changes only modeReleasedNicolas CHARLESActions
Has duplicate Rudder - Bug #5727: Nodes stays in unexpected/missing statusRejectedFrançois ARMANDActions

Updated by Nicolas CHARLES over 11 years ago Actions #1

  • Status changed from New to Pending technical review
  • Assignee set to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/743

Updated by Nicolas CHARLES over 11 years ago Actions #2

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Updated by Vincent MEMBRÉ over 11 years ago Actions #4

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.0~rc1, which was released today.

Actions

Also available in: PDF Atom