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
The saved snapshot should succeed. The first attempt times out in 10 seconds. And a retry attempted after maybe 30 to 60 seconds starts saving successfully again.
Reproducing Results/Observations:
k3s version used for replication:
$ k3s -v
k3s version v1.29.4-rc1+k3s1 (d973fadb)
go version go1.21.9
$ sudo /usr/local/bin/k3s etcd-snapshot save --s3 --s3-bucket=<bucket> --s3-folder=<folder> --s3-region=<region> --s3-access-key=xxxx --s3-secret-key="xxxx" --debug
time="2024-04-19T18:04:31Z" level=warning msg="Unknown flag --cluster-init found in config.yaml, skipping\n"
time="2024-04-19T18:04:31Z" level=warning msg="Unknown flag --write-kubeconfig-mode found in config.yaml, skipping\n"
time="2024-04-19T18:04:31Z" level=warning msg="Unknown flag --node-external-ip found in config.yaml, skipping\n"
time="2024-04-19T18:04:31Z" level=warning msg="Unknown flag --node-label found in config.yaml, skipping\n"
time="2024-04-19T18:04:31Z" level=warning msg="Cluster CA certificate is not trusted by the host CA bundle, but the token does not include a CA hash. Use the full token from the server's node-token file to enable Cluster CA validation."
time="2024-04-19T18:04:41Z" level=fatal msg="see server log for details: Post \"https://127.0.0.1:6443/db/snapshot\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
Also, on the journal logs, the server is still performing some operations during the above timeframe, and we do not see any error reported on the journal logs, when the client timed out.
The text was updated successfully, but these errors were encountered:
Expected Behavior:
etcd snapshot save action should be successful and not timeout in 10 seconds.
Validation Results:
k3s version used for validation:
$ k3s -v
k3s version v1.29.4+k3s-d3b60543 (d3b60543)
go version go1.21.9
$ sudo /usr/local/bin/k3s etcd-snapshot save --s3 --s3-bucket=<s3-bucket> --s3-region=<s3-region> --s3-access-key=xxxx --s3-secret-key="xxxx" --debug
time="2024-04-22T20:19:49Z" level=warning msg="Unknown flag --cluster-init found in config.yaml, skipping\n"
time="2024-04-22T20:19:49Z" level=warning msg="Unknown flag --write-kubeconfig-mode found in config.yaml, skipping\n"
time="2024-04-22T20:19:49Z" level=warning msg="Unknown flag --node-external-ip found in config.yaml, skipping\n"
time="2024-04-22T20:19:49Z" level=warning msg="Unknown flag --node-label found in config.yaml, skipping\n"
time="2024-04-22T20:19:49Z" level=warning msg="Cluster CA certificate is not trusted by the host CA bundle, but the token does not include a CA hash. Use the full token from the server's node-token file to enable Cluster CA validation."
time="2024-04-22T20:20:19Z" level=info msg="Snapshot on-demand-ip-172-31-16-180-1713817190 saved."
time="2024-04-22T20:20:19Z" level=info msg="Snapshot on-demand-ip-172-31-16-180-1713817190 saved."
As we can see from log timings above, the save did not timeout in 10 seconds. It waits for the save completion and the save is successful. Closing the bug.
Issue found on master branch with version v1.29.4-rc1+k3s1
Environment Details
Infrastructure
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
Config.yaml:
Testing Steps
Expected behavior:
The saved snapshot should succeed. The first attempt times out in 10 seconds. And a retry attempted after maybe 30 to 60 seconds starts saving successfully again.
Reproducing Results/Observations:
Also, on the journal logs, the server is still performing some operations during the above timeframe, and we do not see any error reported on the journal logs, when the client timed out.
The text was updated successfully, but these errors were encountered: