Project

General

Profile

Actions

Bug #21429

closed

rollback button in even log can be clicked several time in a row and error are stacked in other screens

Bug #21429: rollback button in even log can be clicked several time in a row and error are stacked in other screens

Added by François ARMAND over 3 years ago. Updated over 3 years ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
I dislike using that feature
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Priority:
71
Name check:
To do
Fix check:
To do
Regression:

Description

This leads to a big moment of WTH because it does not look like anything is happening, and errors are not diplayed in that screen, but as soon as you navigate to an other screen, you have tens of error "rollback can not start because one is already running".

When the rollback button is clicked, we should AT MINIMA have a notification "rollback started" and a js action that disables all rollback button of the page.
It won't prevent a milicious user to trigger several rollback by reloading the page (this is handled by #18500), but it will help a normal user to understand what is happening.


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #18500: clicking twice on rollbacking event in 6.1 breaks rudderResolvedActions

Updated by François ARMAND over 3 years ago Actions #1

  • Related to Bug #18500: clicking twice on rollbacking event in 6.1 breaks rudder added

Updated by Alexis Mousset over 3 years ago Actions #2

  • Target version changed from 6.2.16 to 6.2.17

Updated by Vincent MEMBRÉ over 3 years ago Actions #3

  • Target version changed from 6.2.17 to 997
  • Priority changed from 48 to 72

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

  • Target version changed from 997 to 6.2.18

Updated by Vincent MEMBRÉ over 3 years ago Actions #5

  • Target version changed from 6.2.18 to 6.2.19

Updated by Elaad FURREEDAN over 3 years ago Actions #6

  • Status changed from New to In progress
  • Assignee set to Elaad FURREEDAN
  • Priority changed from 72 to 71

Updated by Elaad FURREEDAN over 3 years ago Actions #7

  • Status changed from In progress to Pending technical review
  • Assignee changed from Elaad FURREEDAN to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/4463

Updated by Anonymous over 3 years ago Actions #8

  • Status changed from Pending technical review to Pending release

Updated by Vincent MEMBRÉ over 3 years ago Actions #9

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.2.19, 7.0.8 and 7.1.6 which were released today.

Actions

Also available in: PDF Atom