Project

General

Profile

Actions

Bug #17165

closed

Not updated root certificate after fresh install

Added by Félix DALLIDET over 4 years ago. Updated about 1 year ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Web - Nodes & inventories
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

I tried to install a Server in 6.1, install went smoothly but, my rudder server was not reporting anything.
In fact, it appeared that my Server agent certificate registered in allnodescert.pem was addressed to a specific UID, which was not root. Even if at the end of the install, my Server
and my certificate were correctly set with the UID "root".

Sending an inventory did not change anything. The API showed that the node certificate was correctly addressed.
I had to manually trigger a "regenerate all" to fix this up. Looks like the certificate change was not triggered by the webapp


Files

rudder.tar.bz2 (21 KB) rudder.tar.bz2 Félix DALLIDET, 2020-06-04 10:31
Actions #1

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.0~beta1 to 6.1.0~beta2
Actions #2

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.0~beta2 to 6.1.0~beta3
Actions #3

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.0~beta3 to 6.1.0~rc1
Actions #4

Updated by François ARMAND over 4 years ago

  • Assignee set to François ARMAND
Actions #5

Updated by François ARMAND over 4 years ago

  • Status changed from New to In progress
Actions #6

Updated by François ARMAND over 4 years ago

  • Status changed from In progress to New
  • Assignee deleted (François ARMAND)

I have little success reproducing or understanding. My best guess is:

- root inventory is uploaded,
- there is some time before we notice that an inventory changed, and we hit it fully,
- webapp is stopped before generation is started.

I'm not sure what we can do against that but advice to do a full generation.

Actions #7

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.0~rc1 to 6.1.0~rc2
Actions #8

Updated by Nicolas CHARLES over 4 years ago

the flag file stating that policy generation is requiered could prevent this issue

Actions #9

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.0~rc2 to 6.1.0~rc3
Actions #10

Updated by Félix DALLIDET over 4 years ago

I just got this issue on a fresh install on 6.1-nightly on sles12.
Same symptoms, most likely the rudder-init which is in fault here since he writes in ldap without many checks.

I attached all my rudder log in a tar archive.

Actions #11

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.0~rc3 to 6.1.0~rc4
Actions #13

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.0~rc4 to 6.1.0
Actions #14

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.0 to 6.1.1
Actions #17

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.1 to 6.1.2
Actions #18

Updated by François ARMAND over 4 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
  • Priority changed from 0 to 49
Actions #19

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.2 to 6.1.3
Actions #20

Updated by François ARMAND over 4 years ago

  • Target version changed from 6.1.3 to 6.1.4
  • Priority changed from 49 to 48
Actions #21

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.1.4 to 6.1.5
Actions #22

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.1.5 to 6.1.6
  • Priority changed from 48 to 47
Actions #23

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.1.6 to 6.1.7
  • Priority changed from 47 to 46
Actions #24

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.1.7 to 6.1.8
  • Priority changed from 46 to 45
Actions #25

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.1.8 to 6.1.9
  • Priority changed from 45 to 44
Actions #26

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.1.9 to 6.1.10
Actions #27

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.10 to 6.1.11
  • Priority changed from 44 to 43
Actions #28

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.11 to 6.1.12
Actions #29

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.12 to 6.1.13
  • Priority changed from 43 to 42
Actions #30

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.13 to 6.1.14
Actions #31

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #32

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #33

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #34

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #35

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #36

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions #37

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions #38

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions #39

Updated by François ARMAND about 1 year ago

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

We changed a ton of things related to that along the version. We still have issues for cases where webapp is killed before root inventory is send/parsed/etc, but not the specific one here I believe.

Actions

Also available in: Atom PDF