Bug #17314: policy generation error when disabling " Enable syntax validation of generated policies" during a policy generation - Rudder - Issue Tracker

Actions

Copy link

Bug #17314

closed

policy generation error when disabling " Enable syntax validation of generated policies" during a policy generation

Added by Nicolas CHARLES over 4 years ago. Updated over 1 year ago.

Status:

Rejected

Priority:

N/A

Assignee:

Category:

Web - Config management

Target version:

old 6.2 issues to relocate

Pull Request:

Severity:

Minor - inconvenience | misleading | easy workaround

UX impact:

User visibility:

Operational - other Techniques | Rudder settings | Plugins

Effort required:

Priority:

Name check:

To do

Fix check:

To do

Regression:

Description

I disabled "Enable syntax validation of generated policies" during a policy generation, and I got

2020-05-04T04:52:59+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:52:59+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:52:59+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:52:59+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:52:59+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:52:59+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:52:59+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:52:59+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:52:59+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:52:59+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:52:59+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:52:59+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:52:59+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:52:59+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:53:00+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:53:00+0000 WARNING Failed to execute shell command from Rudder: error=13, Permission denied2020-05-04T04:53:00+0000 WARNING Failed to ex...
[2020-05-04 04:55:10] INFO  policy.generation.timing - Policy generation failed after: 30 min 36 s
[2020-05-04 04:55:10] ERROR policy.generation - Error when updating policy, reason was: Cannot write nodes configuration <- Unexpected: Error when executing hooks:
 Exit code=-2147483648 (check that file exists and is executable) for hook: '/opt/rudder/etc/hooks.d/policy-generation-node-ready/10-cf-promise-check'. [stdout:][stderr:] (for node(s) a368452b-35b4-4943-bdf3-fcbc14bb6d43;260c74d9-7062-4adb-b2b2-046043991907;421c8022-f493-4801-87eb-c9e1bb75d38d;2e803baa-3d23-4beb-be03-6afa609ff21b;2d20386d-7646-4028-acfc-ec43e03df8f2;9cf80981-7926-4cbd-9d38-2ae2bce3cc7f;c1a6e7bf-c89c-4e96-bef3-c7a285f29e03;1edbfc51-f0b8-4097-b6be-c2999e45fafd;91308052-1e0c-4

this was during the hooks execution

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 6.1.0~beta2 to 6.1.0~beta3

Actions

Copy link

Updated by François ARMAND over 4 years ago

Status changed from New to In progress
Assignee set to François ARMAND

Actions

Copy link

Updated by François ARMAND over 4 years ago

Could it happens that you changed the rights (the checkbox) during policy generation around the time we list what hooks are available? (it seems to be once policies are written, before we start checking and moving files around).

Actions

Copy link

Updated by François ARMAND over 4 years ago

Status changed from In progress to Discussion
Assignee deleted (~~François ARMAND~~)
Target version changed from 6.1.0~beta3 to 5.0.18
Severity set to Minor - inconvenience | misleading | easy workaround
User visibility set to Operational - other Techniques | Rudder settings | Plugins
Priority changed from 0 to 32

To make my previous comment clearer: I think the behavior is ok and I'm not sure we could prevent it anyway. To avoid thounsand of directory listing, we only check for available hooks once for each kind, just before they are first needed. But if the execution bit change before that listing and when it's used, then we get an error, and the error is correct.
On the setting side, it has zero idea that a generation is processing and just between the moment hooks were read and it is used.

In all case, it's not specific to 6.1.

Actions

Copy link