Hello,
It looks like the certificates have expired for 4.2.10 and it is now unable to start.
It gets to INFO Cluster TLS certificates have expired, renewing them... but seems to hang for a long time.
When will the next release be available?
cc @praveenkumar
Can you provide debug logs? Do you remember when was the last time the cluster successfully started?
Renewing of the certs takes minutes... how long have you waited? (Has this been reproduced more than once?)
@BenHall I tried today 1.3.0 release from scratch and INFO Cluster TLS certificates have expired, renewing them... step does take like 4-5 mins which also mentioned in the doc https://code-ready.github.io/crc/#troubleshooting-expired-certificates_gsg if you faced issue after that much time it still hanged or failed then please provide debug logs.
When will the next release be available?
We are trying to make it available it by coming Wednesday.
Thanks. It was taking longer than expected, but when I switched to debug it was restarting the pods as expected.
Sorry for the trouble.
I still believe we need to improve this experience by just indicating it is still ongoing; progressdots, @code-ready/crc-devel WDYT?
The log message is logging.Infof("Cluster TLS certificates have expired, renewing them..."). Are you suggesting animated progress dots?
@cfergeau even not with animated progress dot can we just put [ takes 4-5 mins ] so the user know that he has to wait that long?
@praveenkumar That would have helped and in line with starting of openshift when it takes 3 minutes.
The delay is not deterministic, what about logging.Infof("This will take up to 5 minutes") on a separate line?
@cfergeau Sure that would also work or logging.Infof("Cluster TLS certificates have expired, renewing them... [will take up to 5 mins]") without adding a separate line?
Doesn't this make the line a bit too long?
@cfergeau I don't have any strong opinion the way we put the content as long as we communicate to user, if you think adding a new line make it clear then sure :)
Initially I thought this software is broken. After googling "readhat crc TLS expired renewing hangs" and reaching this issue to read all the comments, I decided to give another shot. It did work, but I think I waited more than 5 minutes.