Skip to content

Latest commit

 

History

History
34 lines (26 loc) · 1.15 KB

proc_troubleshooting-expired-certificates.adoc

File metadata and controls

34 lines (26 loc) · 1.15 KB
Raw

Troubleshooting expired certificates

Before {rh-prod} 1.2.0, the system bundle in each released {bin} binary expired 30 days after the release. This expiration was due to certificates embedded in the OpenShift cluster. As a result, using an older {bin} binary or system bundle results in an expired certificates error.

Starting from {prod} 1.2.0, the embedded certificates can be automatically renewed by {bin}. The {bin} start command triggers the certificate renewal process when needed. Certificate renewal can add up to five minutes to the start time of the cluster.

Procedure

With {prod} releases older than 1.2.0, to resolve expired certificate errors:

  1. Download the latest {prod} release and place the {bin} binary in your $PATH.

  2. Remove the cluster with certificate errors using the {bin} delete command:

  3. Set up the new release:

    $ {bin} setup

  4. Start the new virtual machine:

    $ {bin} start