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

Harbor upgrade from 1.8.x to 1.9.3 fails with harbor job (76299)

Last Updated: 1/7/2020Categories: TroubleshootingTotal Views: 3642Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Harbor upgrade from 1.8.x to 1.9.3 fails with an error similar to:
Action Failed get_task: Task 1b4c82f6-cab2-41a9-46ae-d540e9e55a2e result: 1 of 4 pre-start scripts failed. Failed Jobs: harbor. Successful Jobs: enable-bosh-dns, bosh-dns, wavefront.

You are unable to login to Harbor UI.

In the core.log file on harbor vm, you see the entries similar to:
135 Nov 19 12:05:58 172.80.1.1 core[5878]: 2019-11-19T12:05:58Z [INFO] [/core/main.go:107]: Start to sync quota data .....
136 Nov 19 12:05:58 172.80.1.1 core[5878]: 2019-11-19T12:05:58Z [INFO] /core/api/quota/migrator.go:90]: [Quota-Sync]:: start to ping server ... [chart]
137 Nov 19 12:06:16 172.80.1.1 core[5878]: 2019-11-19T12:06:16Z [INFO] [/core/api/quota/migrator.go:92]: [Quota-Sync]:: fail to ping server ... [chart], quit sync ...
138 Nov 19 12:06:16 172.80.1.1 core[5878]: 2019-11-19T12:06:16Z [ERROR] [/core/main.go:109]: Fail to sync quota data, received unexpected status code: 403 <HTML><HEAD>

When you check the proxy settings in the Harbor tile configuration, you see below info listed:
127.0.0.1,localhost,core,registry

Cause

Before Harbor 1.9.0, the http_proxy/https_proxy setting is used in clair component to update the CVE data from internet. And the no_proxy setting was mentioned as:
127.0.0.1,localhost,core,registry

From Harbor 1.9.3, the http_proxy/https_proxy setting is populated to core, jobservice, clair components as well. And the no_proxy setting should contain all containers as below. Otherwise the core component can not communicate with the chartmuseum component.
127.0.0.1,localhost,.local,.internal,log,db,redis,nginx,core,portal,postgresql,jobservice,registry,registryctl,clair,chartmuseum,notary-server

When you try to upgrade Harbor tile which has the old no_proxy setting values, core components fails to access the chartmuseum component via proxy and causes upgrade failure.

Resolution

This is a known issue while upgrading Harbor from 1.8.x to 1.9.3.

Workaround

To work around this issue, update the below info at Harbor tile > Networking > No Proxy field and then apply changes from Ops Manager.
127.0.0.1,localhost,.local,.internal,log,db,redis,nginx,core,portal,postgresql,jobservice,registry,registryctl,clair,notary-server,chartmuseum

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
vRealize Automation 7.x での Internet Information Services (IIS) アプリケーション プールのリサイクルの無効化 (76333)

KB
•
适用于 vRA 8.0.0 HA 环境的修补程序解决了阻止某些服务在数据库故障切换事件后恢复的问题 (76222)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware PKS 1.x

Take Our Survey

Support Assistant