You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/install/iso-install.md
+5-79
Original file line number
Diff line number
Diff line change
@@ -62,8 +62,8 @@ The following [video](https://youtu.be/X0VIGZ_lExQ) shows a quick overview of an
62
62
1. Choose the installation disk you want to install the Harvester cluster on and the data disk you want to store VM data on. By default, Harvester uses [GUID Partition Table (GPT)](https://en.wikipedia.org/wiki/GUID_Partition_Table) partitioning schema for both UEFI and BIOS. If you use the BIOS boot, then you will have the option to select [Master boot record (MBR)](https://en.wikipedia.org/wiki/Master_boot_record).
- `Installation disk`: The disk to install the Harvester cluster on.
65
+
66
+
- `Installation disk`: The disk to install the Harvester cluster on.
67
67
- `Data disk`: The disk to store VM data on. Choosing a separate disk to store VM data is recommended.
68
68
- `Persistent size`: If you only have one disk or use the same disk for both OS and VM data, you need to configure persistent partition size to store system packages and container images. The default and minimum persistent partition size is 150 GiB. You can specify a size like 200Gi or 153600Mi.
69
69
@@ -94,13 +94,13 @@ The following [video](https://youtu.be/X0VIGZ_lExQ) shows a quick overview of an
### Fail to join nodes using FQDN to a cluster which has custom SSL certificate configured
191
-
192
-
You may encounter that newly joined nodes stay in the **Not Ready** state indefinitely. This is likely the outcome if you already have a set of **custom SSL certificates** configured on the to-be-joined Harvester cluster and provide an **FQDN** instead of a VIP address for the management address during the Harvester installation.
193
-
194
-
195
-
196
-
You can check the **SSL certificates** on the Harvester dashboard's setting page or using the command line tool `kubectl get settings.harvesterhci.io ssl-certificates` to see if there is any custom SSL certificate configured (by default, it is empty).
Oct 06 03:36:08 node-0 rancherd[2171]: time="2023-10-06T03:36:08Z" level=info msg="[stdout]: [INFO] Using default agent configuration directory /etc/rancher/agent"
214
-
Oct 06 03:36:08 node-0 rancherd[2171]: time="2023-10-06T03:36:08Z" level=info msg="[stdout]: [INFO] Using default agent var directory /var/lib/rancher/agent"
215
-
Oct 06 03:36:08 node-0 rancherd[2171]: time="2023-10-06T03:36:08Z" level=info msg="[stderr]: [WARN] /usr/local is read-only or a mount point; installing to /opt/rancher-system-agent"
216
-
Oct 06 03:36:08 node-0 rancherd[2171]: time="2023-10-06T03:36:08Z" level=info msg="[stdout]: [INFO] Determined CA is necessary to connect to Rancher"
217
-
Oct 06 03:36:08 node-0 rancherd[2171]: time="2023-10-06T03:36:08Z" level=info msg="[stdout]: [INFO] Successfully downloaded CA certificate"
218
-
Oct 06 03:36:08 node-0 rancherd[2171]: time="2023-10-06T03:36:08Z" level=info msg="[stdout]: [INFO] Value from https://harvester.192.168.48.240.sslip.io:443/cacerts is an x509 certificate"
Oct 06 03:36:09 node-0 rancherd[2171]: time="2023-10-06T03:36:09Z" level=info msg="[stderr]: time=\"2023-10-06T03:36:09Z\" level=info msg=\"Running probes defined in /var/lib/rancher/rancherd/plan/plan.json\""
234
-
Oct 06 03:36:10 node-0 rancherd[2171]: time="2023-10-06T03:36:10Z" level=info msg="[stderr]: time=\"2023-10-06T03:36:10Z\" level=info msg=\"Probe [kubelet] is unhealthy\""
235
-
236
-
```
237
-
238
-
The above log shows that `rancherd` is waiting for `kubelet` to become healthy. `rancherd` is doing nothing wrong and is working as expected. The next step is to check the `rancher-system-agent`:
239
-
240
-
```sh
241
-
$ journalctl -u rancher-system-agent.service
242
-
Oct 06 03:43:51 node-0 systemd[1]: rancher-system-agent.service: Scheduled restart job, restart counter is at 88.
243
-
Oct 06 03:43:51 node-0 systemd[1]: Stopped Rancher System Agent.
244
-
Oct 06 03:43:51 node-0 systemd[1]: Started Rancher System Agent.
245
-
Oct 06 03:43:51 node-0 rancher-system-agent[4164]: time="2023-10-06T03:43:51Z" level=info msg="Rancher System Agent version v0.3.3 (9e827a5) is starting"
246
-
Oct 06 03:43:51 node-0 rancher-system-agent[4164]: time="2023-10-06T03:43:51Z" level=info msg="Using directory /var/lib/rancher/agent/work for work"
247
-
Oct 06 03:43:51 node-0 rancher-system-agent[4164]: time="2023-10-06T03:43:51Z" level=info msg="Starting remote watch of plans"
248
-
Oct 06 03:43:51 node-0 rancher-system-agent[4164]: time="2023-10-06T03:43:51Z" level=info msg="Initial connection to Kubernetes cluster failed with error Get \"https://harvester.192.168.48.240.sslip.io/version\": x509: certificate signed by unknown authority, removing CA data and trying again"
249
-
Oct 06 03:43:51 node-0 rancher-system-agent[4164]: time="2023-10-06T03:43:51Z" level=fatal msg="error while connecting to Kubernetes cluster with nullified CA data: Get \"https://harvester.192.168.48.240.sslip.io/version\": x509: certificate signed by unknown authority"
250
-
Oct 06 03:43:51 node-0 systemd[1]: rancher-system-agent.service: Main process exited, code=exited, status=1/FAILURE
251
-
Oct 06 03:43:51 node-0 systemd[1]: rancher-system-agent.service: Failed with result 'exit-code'.
252
-
```
253
-
254
-
If you see a similar log output, you need to manually add the CA to the trust list on each joining node with the following commands:
255
-
256
-
```sh
257
-
# prepare the CA as embedded-rancher-ca.pem on the nodes
Copy file name to clipboardexpand all lines: versioned_docs/version-v1.4/install/iso-install.md
+6-3
Original file line number
Diff line number
Diff line change
@@ -62,8 +62,8 @@ The following [video](https://youtu.be/X0VIGZ_lExQ) shows a quick overview of an
62
62
1. Choose the installation disk you want to install the Harvester cluster on and the data disk you want to store VM data on. By default, Harvester uses [GUID Partition Table (GPT)](https://en.wikipedia.org/wiki/GUID_Partition_Table) partitioning schema for both UEFI and BIOS. If you use the BIOS boot, then you will have the option to select [Master boot record (MBR)](https://en.wikipedia.org/wiki/Master_boot_record).
- `Installation disk`: The disk to install the Harvester cluster on.
65
+
66
+
- `Installation disk`: The disk to install the Harvester cluster on.
67
67
- `Data disk`: The disk to store VM data on. Choosing a separate disk to store VM data is recommended.
68
68
- `Persistent size`: If you only have one disk or use the same disk for both OS and VM data, you need to configure persistent partition size to store system packages and container images. The default and minimum persistent partition size is 150 GiB. You can specify a size like 200Gi or 153600Mi.
69
69
@@ -231,9 +231,12 @@ Oct 06 03:43:51 node-0 systemd[1]: rancher-system-agent.service: Main process ex
231
231
Oct 06 03:43:51 node-0 systemd[1]: rancher-system-agent.service: Failed with result 'exit-code'.
232
232
```
233
233
234
-
If you see a similar log output, you need to manually add the CA to the trust list on each joining node with the following commands:
234
+
If you see similar log output, you must change the Rancher setting and manually add the CA to the trust list on each joining node with the following commands:
235
235
236
236
```sh
237
+
# Change the value of the Rancher `agent-tls-mode` setting from `strict` to `system-store`.
0 commit comments