Skip to content

[BUG] Second node cannot join with Rancher v2.13.0-alpha4 #9414

@FrankYang0529

Description

@FrankYang0529

Describe the Bug

In Harvester, the second node cannot join the cluster. There is error in rancher-system-agent v0.3.14-rc.4 (e725216).

Nov 04 02:06:20 harvester-node-1 rancher-system-agent[4111]: time="2025-11-04T02:06:20Z" level=info msg="Rancher System Agent version v0.3.14-rc.4 (e725216) is starting"
Nov 04 02:06:20 harvester-node-1 rancher-system-agent[4111]: time="2025-11-04T02:06:20Z" level=info msg="Using directory /var/lib/rancher/agent/work for work"
Nov 04 02:06:20 harvester-node-1 rancher-system-agent[4111]: time="2025-11-04T02:06:20Z" level=info msg="Starting remote watch of plans"
Nov 04 02:06:20 harvester-node-1 rancher-system-agent[4111]: time="2025-11-04T02:06:20Z" level=info msg="Starting /v1, Kind=Secret controller"
Nov 04 02:08:20 harvester-node-1 rancher-system-agent[4111]: I1104 02:08:20.213189    4111 reflector.go:568] "Warning: watch ended with error" reflector="pkg/mod/k8s.io/client-go@v0.34.1/tools/cache/reflector.go:290" type="*v1.Secret" err="an error on the server (\"unable to decode an event from the watch stream: stream error: stream ID 5; INTERNAL_ERROR; received from peer\") has prevented the request from succeeding"

ref: rancher/rancher#52592

To Reproduce

Use harvester/harvester-installer#1173 to start 2-node Harvester cluster.

Expected Behavior

The second node can join the cluster.

Support Bundle for Troubleshooting

N/A

Environment

Additional context

No response

Workaround and Mitigation

No response

Metadata

Metadata

Labels

area/embedded-rancherRancher for Harvester cluster provisionkind/bugIssues that are defects reported by users or that we know have reached a real releaserequire/rancherRequire a Rancher fix. Create a corresponding upstream issue and correlate it to this issue.require/reproduceRequire adding a `reproduce` label.require/severityRequire adding a `severity` label.

Type

Projects

Status

Closed

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions