Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Deleting an Enterprise PKS cluster may not complete when the vSphere CSI is used to provision persistent volumes (78981)

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

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

A cluster is created in Enterprise PKS 1.7 and vSphere CSI is configured to allow for persistent volumes to be created via vSphere Cloud Native Storage (CNS).

A workload is deployed with persistent volumes that makes use of vSphere CNS.

An attempt to delete the cluster is made but it hangs indefinitely.

You see that the drain-cluster errand task is not completing. You see output similar to the following when running bosh task <id>:

Task 137 | 13:17:33 | Preparing deployment: Preparing deployment
Task 137 | 13:17:33 | Deprecation: Global 'properties' are deprecated. Please define 'properties' at the job level.
Task 137 | 13:17:36 | Warning: Executing errand on multiple instances in parallel. Use the `--instance` flag to run the errand on a single instance.
Task 137 | 13:17:36 | Preparing deployment: Preparing deployment (00:00:03)
Task 137 | 13:17:36 | Running errand: worker/64b96419-83bb-48eb-a1c5-5823855df887 (1)
Task 137 | 13:17:36 | Running errand: worker/f85cef70-0dc8-41ba-9a47-5c64c844411b (0)
Task 137 | 13:17:40 | Running errand: worker/64b96419-83bb-48eb-a1c5-5823855df887 (1) (00:00:04)
Task 137 | 13:17:40 | Fetching logs for worker/64b96419-83bb-48eb-a1c5-5823855df887 (1): Finding and packing log files (00:00:01)

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

Resolution

This is a known issue affecting Enterprise PKS 1.7 when vSphere Cloud Native storage is used. There is currently no resolution.

Workaround

To workaround this issue you can issue the bosh cancel-task <id> command to cancel the drain-cluster errand task.

To prevent this issue from occurring you can manually delete the workload that is using CNS to provision persistent volumes prior to deleting the cluster.

Related Information

Cloud Native Storage (CNS) on vSphere

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
VMware Update Manager の診断情報の収集 (1003693)

KB
•
将 Cloud Director 9.5 迁移到 10.0 的过程中，出现“无法读取或写入配置文件: 密钥库已被篡改，或密码不正确”错误 (78924)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware PKS

VMware Cloud Native Storage

Related Versions:

VMware PKS 1.7.x

VMware Cloud Native Storage 1.x

Take Our Survey

Support Assistant