Project

General

Profile

Actions

Bug #13886

closed

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

Bug #13886: New inventory not accepted when deleted inventory with "undefined" key status deleted

Added by François ARMAND over 7 years ago. Updated over 6 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

Updated by François ARMAND over 7 years ago Actions #1

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

Updated by François ARMAND over 7 years ago Actions #2

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

Updated by François ARMAND over 7 years ago Actions #3

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

Updated by Vincent MEMBRÉ over 7 years ago Actions #4

  • Target version changed from 4.1.17 to 4.1.18

Updated by Benoît PECCATTE over 7 years ago Actions #5

  • 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

Updated by Vincent MEMBRÉ over 7 years ago Actions #6

  • Target version changed from 4.1.18 to 4.1.19
  • Priority changed from 41 to 40

Updated by Alexis Mousset about 7 years ago Actions #7

  • Target version changed from 4.1.19 to 4.1.20

Updated by François ARMAND about 7 years ago Actions #8

  • Target version changed from 4.1.20 to 4.1.21
  • Priority changed from 40 to 39

Updated by Vincent MEMBRÉ about 7 years ago Actions #9

  • Target version changed from 4.1.21 to 4.1.22

Updated by Vincent MEMBRÉ almost 7 years ago Actions #10

  • Target version changed from 4.1.22 to 4.1.23
  • Priority changed from 39 to 38

Updated by Vincent MEMBRÉ almost 7 years ago Actions #11

  • Target version changed from 4.1.23 to 4.1.24

Updated by Vincent MEMBRÉ almost 7 years ago Actions #12

  • Target version changed from 4.1.24 to 588
  • Priority changed from 38 to 37

Updated by Nicolas CHARLES almost 7 years ago Actions #13

  • Target version changed from 588 to 5.0.13

this is certainly the case in 5.0

Updated by Vincent MEMBRÉ over 6 years ago Actions #14

  • Target version changed from 5.0.13 to 5.0.14
  • Priority changed from 37 to 36

Updated by Vincent MEMBRÉ over 6 years ago Actions #15

  • Target version changed from 5.0.14 to 5.0.15
  • Priority changed from 36 to 35

Updated by François ARMAND over 6 years ago Actions #16

  • 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.

Updated by François ARMAND over 6 years ago Actions #17

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

Updated by François ARMAND over 6 years ago Actions #18

  • Status changed from New to Resolved

Solved in 5.0.14

Actions

Also available in: PDF Atom