Upgrades to Access 8.2 fail if the deduplication IP has been added as a FQDN entry to the VDD instance

Problem

During an upgrade to Access 8.2, if the /etc/hosts entry for the VDD IP/Fully Qualified Domain Name (FQDN) exists, spoold fails to start and the upgrade will fail.
 

Error Message

engine : /usr/openv/pdde/pdcr/bin/spoold --test
Warning: -1: NetBackup Appliance: CA:Address=va810a-vip1.samgwin.local (Cannot assign requested address).

In the Access upgrade logs, you'll see errors indicating the container couldn't be configured:

2024-04-23T05:01:23.727544-0700 DEBUG (140010168911616) connection.py:429 :  STDERR:
2024-04-23T05:01:23.727709-0700 INFO (140010550372160) vacontainerops.py:92 :  Result of API execution from all nodes {'va810a-01': {'STDOUT': '', 'STDERR': 1003, 'STATUS': False}}
2024-04-23T05:01:23.727784-0700 ERROR (140010550372160) vacontainerops.py:95 :  Failed to configure container on node va810a-01
2024-04-23T05:01:23.727818-0700 INFO (140010550372160) vacontainersha_monitor.py:218 :  Failed to configure container: msdp-engine

Cause

The FQDN for the deduplication service was added to the /etc/hosts entries within the docker container:

​va810a> dedupe show
Parameter                      msdp-engine
=============================  ==============
Catalog_Filesystem             fs2
Virtual_IP                     192.168.10.140  <<<
Secondary_IP                   -
Filesystem                     fs1
Deduplication_Storage_Size_GB  10
WORM_enabled                   False
Hostname                       va810a-01
Server_Status                  ONLINE

va810a-01:/ # docker exec -it msdp-engine cat /etc/hosts
127.0.0.1       localhost
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.16.1.2      va810a-vip1.samgwin.local   <<< internal docker IP, this entry is valid
192.168.10.140 va810a-vip1.samgwin.local    <<< external VDD IP used for communication, this entry should not exist.

If that entry exists, it was added via the management CLISH:
> dedupe fqdn add 192.168.10.140 va810a-vip1.samgwin.local

The address is already in use by another network location, so spoold fails to start and bind to this address.

This behavior is specific to the way spoold operates in Access 8.2 and is not present in Access 8.1.

The virtual IP used for the VDD instance should not be added as a FQDN entry within the docker container.

The FQDN entries added in this manner should be for external hosts, namely NB media and master servers.  By adding these entries to the VDD instance's /etc/hosts, it speeds up the communication by avoiding external DNS/name lookup and using the direct host entries, but if a user adds the VDD IP and FQDN to it's own /etc/hosts file, this has the negative effect of preventing successful spoold startup at 8.2.

Solution

Prior to upgrading, remove this entry from the VDD /etc/hosts using the Access Management CLISH:

va810a> dedupe fqdn remove 192.168.10.140
Access Appliance dedupe INFO V-493-10-5839 Removed FQDN from the deduplication server configuration successfully.