Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

The vSphere plugin for Velero fails to backup persistent volumes when non-vSphere persistent volumes are present (78977)

Last Updated: 5/5/2020Categories: InformationalTotal Views: 3938Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

A Kubernetes cluster has persistent volumes present with differing configurations. There may be persistent volumes using vSphere CSI but others may use NFS or some other backing.

A Velero backup using the vSphere plugin to perform a volume snapshot of a vSphere CSI backed persistent volume is created and appears to complete successfully.

The Velero upload process never exists the New phase. You see output similar to the following when running kubectl -n velero get uploads.veleroplugin.io -o yaml:

items:
- apiVersion: veleroplugin.io/v1
kind: Upload
metadata:
creationTimestamp: "2020-05-05T14:32:11Z"
generation: 1
name: upload-154d2c24-49b0-40eb-a4c2-76d68ae43579
namespace: velero
resourceVersion: "213757"
selfLink: /apis/veleroplugin.io/v1/namespaces/velero/uploads/upload-154d2c24-49b0-40eb-a4c2-76d68ae43579
uid: 65e0a916-6575-433c-a2f5-651a23bd2892
spec:
backupTimestamp: "2020-05-05T14:32:11Z"
snapshotID: ivd:c25cc856-0d9e-44ec-b542-cd51a8e54dba:154d2c24-49b0-40eb-a4c2-76d68ae43579
status:
nextRetryTimestamp: "2020-05-05T14:32:11Z"
phase: New
progress: {}

When you examine the pods running in the velero namespace, you see that the datamgr-for-vsphere-plugin pods are in a CrashLoopBackoff or Error state.

NAME                               READY   STATUS      RESTARTS   AGE
datamgr-for-vsphere-plugin-fn9pp   0/1     Error       4          30m

You see messages similar to the following when you review the logs for the datamgr-for-vsphere-plugin pods:

time="2020-05-05T00:22:20Z" level=info msg="Filtering out the upload request from nodes other than test-md-0-7c9d5d4cd-wcrcr" controller=upload generation=1 logSource="/go/src/github.com/vmware-tanzu/velero-plugin-for-vsphere/pkg/controller/upload_controller.go:121" name=upload-08b98b68-e545-481c-9855-a697f7b94161 namespace=velero phase=New
2020/05/05 00:22:20 pei = ivd:5ac38391-4773-4c1f-9d88-d8fd7105a9fa:08b98b68-e545-481c-9855-a697f7b94161
E0505 00:22:20.391671       1 runtime.go:78] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
goroutine 38 [running]:
k8s.io/apimachinery/pkg/util/runtime.logPanic(0x1e39b60, 0x381a630)
/go/pkg/mod/k8s.io/[email-masked]/pkg/util/runtime/runtime.go:74 +0xa3
k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue can occur when there are non-vSphere persistent volumes present in the cluster.

Resolution

This is a known issue affecting the vSphere plugin for Velero. There is currently no resolution.

Workaround

You can workaround this issue by only having vSphere CSI backed persistent volumes present in a cluster where you will be running Velero backups using the vSphere plugin to perform volume snapshots. Alternatively, you can perform Velero backups without taking volume snapshots.

To fix the datamgr-for-vsphere-plugin pods that are in a CrashLoopBackoff or Error state, you can delete the Velero uploads and recreate the pods by issuing commands similar to the following:

kubectl -n velero get uploads
kubectl -n velero delete upload <upload ID from  previous command>
kubectl -n velerro delete pod datamgr-for-vsphere-plugin-<UUID>

Related Information

Velero Plugin for vSphere

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
[解決済み] ECDS-11794：Outlook.com でホストされた E メールを使用しているユーザーへの Workspace ONE UEM からの E メール通知が遅延する (78934)

KB
•
VMware AirWatch Zebra MX Service 4.8 for Android リリースのお知らせ (79001)

KB
•
「構成ファイルの読み取りまたは書き込みができませんでした。キーストアが改ざんされたか、パスワードが正しくありません」(Could not read or write the configuration file: Keystore was tampered with, or password was incorrect) というエラー メッセージが Cloud Director 9.5 から 10.0 への移行中に表示される (78924)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Tanzu Kubernetes Grid Plus

VMware Tanzu Kubernetes Grid

VMware PKS

VMware Cloud Native Storage

Related Versions:

VMware Tanzu Kubernetes Grid Plus 1.x

VMware Tanzu Kubernetes Grid 1.x

VMware PKS 1.x

VMware Cloud Native Storage 1.x

Take Our Survey

Support Assistant