Project

General

Custom queries

Profile

Actions
Copy link

Bug #17460

closed

When keyhash is empty, `key-hash` should not be in nodeslist.json node's entry

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

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
7.0.0~beta1
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
18
Name check:
To do
Fix check:
To do
Regression:

Description

We have case where node are broken (or edge case, when key is deleted, etc) and keyhash is empty.
In that case, we generate:

...
"nodeXX": {
  "hostname": "nodeXX.local",
  "key-hash": "sha256:",
  "policy-server": "root" 
}

We should just not write key-hash at all in that case.

#1

Updated by François ARMAND almost 5 years ago

  • Status changed from New to In progress
#2

Updated by François ARMAND almost 5 years ago

  • Status changed from In progress to New
  • Assignee deleted (François ARMAND)
  • Target version changed from 5.0.18 to 6.2.0~beta1
#3

Updated by François ARMAND almost 5 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Infrequent - complex configurations | third party integrations
  • Priority changed from 0 to 11
#4

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.2.0~beta1 to 6.2.0~rc1
  • Priority changed from 11 to 20
#5

Updated by François ARMAND over 4 years ago

  • Target version changed from 6.2.0~rc1 to 7.0.0~beta1
  • Priority changed from 20 to 10
#6

Updated by Alexis Mousset over 3 years ago

  • Status changed from New to Rejected
  • Priority changed from 10 to 18
Actions
Copy link

Also available in: Atom PDF