Project

General

Profile

Actions

Bug #13886

closed

New inventory not accepted when deleted inventory with "undefined" key status deleted

Added by François ARMAND over 5 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Very Small
Priority:
58
Name check:
Fix check:
Regression:

Description

In #13843, we ensured that a deleted inventory change the key status to "undefined".

But for some reason, using the UndefinedKey.value does not allow new inventory with a different key. In fact, the value must be none of:
- no value for keyStatus,
- UndefinedKey.value
- CertifiedKey.value

Using "bzouing" works fine, for example.

It is most certainly not what we want.


Related issues 2 (0 open2 closed)

Related to Rudder - Bug #13843: Inventory keeps its key certified when node is deleted even is keystatus is erasedReleasedFrançois ARMANDActions
Related to Rudder - Bug #16074: When deleting completely a rudder-agent, it is very hard to re-install a functionnal agent on itResolvedFrançois ARMANDActions
Actions #1

Updated by François ARMAND over 5 years ago

  • Related to Bug #13842: Use openssl 1.0.2 on old agents added
Actions #2

Updated by François ARMAND over 5 years ago

  • Related to deleted (Bug #13842: Use openssl 1.0.2 on old agents)
Actions #3

Updated by François ARMAND over 5 years ago

  • Related to Bug #13843: Inventory keeps its key certified when node is deleted even is keystatus is erased added
Actions #4

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.17 to 4.1.18
Actions #5

Updated by Benoît PECCATTE over 5 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Infrequent - complex configurations | third party integrations
  • Priority changed from 0 to 41
Actions #6

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 4.1.18 to 4.1.19
  • Priority changed from 41 to 40
Actions #7

Updated by Alexis Mousset about 5 years ago

  • Target version changed from 4.1.19 to 4.1.20
Actions #8

Updated by François ARMAND about 5 years ago

  • Target version changed from 4.1.20 to 4.1.21
  • Priority changed from 40 to 39
Actions #9

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 4.1.21 to 4.1.22
Actions #10

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 4.1.22 to 4.1.23
  • Priority changed from 39 to 38
Actions #11

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 4.1.23 to 4.1.24
Actions #12

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 4.1.24 to 588
  • Priority changed from 38 to 37
Actions #13

Updated by Nicolas CHARLES over 4 years ago

  • Target version changed from 588 to 5.0.13

this is certainly the case in 5.0

Actions #14

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.13 to 5.0.14
  • Priority changed from 37 to 36
Actions #15

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.14 to 5.0.15
  • Priority changed from 36 to 35
Actions #16

Updated by François ARMAND over 4 years ago

  • Effort required set to Very Small
  • Priority changed from 35 to 58

Some more modification were done in that one. Check if it's still a bug.

Actions #17

Updated by François ARMAND over 4 years ago

  • Related to Bug #16074: When deleting completely a rudder-agent, it is very hard to re-install a functionnal agent on it added
Actions #18

Updated by François ARMAND over 4 years ago

  • Status changed from New to Resolved

Solved in 5.0.14

Actions

Also available in: Atom PDF