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

Disabling a running Harbor on a WCP cluster fails (77151)

Last Updated: 4/6/2020Categories: TroubleshootingTotal Views: 4852Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Disabling a running Harbor on the WCP cluster fails with the error:

Harbor namespace vmware-system-registry-xxxxx delete operation timed out after 600 seconds.

Cause

This issue occurs due to a failed disable Harbor registry on the WCP cluster due to harbor namespace deletion failure.

Resolution

To resolve the issue use the kubectl command to delete the Harbor namespace:

Connect to the WCP cluster with SSH and the root user.

Run this command to find the Harbor namespace: kubectl get ns -A

Example Output:

NAME                                        STATUS   AGE
default                                     Active   24h
kube-node-lease                             Active   24h
kube-public                                 Active   24h
kube-system                                 Active   24h
my-podvm-ns                                 Active   23h
storage-policy-test                         Active   23h
test-dataprovider-ns                        Active   23h
test-exec-ns                                Active   23h
test-kube-events-ns                         Active   23h
test-multiple-podvm-ns                      Active   23h
test-pod-security-policy                    Active   23h
test-podvm-annotations                      Active   23h
test-podvm-tolerations                      Active   23h
test-resource-quota-ns                      Active   23h
test-telemetry                              Active   23h
test-update-workload-ns                     Active   23h
vmware-system-appplatform-operator-system   Active   24h
vmware-system-capw                          Active   24h
vmware-system-csi                           Active   24h
vmware-system-gcm                           Active   24h
vmware-system-kubeimage                     Active   24h
vmware-system-nsx                           Active   24h
vmware-system-registry                      Active   24h
vmware-system-registry-787466687            Active   5s
vmware-system-vmop                          Active   24h

Run this command:

kubectl delete ns vmware-system-registry-xxxxxxxx

Note: If the deletion hangs, see: https://success.docker.com/article/kubernetes-namespace-stuck-in-terminating

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
如果 Harbor 注册表负载均衡器 IP 无法进行公共访问，请配置 HTTPS 代理 (77020)

KB
•
vCenter Server 7.0 へのアップグレード後にスマート カードと RSA SecurID による認証が停止する (78057)

KB
•
从阵列中移除后，动态发现的目标保留在 UI 中 (78041)

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 vCenter Server

Related Versions:

VMware vCenter Server 7.0.x

Take Our Survey

Support Assistant