velero: backup logs gzip: invalid header
What steps did you take and what happened: Trying to get logs results in gzip invalid headers output:
$ velero backup logs first-backup
An error occurred: gzip: invalid header
What did you expect to happen: I expected logs to output. This command was presented to me when I ran my first backup.
The output of the following commands will help us better understand what’s going on: (Pasting long output into a GitHub gist or other pastebin is fine.)
kubectl logs deployment/velero -n velero
Find the logs in gist here: https://gist.githubusercontent.com/CafeLungo/787a0ed66945b8e3433edfdfe6a4e164/raw/37c27eef32c101e93c9dea8d318d373d96b68ca2/velero-first-backup-logs.txtvelero backup describe <backupname>
orkubectl get backup/<backupname> -n velero -o yaml
Name: first-backup
Namespace: velero
Labels: velero.io/storage-location=default
Annotations: velero.io/source-cluster-k8s-gitversion=v1.20.7
velero.io/source-cluster-k8s-major-version=1
velero.io/source-cluster-k8s-minor-version=20
Phase: Completed
Errors: 0
Warnings: 0
Namespaces:
Included: *
Excluded: <none>
Resources:
Included: *
Excluded: <none>
Cluster-scoped: auto
Label selector: <none>
Storage Location: default
Velero-Native Snapshot PVs: auto
TTL: 720h0m0s
Hooks: <none>
Backup Format Version: 1.1.0
Started: 2021-06-25 11:12:56 -0400 EDT
Completed: 2021-06-25 11:13:02 -0400 EDT
Expiration: 2021-07-25 11:12:56 -0400 EDT
Total items to be backed up: 376
Items backed up: 376
Velero-Native Snapshots: <none included>
velero backup logs <backupname>
An error occurred: gzip: invalid header
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
- Velero version (use
velero version
):
Client:
Version: v1.6.1
Git commit: -
Server:
Version: v1.6.1
- Velero features (use
velero client config get features
):
features: <NOT SET>
- Kubernetes version (use
kubectl version
):
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-12T14:18:45Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.7", GitCommit:"132a687512d7fb058d0f5890f07d4121b3f0a2e2", GitTreeState:"clean", BuildDate:"2021-05-12T12:32:49Z", GoVersion:"go1.15.12", Compiler:"gc", Platform:"linux/amd64"}
- Kubernetes installer & version:
$ minikube version
minikube version: v1.21.0
commit: 76d74191d82c47883dc7e1319ef7cebd3e00ee11
- Cloud provider or hardware configuration: Using docker on macOS
$ docker version
Client:
Cloud integration: 1.0.17
Version: 20.10.7
API version: 1.41
Go version: go1.16.4
Git commit: f0df350
Built: Wed Jun 2 11:56:22 2021
OS/Arch: darwin/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.7
API version: 1.41 (minimum version 1.12)
Go version: go1.13.15
Git commit: b0f5bc3
Built: Wed Jun 2 11:54:58 2021
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.4.6
GitCommit: d71fcd7d8303cbf684402823e425e9dd2e99285d
runc:
Version: 1.0.0-rc95
GitCommit: b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
docker-init:
Version: 0.19.0
GitCommit: de40ad0
- OS (e.g. from
/etc/os-release
): macOS 10.15.7
Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project’s top voted issues listed here.
Use the “reaction smiley face” up to the right of this comment to vote.
- 👍 for “I would like to see this bug fixed as soon as possible”
- 👎 for “There are more important bugs to focus on right now”
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 6
- Comments: 15 (1 by maintainers)
Success! Thank you @jr0dd! I added an ingress at
https://minio-api.example.com
(obviously substituting example.com) pointing to the minio api port and changed mypublicUrl
in velero to use that and now both the logs and the resource list in the backup details is loading.