Project

General

Profile

Actions

Bug #2781

closed

No promises are generated for a node which were pending in 2.3.9 nightly and accepted in 2.4.0~beta3

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

Status:
Rejected
Priority:
1
Category:
-
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I had a node pending in rudder 2.3.9 nightly and after an update to 2.4.0~beta3, the node is still capable to send its inventories. Nevertheless, after I have accepted this node, whatever directive I try to apply to it, no promise for it is generated.


Files

rudder_migrated_error.log (31.6 KB) rudder_migrated_error.log Nicolas PERRON, 2012-08-07 17:55
Actions #1

Updated by Nicolas PERRON over 11 years ago

I've restarted jetty with debug mode and after a clear cache of Rudder webapp the content of the /var/log/rudder/webapp/xxxx.log file is the file I uploaded

I think this is because of the techniques which have not been updated.

Actions #2

Updated by Nicolas PERRON over 11 years ago

Nicolas PERRON wrote:

I've restarted jetty with debug mode and after a clear cache of Rudder webapp the content of the /var/log/rudder/webapp/xxxx.log file is the file I uploaded

I think this is because of the techniques which have not been updated.

Even if the techniques are updated, the error is still here.
The problem is the same for a new node I've added to this server and even if I delete the other one and the rules associated.

Actions #3

Updated by Nicolas PERRON over 11 years ago

  • Status changed from New to Rejected

No one was able to reproduce it. Then, I rejected this issue.

Actions

Also available in: Atom PDF