Project

General

Profile

Actions

Bug #9415

closed

User story #1808: Add an Audit mode to Rudder: only check properties, no modification on nodes

Nodes have several open nodeconfigurations

Added by François ARMAND about 8 years ago. Updated about 8 years ago.

Status:
Released
Priority:
1 (highest)
Category:
Web - Compliance & node report
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

On my test machine, I get to the situation where nodes have several opened expected node configurations:

rudder=> select nodeid, nodeconfigid, begindate, enddate from nodeconfigurations where nodeid = '00000010-55a2-4b97-8529-5154cbb63a18' and enddate is null;
                nodeid                | nodeconfigid |         begindate          | enddate
--------------------------------------+--------------+----------------------------+---------
 00000010-55a2-4b97-8529-5154cbb63a18 | 4f920c3b     | 2016-10-18 03:16:35.582+02 |
 00000010-55a2-4b97-8529-5154cbb63a18 | 4f920c3b     | 2016-10-18 03:16:41.431+02 |
 00000010-55a2-4b97-8529-5154cbb63a18 | 4f920c3b     | 2016-10-18 03:20:07.635+02 |
 00000010-55a2-4b97-8529-5154cbb63a18 | 4f920c3b     | 2016-10-18 03:27:41.337+02 |
 00000010-55a2-4b97-8529-5154cbb63a18 | 4f920c3b     | 2016-10-18 03:04:54.63+02  |
 00000010-55a2-4b97-8529-5154cbb63a18 | 4f920c3b     | 2016-10-18 03:05:32.522+02 |

It does not seem to lead to user viewable error, but it means that something is broken in the logic which update node configurations.


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #9444: When accepting 100 nodes, I randomly get multiple policy generationRejectedActions
Actions #1

Updated by François ARMAND about 8 years ago

  • Translation missing: en.field_tag_list set to Blocking 4.0
Actions #2

Updated by François ARMAND about 8 years ago

  • Related to Architecture #9315: Update DB schema of expected reports to store policy mode added
Actions #3

Updated by François ARMAND about 8 years ago

  • Related to Bug #9444: When accepting 100 nodes, I randomly get multiple policy generation added
Actions #4

Updated by François ARMAND about 8 years ago

  • Status changed from New to In progress
Actions #5

Updated by François ARMAND about 8 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/1307
Actions #6

Updated by François ARMAND about 8 years ago

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

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 318 to 4.0.0~rc2
Actions #8

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 4.0.0~rc2 to 4.0.0~rc1
Actions #9

Updated by Vincent MEMBRÉ about 8 years ago

  • Related to deleted (Architecture #9315: Update DB schema of expected reports to store policy mode)
Actions #10

Updated by Vincent MEMBRÉ about 8 years ago

  • Parent task set to #1808
Actions #11

Updated by Alexis Mousset about 8 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.0.0 which was released the 10th November 2016.

Actions

Also available in: Atom PDF