Actions
Bug #21367
closedNode certificate expiration date does not follow the same format than the others dates in the UI
Pull Request:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
I was bothered the first time
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Very Small
Priority:
47
Name check:
To do
Fix check:
To do
Regression:
No
Description
In the summary webpage of a node, the expiration date of the certificate does not follow the same date format than the other dates displayed:
Inventory created (node local time): 2022-07-06 08:16:15+0000
Expiration date: 2032-07-03T08:15:03Z
Updated by Félix DALLIDET over 2 years ago
- Effort required set to Very Small
- Priority changed from 9 to 23
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.2.0~beta1 to 7.2.0~rc1
- Priority changed from 23 to 47
Updated by Alexis Mousset over 2 years ago
- Target version changed from 7.2.0~rc1 to 7.1.5
- Priority changed from 47 to 48
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.1.5 to 7.1.6
- Priority changed from 48 to 47
Updated by Elaad FURREEDAN over 2 years ago
- Target version changed from 7.1.6 to 7.0.8
- Regression set to No
Updated by Elaad FURREEDAN over 2 years ago
- Status changed from New to In progress
- Assignee set to Elaad FURREEDAN
Updated by Elaad FURREEDAN over 2 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Elaad FURREEDAN to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/4461
Updated by Anonymous over 2 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|03dd1cb5da48693c3d3ec6e8a1c3a12034ff5429.
Updated by Vincent MEMBRÉ over 2 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.0.8 and 7.1.6 which were released today.
Actions