We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Saw this on osmosis:
apiVersion: snapshot.storage.k8s.io/v1 kind: VolumeSnapshot metadata: creationTimestamp: "2023-03-28T21:00:10Z" finalizers: - snapshot.storage.kubernetes.io/volumesnapshot-as-source-protection generation: 1 labels: app.kubernetes.io/component: ScheduledVolumeSnapshot app.kubernetes.io/created-by: cosmos-operator app.kubernetes.io/instance: osmosis-mainnet-fullnode-0 app.kubernetes.io/name: osmosis-mainnet-fullnode app.kubernetes.io/revision: 87aa4b0d app.kubernetes.io/version: v15.0.0 cosmos.strange.love/network: mainnet cosmos.strange.love/source: osmosis-mainnet-fullnode name: osmosis-mainnet-fullnode-202303282100 namespace: strangelove resourceVersion: "158984848" uid: e62a5880-8837-4127-8807-1d18d15642db spec: source: persistentVolumeClaimName: "" volumeSnapshotClassName: cosmos-fullnode status: error: message: 'Failed to create snapshot content with error snapshot controller failed to update osmosis-mainnet-fullnode-202303282100 on API server: cannot get claim from snapshot' time: "2023-03-28T21:00:10Z" readyToUse: false
Also what's odd is persistentVolumeClaimName: ""
persistentVolumeClaimName: ""
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Saw this on osmosis:
Also what's odd is
persistentVolumeClaimName: ""
The text was updated successfully, but these errors were encountered: