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

Host Live Upgrade from NSX-T 2.5.0 to NSX-T 2.5.1 may fail under certain cases (76606)

Last Updated: 12/19/2019Categories: TroubleshootingTotal Views: 8378Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Upgrade will fail with the following message on UI

Unexpected error while upgrading upgrade unit: Install of offline bundle failed on host 5ab65127-234e-4634-98cc-7f28ab2cefab with error : [LiveInstallationError] Error in running ['/etc/init.d/nsx-datapath', 'start', 'upgrade']: Return code: 1 Output: ioctl failed: No such file or directory ioctl failed: No such file or directory start upgrade begin Exception: Traceback (most recent call last): File "/etc/init.d/nsx-datapath", line 1397, in <module> PostLoad() File "/etc/init.d/nsx-datapath", line 1023, in PostLoad shell = True) File "/build/mts/release/bora-13885523/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 676, in __init__ File "/build/mts/release/bora-13885523/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 1228, in _execute_child OSError: [Errno 28] No space left on device It is not safe to continue. Please reboot the host immediately to discard the unfinished update. Please refer to the log file for more details..

- Host nsx-syslog will show following message, not able to connect to manager.

<180>1 2019-12-14T19:10:37.898Z prom-05056a0ad9.nsbucqesystem.test NSX 2110786 - [nsx@6876 comp="nsx-esx" subcomp="nsx-proxy" s2comp="nsx-net" tid="2110789" level="WARN"] StreamConnection[935 Connecting to ssl://20.20.0.14:1234 sid:935] Couldn't connect to 'ssl://20.20.0.14:1234' (error: 335544539-short read)
<180>1 2019-12-14T19:10:37.898Z prom-05056a0ad9.nsbucqesystem.test NSX 2110786 - [nsx@6876 comp="nsx-esx" subcomp="nsx-proxy" s2comp="nsx-net" tid="2110789" level="WARN"] StreamConnection[935 Error to ssl://20.20.0.14:1234 sid:-1] Error 335544539-short read
<180>1 2019-12-14T19:10:37.898Z prom-05056a0ad9.nsbucqesystem.test NSX 2110786 - [nsx@6876 comp="nsx-esx" subcomp="nsx-proxy" s2comp="nsx-rpc" tid="2110789" level="WARN"] RpcConnection[935 Connecting to ssl://20.20.0.14:1234] Couldn't connect to ssl://20.20.0.14:1234 (error: 335544539-short read
<180>1 2019-12-14T19:10:37.898Z prom-05056a0ad9.nsbucqesystem.test NSX 2110786 - [nsx@6876 comp="nsx-esx" subcomp="nsx-proxy" s2comp="nsx-rpc" tid="2110789" level="WARN"] RpcTransport[0] Unable to connect to ssl://20.20.0.14:1234: 335544539-short rea

Cause

The upgrade fails because of a certificate mismatch between NSX Manager and the host. Host certificate and host private keys are not updated properly

Impact / Risks

Host Upgrade from NSX-T 2.5.0 to NSX-T 2.5.1 may fail.

Resolution

This is known issue and is planned to be fixed in future release.

Workaround

Follow the steps below to recover the failed host

1. Manually migrate the VMs residing on the impacted host to a good host
2. Reboot the impacted host after all the VMs are moved out.
3. Exit host from Transport Node maintenance mode  using TN API / UI. Use the API below to perform the operation

Note: This is not the same as exiting host from ESX maintenance mode

POST https://<nsx-mgr>/api/v1/transport-nodes/<<Transport Node UUID>>/?action=exit_maintenance_mode

4. Push the host certificate to the NSX Manager node.

A. Obtain the NSX Manager thumbprint by logging into one of the MP nodes and execute the command below

NSX-MANAGER:> get certificate api thumbprint

B. Once the thumbprint of the NSX manager is obtained, perform the host certificate push operation from the host using the command below

host-1# nsxcli -c push host-certificate <NSX Manager-IP/hostname> username admin thumbprint <thumbprint> password <NSX Manager password>

Example:
[host-1]# nsxcli -c push host-certificate 20.20.0.12 username admin thumbprint 53537ebe011198dea035837c7c75a3cd66b08743d12278bd2f2643862b74fc65 password ABCD!!
Host certificate was pushed to management plane successfully

5. Retry the host upgrade after successfully pushing the host certificate to the NSX Manager

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
コンピューティング ポリシーは、関連付け可能なエンティティ タイプが設定されたカテゴリがある場合にのみ、ユーザー インターフェイスから作成できる (76576)

KB
•
vRealize Automation 仮想アプライアンスとは異なるドメインの Kerberos の設定 (76634)

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 NSX-T Data Center 2.5.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant