Skip to content

Commit

Permalink
Issue #643 Document troubleshooting expired certificates
Browse files Browse the repository at this point in the history
  • Loading branch information
kowen-rh authored and cfergeau committed Sep 30, 2019
1 parent 6bbc3cf commit c31805a
Show file tree
Hide file tree
Showing 5 changed files with 43 additions and 4 deletions.
3 changes: 1 addition & 2 deletions README.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,10 @@ Using an older `crc` binary will result in an expired certificates error.
To resolve this error:
* link:https://github.com/code-ready/crc/releases[Download the latest CodeReady Containers release] and place the `crc` binary in your `$PATH`.
* link:https://cloud.redhat.com/openshift/install/crc/installer-provisioned[Download the latest CodeReady Containers release] and place the `crc` binary in your `$PATH`.
* Remove the cluster with certificate errors using the `crc delete` command.
* Set up the new release with the `crc setup` command.
* Start the new cluster with the `crc start` command.
====

toc::[]
Expand Down
2 changes: 1 addition & 1 deletion docs/source/common-content/attributes.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -25,4 +25,4 @@
:bin: crc

// URLs
:crc-download-url: https://mirror.openshift.com/pub/openshift-v4/clients/crc/latest/
:crc-download-url: https://cloud.redhat.com/openshift/install/crc/installer-provisioned
Original file line number Diff line number Diff line change
Expand Up @@ -9,3 +9,5 @@ For example, OpenShift issues are tracked on link:https://github.com/openshift/o
====

include::proc_basic-troubleshooting.adoc[leveloffset=+1]

include::proc_troubleshooting-expired-certificates.adoc[leveloffset=+1]
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,10 @@ The majority of issues can be resolved by stopping a running {prod} virtual mach
For more information, see <<setting-up-codeready-containers_{context}>>.
* The virtual machine has been started using the [command]`{bin} start` command.
For more information, see <<starting-the-virtual-machine_{context}>>.
* You are using the latest {prod} release
* You are using the latest {prod} release.
The generated certificates for the embedded system image bundle expire after 30 days.
Using an older system image bundle may result in errors related to expired x509 certificates.
For more information, see <<troubleshooting-expired-certificates_{context}>>.

.Procedure

Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
[id="troubleshooting-expired-certificates_{context}"]
= Troubleshooting expired certificates

Each released `{bin}` binary includes an embedded system bundle that expires 30 days after the release due to certificates embedded in the OpenShift cluster.
Using an older `{bin}` binary or system bundle will result in an expired certificates error.

.Procedure

To resolve expired certificate errors:

. link:{crc-download-url}[Download the latest {prod} release] and place the `{bin}` binary in your `$PATH`.

. Remove the cluster with certificate errors using the [command]`{bin} delete` command:
+
[subs="+quotes,attributes"]
----
$ {bin} delete
----
+
[NOTE]
====
The [command]`{bin} delete` command will result in the loss of data stored in the {prod} virtual machine.
====

. Set up the new release:
+
[subs="+quotes,attributes"]
----
$ {bin} setup
----

. Start the new cluster:
+
[subs="+quotes,attributes"]
----
$ {bin} start
----

0 comments on commit c31805a

Please sign in to comment.