VMware NSX manager upgrade fails: Fatal can't create directory /root/grupa
search cancel

VMware NSX manager upgrade fails: Fatal can't create directory /root/grupa

book

Article ID: 369092

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • You are upgrading VMware NSX.
  • The Edge nodes and hosts have been upgraded.
  • The pre checks for the manager upgrade passed with no errors.
  • A manager node fails with the following error in the upgrade UI:

"<Manager-name>: Unexpected error while upgrading upgrade unit: Download and verify bundle failed with msg: Checking upgrade bundle /var/vmware/ncx/file-store/VMware NSX-unified-appliance-<nsx-version>.nub contents Verifying bundle VMware NSX-unified-appliance-<nsx-version>.bundle with signature VMware-NSX-unified-appliance-<nsx-version> bundle, sig Failed to verify bundle [gpg,homedir", "/root/grupg, verify", "/tmp/tmproeuxtzi/VMware NSX-unified-appliance-<nsx-version> bundle sig /tmp/tmproeuxcizi/VMware NSX-unified-appliance-<nsx-version>.bundle returned 2: bgpg: Fatal can't create directory /root/grupa: No such file or directory'
<Manager-name>: Unexpected error white upgrading upgrade unit: (MPP] Upgrade stopped on this node as upgrade on other node <Manager-name> has falled.
<Manager-name>: Unexpected error while upgrading upgrade unit: [MPP] Cannot upgrade the MP as upgrade of <Manager-name> failed"

Environment

VMware NSX-T Data Center

Cause

There is a typo in the error message received, the partition name should be '/root/.gnupg/', not '/root/grupa'.

The /root/.gnupg directory is missing for that manager, this may occur due to underlying storage issue which impacts the NSX manager.

Resolution

1. login to the failed manager as root

2. Create the '/root/.gnupg/' directory, if not present: 

   mkdir -p /root/.gnupg/
   chmod 700 /root/.gnupg/

3. Import public keys again:

   gpg --homedir /root/.gnupg --import /opt/vmware/nsx-node-api/etc/publickey_530C79E6.asc
   gpg --homedir /root/.gnupg --import /opt/vmware/nsx-node-api/etc/publickey_FDF4DC95.asc

4. Confirm the following now exist on the failed manager:
  Directory: '/root/.gnupg/' 
  File: '/root/.gnupg/trustdb.gpg'
  File: '/root/.gnupg/pubring.kbx'  
  File: '/root/.gnupg/pubring.kbx~'

5. run 'gpg --list-keys --homedir /root/.gnupg/' - it will show 2 keys.