Bug #4492: When accepting several nodes, one policy generation is triggered for each of them - Rudder - Issue Tracker

Actions

Copy link

Bug #4492

closed

When accepting several nodes, one policy generation is triggered for each of them

Added by Vincent MEMBRÉ almost 11 years ago. Updated almost 11 years ago.

Status:

Released

Priority:

Assignee:

Nicolas CHARLES

Category:

Web - Nodes & inventories

Target version:

2.6.12

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

WHen you accept more than one node, a deployment is launched for every node.

This is totally useless, and only one deployment should be launched once every node is accepted.

If a deployment succeed while nodes are accepted it will be not be complete (miss some nodes) and replaced right after.

Moreover, a deployment is started when nodes are refused, what make no sens, because no modification on the configuration of the infrastructure can happen on that case.

Actions

Copy link

Updated by Vincent MEMBRÉ almost 11 years ago

Target version changed from 2.6.11 to 2.6.12

Actions

Copy link

Updated by François ARMAND almost 11 years ago

I believe it is more than a bug for 2.6, so if it's more than 2 lines, it should bo to 2.10.

Actions

Copy link

Updated by François ARMAND almost 11 years ago

In fact, the correction is trivial and also correct the fact that policies are regenerated when refusing nodes, so correcting it to 2.6.

Actions

Copy link

Updated by François ARMAND almost 11 years ago

Status changed from New to In progress
Assignee changed from Vincent MEMBRÉ to François ARMAND

Actions

Copy link

Updated by François ARMAND almost 11 years ago

Subject changed from When accepting several nodes, there is as many deployment launched to When accepting several nodes, one policy generation is triggered for each of them

Actions

Copy link