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
{{ message }}
Repository navigation
Commit 842b8fd
Browse filesBrowse the repository at this point in the historyBrowse files
## Stuck in`Loading images. This may take a few minutes...`
25
+
## 卡在`Loading images. This may take a few minutes...`
26
26
27
-
Because the system doesn't have a default route, your installer may become "stuck" in this state. You can check your route status by executing the following command:
27
+
由於系統沒有預設路由,您的安裝程式可能會「卡在」這個狀態。您可以透過執行以下命令來檢查路由狀態:
28
28
29
29
```shell
30
30
$ ip route
31
-
default via 10.10.0.10 dev mgmt-br proto dhcp <-- Does a default route exist?
31
+
default via 10.10.0.10 dev mgmt-br proto dhcp <-- 是否存在預設路由?
32
32
10.10.0.0/24 dev mgmt-br proto kernel scope link src 10.10.0.15
33
33
```
34
34
35
-
Check that your DHCP server offers a default route option. Attaching content from `/run/cos/target/rke2.log`is helpful too.
For more information, see [DHCP Server Configuration](../install/pxe-boot-install.md#dhcp-server-configuration).
37
+
如需更多資訊,請參閱 [DHCP Server Configuration](../install/pxe-boot-install.md#dhcp-server-configuration)。
38
38
39
-
## Modifying cluster token on agent nodes
39
+
## 修改代理節點上的叢集權杖
40
40
41
-
When an agent node fails to join the cluster, it can be related to the cluster token not being identical to the server node token.
42
-
In order to confirm the issue, connect to your agent node (i.e. with [SSH](./os.md#how-to-log-in-to-a-harvester-node) and check the `rancherd`service log with the following command:
msg="failed to bootstrap system, will retry: generating plan: response 502: 502 Bad Gateway getting cacerts: <html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body>\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n"
53
53
```
54
54
55
-
Note that the Rancher version and IP address depend on your environment and might differ from the message above.
55
+
請注意,Rancher 版本和 IP 位址取決於您的環境,可能與上述訊息不同。
56
56
57
-
To fix the issue, you need to update the token value in the `rancherd`configuration file `/etc/rancher/rancherd/config.yaml`.
Before checking the status of Harvester components, obtain a copy of the Harvester cluster's kubeconfig file following the [guide](../faq.md#how-can-i-access-the-kubeconfig-file-of-the-harvester-cluster).
After you obtain a copy of the kubeconfig file, run the following script against the cluster to check the readiness of each component.
111
+
取得 kubeconfig 檔案副本後,針對叢集執行以下腳本以檢查每個元件的就緒狀態。
114
112
115
-
- Harvester components script
113
+
- Harvester 元件腳本
116
114
```shell
117
115
#!/bin/bash
118
116
@@ -147,44 +145,44 @@ After you obtain a copy of the kubeconfig file, run the following script against
147
145
```
148
146
149
147
:::note
150
-
151
-
You must replace `<VIP>` with the [real VIP](../install/management-address.md#how-to-get-the-vip-mac-address), which is the value of `kube-vip.io/requestedIP` in the link.
Please include the following information in a bug report when reporting a failed installation:
155
+
在報告安裝失敗時,請在錯誤報告中包含以下資訊:
158
156
159
-
- A failed installation screenshot.
160
-
- System information and logs.
161
-
- Available as of v1.0.2
157
+
- 安裝失敗的螢幕截圖。
158
+
- 系統資訊和日誌。
159
+
- 從 v1.0.2 開始提供
162
160
163
-
Please follow the guide in [Logging into the Harvester Installer (a live OS)](#logging-into-the-harvester-installer-a-live-os) to log in. And run the command to generate a tarball that contains troubleshooting information:
The command output messages contain the generated tarball path. For example the path is `/var/loq/scc_aaa_220520_1021 804d65d-c9ba-4c54-b12d-859631f892c5.txz` in the following example:
A failure PXE Boot installation automatically generates a tarball if the [`install.debug`](../install/harvester-configuration.md#installdebug) field is set to `true` in the Harvester configuration file.
## Harvester Console shows "Setting up Harvester" after day 0 Installation
177
+
## Harvester 控制台在第 0 天安裝後顯示「Setting up Harvester」
180
178
181
-
### Issue Description
179
+
### 問題描述
182
180
183
-
After a successful installation, the Harvester console persistently shows `Setting up Harvester`. While most UI and CLI operations remain unaffected, attempts to [start an upgrade](../upgrade/automatic.md#start-an-upgrade) are blocked.
181
+
成功安裝後,Harvester 控制台持續顯示 `Setting up Harvester`。雖然大多數 UI 和 CLI 操作不受影響,但嘗試[開始升級](../upgrade/automatic.md#start-an-upgrade)會被阻止。
The following information is displayed after you run the command `kubectl get managedchart -n fleet-local harvester -oyaml`:
185
+
執行命令 `kubectl get managedchart -n fleet-local harvester -oyaml` 後會顯示以下資訊:
188
186
189
187
```yaml
190
188
...
@@ -203,18 +201,18 @@ status:
203
201
type: Ready
204
202
```
205
203
206
-
### Root Cause
204
+
### 根本原因
207
205
208
-
The Harvester console runs the following command to determine if the status of the `harvester` ManagedChart (in the `fleet-local` namespace) is `Ready`.
jq 'map(select(.type == "Ready" and .status == "True")) | length')
213
211
```
214
212
215
-
The `ManagedChart` CRD is used by [Fleet](https://fleet.rancher.io/) to manage resources via GitOps. If any of those resources are directly modified, `ManagedChart` records and flags the deviations. In the above example, the error occurred because a custom image tag was directly applied to the `harvester-system/harvester-network-controller` DaemonSet.
**Summary**: When you enable the `rancher-logging`add-on, Harvester attempts to install the [Logging Operator](https://kube-logging.dev/docs/#overview). The installation fails when the operator already exists on the cluster, which may be a stale resource from previous upgrade attempts or created by the current ongoing upgrade.
You may encounter the issue in the following situations:
83
+
您可能會在以下情況下遇到此問題:
84
84
85
-
-The `rancher-logging`add-on is initially disabled. You start the upgrade with the **Enable Logging**option selected. Without waiting for the upgrade to be completed, you enable the `rancher-logging`add-on. The Harvester UI displays an error message.
-The `rancher-logging`add-on is initially disabled. You start the upgrade with the **Enable Logging**option selected and wait until the upgrade is completed. The `managedchart` and `logging` objects are not removed because of a [known issue](https://github.com/harvester/harvester/issues/7654). Next, you enable the`rancher-logging`add-on. The Harvester UI displays an error message.
1.If an upgrade is in progress, wait until it is successfully completed or removed.
91
+
1.如果升級正在進行中,請等待其成功完成或移除。
92
92
93
93
:::info important
94
94
95
-
To avoid logging conflicts, do not enable or disable the `rancher-logging`add-on while an upgrade is in progress. This action is blocked in Harvester v1.7.0 and later versions.
All add-ons must be in a healthy state prior to starting an upgrade. This prerequisite is automatically verified in Harvester v1.7.0 and later versions.
0 commit comments