Project

General

Profile

Actions

Bug #7038

closed

When promises could have been updated, we still have the error messages saying we couldn't update promises

Bug #7038: When promises could have been updated, we still have the error messages saying we couldn't update promises

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

Status:
Released
Priority:
N/A
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

We persist the error messages for update for 4 minutes, to let user a chance to see error messages
however, the message stay even if there is success, which is confusing, and mess reports

Updated by Nicolas CHARLES over 10 years ago Actions #1

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/727

Updated by Nicolas CHARLES over 10 years ago Actions #2

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

Updated by François ARMAND over 10 years ago Actions #4

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.13, 3.0.8 and 3.1.1 which were released today.

Actions

Also available in: PDF Atom