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
When the agent needs to be restarted, it does not get restarted. The reason is that the wildcard k3s* only applies to loaded and active systemd units. However, in tests such as multicidr or the upcoming tailscale, the k3s-agent unit is loaded but inactive. Therefore, the wildcard will not apply and thus the e2e test fails
Steps To Reproduce:
Installed K3s:
Expected behavior:
Actual behavior:
Additional context / logs:
The text was updated successfully, but these errors were encountered:
Environmental Info:
K3s Version:
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
Describe the bug:
When the agent needs to be restarted, it does not get restarted. The reason is that the wildcard
k3s*
only applies to loaded and active systemd units. However, in tests such as multicidr or the upcoming tailscale, the k3s-agent unit is loaded but inactive. Therefore, the wildcard will not apply and thus the e2e test failsSteps To Reproduce:
Expected behavior:
Actual behavior:
Additional context / logs:
The text was updated successfully, but these errors were encountered: