Unable to add VxUpdate EEB packages to the repository in the Command Line Shell on Appliance Version 3.2

Problem

Unable to add an EEB Package to the VxUpdate Repository using the Command Line Shell. After uploading the EEB package to the incoming patches share running "Manage > Software > List Downloaded", the result is the package being flagged as invalid and removed.

Error Message

nbapp.Software> List Downloaded 
Validating update 'nbeeb.server_3981837.7_8.2_redhat_x64.sja' ...     failed
- [Error] Update nbeeb.server_3981837.7_8.2_redhat_x64.sja has an invalid name.

Unified Logging Shows:

27/11/19 23:15:54.592 [Info] [230994] cmd:"  find /inst/patch/incoming/ -maxdepth 1 -print"( 0 )
stdout:    /inst/patch/incoming/
stdout:    /inst/patch/incoming/nbeeb_3989728.1_8.2_windows_x64.sja
endcmd:
27/11/19 23:15:54.679 [Error] [230994] cmd:" /bin/rpm -qp /inst/patch/incoming/nbeeb_3989728.1_8.2_windows_x64.sja"( 1 )
stderr:    error: /inst/patch/incoming/nbeeb_3989728.1_8.2_windows_x64.sja: not an rpm package (or package manifest)
endcmd:
27/11/19 23:15:54.767 [Error] [230994] cmd:" /bin/rpm -qp /inst/patch/incoming/nbeeb_3989728.1_8.2_windows_x64.sja"( 1 )
stderr:    error: /inst/patch/incoming/nbeeb_3989728.1_8.2_windows_x64.sja: not an rpm package (or package manifest)
endcmd:
27/11/19 23:15:54.816 [Info] [230994] Validating update 'nbeeb_3989728.1_8.2_windows_x64.sja'
27/11/19 23:15:55.589 [Error] [230994] cmd:" lsof -t /inst/patch/incoming/nbeeb_3989728.1_8.2_windows_x64.sja"( 1 )
endcmd:
27/11/19 23:15:55.608 [Info] [230994] failed
27/11/19 23:15:55.627 [Error] [230994] Update nbeeb_3989728.1_8.2_windows_x64.sja has an invalid name.
27/11/19 23:15:55.666 [Info] [230994] cmd:" rm -rf "/inst/patch/incoming/nbeeb_3989728.1_8.2_windows_x64.sja""( 0 )

Cause

The appliance software is detecting that the package has an invalid name beginning with nbeeb - it is expecting these packages to begin with vxupdate. As a result the package is determined to be invalid and is removed.

Solution

This issue is currently being considered by Veritas Technologies LLC to be addressed in the next major revision of the product.  There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time.  Please note that Veritas Technologies LLC reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability.  Veritas’ plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

The current workaround is to:

1. Upload the package to the incoming patches share as normal but to not run "List Downloaded" - since the file will be detected as invalid it would then be removed
2. Using a NetBackup CLI user execute "nbrepo -a /inst/patch/incoming/<PACKAGE NAME>" to manually add the package to the repository. Replace <PACKAGE_NAME> with the name of the package. Below is an example output:

nbuuser1@nbapp:~> nbrepo -a /inst/patch/incoming/nbeeb_3989728.1_8.2_windows_x64.sja
Adding package to the repository. This may take a few minutes...
Successfully added deployment package ID: 50 to the repository.

After this the package will be available as normal for use by VxUpdate deployment policies and can be managed in "Manage > Software > VxUpdate" as normal, example of ListPkgs below showing the EEB available:

nbapp.VxUpdate> ListPkgs 
ID Type          Version OS             File Name                               
-- ------------- ------- -------------- ----------------------------------------
1  server+client 8.2     windows_x64    vxupdate_nb_8.2_windows_x64.sja         
6  client        8.2     suse_ppc64le   vxupdate_nbclient_8.2_suse_ppc64le.sja  
40 client        8.2     debian_x64     vxupdate_nbclient_8.2_debian_x64.sja    
43 server+client 8.2     solaris_sparc  vxupdate_nb_8.2_solaris_sparc.sja       
50 eeb           8.2     windows_x64    nbeeb_3989728.1_8.2_windows_x64.sja