Actions
Bug #25563
open
We can't disable a node with a bad certificate anymore
Bug #25563:
We can't disable a node with a bad certificate anymore
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
We added a check to not be able to save a node with a bad certificate, but the side effect is that if we already had a node with a bad certificate, we can't disable it anymore:
The error is:
Error when saving the new node state <- CryptoEx: Key '-----BEGIN CERTIFICATE----- MIIFqDCCA5CgAwIBAgIUIb+ay gIrV31P4GyU-XXXX -----END CERTIFICATE-----' cannot be parsed as a valid certificate; root exception was: unable to decode base64 string: invalid characters encountered in base64 data
We should not run the savePreChecks when disabling a node.
Files
Updated by François ARMAND about 1 year ago
- Related to Bug #24815: Node with inventories with bad certificate still get into Rudder added
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 8.1.8 to 8.1.9
Updated by Vincent MEMBRÉ 12 months ago
- Target version changed from 8.1.9 to 8.1.10
Updated by Vincent MEMBRÉ 12 months ago
- Target version changed from 8.1.10 to 8.1.11
Updated by Vincent MEMBRÉ 10 months ago
- Target version changed from 8.1.11 to 8.1.12
Updated by Vincent MEMBRÉ 9 months ago
- Target version changed from 8.1.12 to 8.1.13
Updated by Vincent MEMBRÉ 7 months ago
- Target version changed from 8.1.13 to 8.2.6
Updated by Vincent MEMBRÉ 6 months ago
- Target version changed from 8.2.6 to 8.2.7
Updated by Vincent MEMBRÉ 6 months ago
- Target version changed from 8.2.7 to 8.2.8
Updated by Félix DALLIDET 4 months ago
- Target version changed from 8.2.8 to 8.2.9
Updated by Vincent MEMBRÉ 2 months ago
- Target version changed from 8.2.9 to 1133
Updated by Alexis Mousset 24 days ago
- Target version changed from 1133 to 8.3.6
Updated by Vincent MEMBRÉ 5 days ago
- Target version changed from 8.3.6 to 8.3.7
Actions