Project

General

Profile

Actions
Copy link

Bug #15863

closed

Very often, a policy generation starts at rudder start, because of the flag file /opt/rudder/etc/policy-update-running

Added by Nicolas CHARLES over 4 years ago. Updated 6 months ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
old 6.1 issues to relocate
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

i'm pretty sure that on most of my tests, there were no generation during restart of rudder

Actions
Copy link
 #1

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions
Copy link
 #2

Updated by Alexis Mousset about 4 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions
Copy link
 #4

Updated by François ARMAND almost 4 years ago

It's the goal of the flag, what is the problem? In logs, I see the log correctly removed. Do you have more information about the pb? Else, perhaps we could close the ticket as "it was solved at some point" ?

Actions
Copy link
 #5

Updated by François ARMAND almost 4 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 28
Actions
Copy link
 #6

Updated by Nicolas CHARLES almost 4 years ago

issue is that the flag is there for no reason - i stopped the webapp withtout a policy generation started, and i restart it and get a policy generation

Actions
Copy link
 #7

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.19 to 5.0.20
  • Priority changed from 28 to 27
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.20 to 797
Actions
Copy link
 #10

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 797 to 6.1.14
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions
Copy link
 #19

Updated by François ARMAND 6 months ago

  • Status changed from New to Resolved
  • Priority changed from 27 to 0
  • Regression set to No

We changed how we managed that tag and I was not able to reproduce the problem.

Actions
Copy link

Also available in: Atom PDF