Open krumware opened 5 years ago
Validated using v0.2.7
The nodes were of Ubuntu, 16.04 LTS, images rancher-cluster.yml
nodes:
- address: x.x.x.x
internal_address: x.x.x.x
user: ubuntu
role: [controlplane,etcd,worker]
ssh_key_path:<path-to-key>
- address: x.x.x.x
internal_address: x.x.x.x
user: ubuntu
role: [controlplane,etcd,worker]
ssh_key_path: <path-to-key>
- address: x.x.x.x
internal_address: x.x.x.x
user: ubuntu
role: [controlplane,etcd,worker]
ssh_key_path: <path-to-key>
services:
etcd:
snapshot: true
creation: 6h
retention: 24h
./rke etcd snapshot-save --config rancher-cluster.yml
-- local snapshots are taken successfully. Can be seen on the etcd nodes in /opt/rke/etcd-snapshots
directory./rke etcd snapshot-save --config rancher-cluster.yml --name sowmya-snapshots2 --s3 --access-key xxxxx --secret-key xxxxx --bucket-name xxxx --s3-endpoint xxxx
-- snapshots are seen saved on the S3 bucket.May be worth clarifying that the nodes are RancherOS. Also, the .zip is created in s3, just has no file contents.
Is there a way to opt in to a more verbose debug/logging level?
verified in a RancherOS instance.
rke v0.2.7
image - rancheros-v1.5.0-hvm-1
./rke etcd snapshot-restore --config rancher-cluster.yml --name snapshot-name3 --s3 --access-key xxx --secret-key xxx --bucket-name xxx --s3-endpoint s3.amazonaws.com
I'd like to help track this down, or at least narrow this down to something environmental. Is there any additional information I can provide, or a way to change the logging level?
@sowmyav27 updated information: the file size of the zip file in AWS S3 is approximately 20.5 MB. When I download on a windows machine and attempt extract, it appears to be empty. The default windows extraction tool thinks that the zip file is corrupt, and browsing the zip file makes it appear to be empty. But if I use a third party extraction tool such as 7zip, then it does properly extract with a backup folder and the file included inside.
RKE version:
v0.2.7
Docker version: (
docker version
,docker info
preferred)18.09.7 (local machine)
Operating system and kernel: (
cat /etc/os-release
,uname -r
preferred) WSL 2 UbuntuType/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
AWS
cluster.yml file:
Steps to Reproduce:
rke etcd snapshot-save --config rancher-cluster.yml
INFO[0037] Finished saving snapshot [rancher-2-ha-backup] on all etcd hosts
/opt/rke/etcd-snapshots
-or-
rke etcd snapshot-save --config rancher-cluster.yml --name rancher-2-ha-backup \ --s3 --access-key xxx --secret-key xxx \ --bucket-name xxx --s3-endpoint s3.amazonaws.com
INFO[0037] Finished saving snapshot [rancher-2-ha-backup] on all etcd hosts
Results:
directory is empty
-or-
rancher-2-ha-backup.zip is empty
additional info
I also observed this behavior with v0.2.4 Rancher version is rancher-latest 2.2.7 There is no additional --debug flag available for this command. All rke output appears as though everything is normal and has completed successfully. Followed the steps in the documentation here: https://rancher.com/docs/rancher/v2.x/en/backups/backups/ha-backups/#option-b-one-time-snapshots