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
Node(s) CPU architecture, OS, and Version:
Linux harana-server 5.15.0-75-generic #82-Ubuntu SMP Tue Jun 6 23:10:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
1 server, 2 agents (Linux and Windows)
Describe the bug:
When restarting RKE2 it loads with the previous state e.g. the uptime on Pods, Containers, Nodes are not reset back to zero.
Steps To Reproduce:
Installed RKE2 using Quick Start.
Previous State:
Stopped RKE2:
systemctl stop rke2-server.service
But RKE2 is not stopped:
Manually kill all RKE2 processes:
pkill -f rke2
RKE2 is now stopped so we restart it with:
systemctl start rke2-server.service
New State:
Expected behavior:
Uptime should be zero. IP address should change etc.
The text was updated successfully, but these errors were encountered:
Environmental Info:
RKE2 Version:
v1.25.11+rke2r1
Node(s) CPU architecture, OS, and Version:
Linux harana-server 5.15.0-75-generic #82-Ubuntu SMP Tue Jun 6 23:10:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
1 server, 2 agents (Linux and Windows)
Describe the bug:
When restarting RKE2 it loads with the previous state e.g. the uptime on Pods, Containers, Nodes are not reset back to zero.
Steps To Reproduce:
Installed RKE2 using Quick Start.
Previous State:
Stopped RKE2:
But RKE2 is not stopped:
Manually kill all RKE2 processes:
RKE2 is now stopped so we restart it with:
New State:
Expected behavior:
Uptime should be zero. IP address should change etc.
The text was updated successfully, but these errors were encountered: