Project

General

Profile

Bug #14386

UI "settings" for management of hooks works inconsistently

Added by François ARMAND 5 months ago. Updated 3 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
80

Description

Since https://issues.rudder.io/issues/14331, we can manage /opt/rudder/etc/hooks.d/policy-generation-node-ready/10-cf-promise-check directly in the "Setting > General" UI. But if you disable it, reload the page, the hook seems to be enable again.

In fact, the permissions on /opt/rudder/etc/hooks.d/policy-generation-node-ready/10-cf-promise-check are now "rw-r-xr-x". So the UI only changed the owner exec right, not group/other. We should change all exec rights of the hook.


Subtasks

Bug #14550: UI "settings" for management of hooks need Unix rightReleasedNicolas CHARLESActions

Related issues

Related to Rudder - Bug #14331: Trigger agent update and run after policy server has finished policy generationReleasedActions

Associated revisions

Revision bf3705e8 (diff)
Added by François ARMAND 4 months ago

Fixes #14386: UI management of 10-cf-promise-check works inconsistently

History

#1

Updated by François ARMAND 5 months ago

  • Related to Bug #14322: Directive parameter values are mixed between directives added
#2

Updated by François ARMAND 5 months ago

  • Related to deleted (Bug #14322: Directive parameter values are mixed between directives)
#3

Updated by François ARMAND 5 months ago

  • Related to Bug #14331: Trigger agent update and run after policy server has finished policy generation added
#4

Updated by François ARMAND 5 months ago

  • Description updated (diff)
#5

Updated by François ARMAND 5 months ago

  • Target version changed from 5.0.8 to 5.0.9
#6

Updated by François ARMAND 5 months ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Effort required set to Very Small
  • Priority changed from 0 to 80
#7

Updated by François ARMAND 5 months ago

  • Assignee set to François ARMAND
#8

Updated by Nicolas CHARLES 5 months ago

  • Description updated (diff)
#10

Updated by François ARMAND 4 months ago

  • Status changed from New to In progress
#11

Updated by François ARMAND 4 months 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/2163
#12

Updated by Rudder Quality Assistant 4 months ago

  • Status changed from Pending technical review to Discussion
  • Assignee changed from Nicolas CHARLES to François ARMAND
#13

Updated by François ARMAND 4 months ago

  • Assignee changed from François ARMAND to Nicolas CHARLES
#14

Updated by Rudder Quality Assistant 4 months ago

  • Assignee changed from Nicolas CHARLES to François ARMAND
#15

Updated by François ARMAND 4 months ago

  • Assignee changed from François ARMAND to Nicolas CHARLES
#16

Updated by Rudder Quality Assistant 4 months ago

  • Assignee changed from Nicolas CHARLES to François ARMAND
#17

Updated by François ARMAND 4 months ago

  • Status changed from Discussion to Pending release
#18

Updated by François ARMAND 4 months ago

  • Subject changed from UI management of 10-cf-promise-check works inconsistently to UI "settings" for management of hooks works inconsistently
#19

Updated by Vincent MEMBRÉ 3 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.9 which was released today.

Also available in: Atom PDF