node certificate nearly expired, created a new certificate, but ...

[p-user]

My node certificate was going to expire soon, so I issued the command:

pvecm updatecerts -f

and rebooted the node (it is just for test, so that's ok).

When I now look at the certificate in the virtual enviroment I noticed that, although today is March 5th 2024, the validity of this new certificate is same time I created it, but valid since yesterday (i.e. March 4th 2024).

I cannot imagine that this is intentional, but maybe it is. It looks odd though.

Kind regards,
Albert

 

[fabian]

it is, because the certificate is initially created on first boot and there were a lot of users running into an issue with time sync jumping the clock backwards a bit after the certificate was created. backdating it by a day avoids 99% of those cases (the other ones where the clock is so wrong that a day is not enough need to be manually handled).

 

[p-user]

Thanks for the clear explanation!
Makes perfect sense.

Kind regards,
Albert