Project

General

Profile

Actions

Bug #14386

closed

UI "settings" for management of hooks works inconsistently

Added by François ARMAND about 5 years ago. Updated almost 5 years ago.

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

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 1 (0 open1 closed)

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

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #14331: Trigger agent update and run after policy server has finished policy generationReleasedAlexis MoussetActions
Actions #1

Updated by François ARMAND about 5 years ago

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

Updated by François ARMAND about 5 years ago

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

Updated by François ARMAND about 5 years ago

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

Updated by François ARMAND about 5 years ago

  • Description updated (diff)
Actions #5

Updated by François ARMAND about 5 years ago

  • Target version changed from 5.0.8 to 5.0.9
Actions #6

Updated by François ARMAND about 5 years 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
Actions #7

Updated by François ARMAND about 5 years ago

  • Assignee set to François ARMAND
Actions #8

Updated by Nicolas CHARLES about 5 years ago

  • Description updated (diff)
Actions #10

Updated by François ARMAND about 5 years ago

  • Status changed from New to In progress
Actions #11

Updated by François ARMAND about 5 years 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
Actions #12

Updated by Rudder Quality Assistant about 5 years ago

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

Updated by François ARMAND about 5 years ago

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

Updated by Rudder Quality Assistant about 5 years ago

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

Updated by François ARMAND about 5 years ago

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

Updated by Rudder Quality Assistant about 5 years ago

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

Updated by François ARMAND about 5 years ago

  • Status changed from Discussion to Pending release
Actions #18

Updated by François ARMAND about 5 years ago

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

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending release to Released

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

Actions

Also available in: Atom PDF