On VCF Operations
- the required binaries have been downloaded by using the VCF Download Tool, per the documentation here -
- the Offline Depot type being used is Local Path, and has been configured as per the documentation here -
- the required binaries that were downloaded using the VCF Download Tool have been moved into a directory on the VCF Operations fleet management appliance - example: /data/
- the Fleet Management - Lifecycle - VCF Management - Binary Management page doesn't show the expected installation packages
On the VCF Operations fleet management appliance -
- the log /var/log/vrlcm/vmware-vrlcm.log shows that initially the productVersionCatalog.json is seen in the directory ("true")
YYYY-MM-DDThh:mm:ss.sssZ INFO vrlcm[xxxx] [http-nio-xxxx-exec-x] [c.v.v.l.b.s.u.UnifiedManifestUtility] -- filePath in tar : /PROD/metadata/productVersionCatalog/v1/productVersionCatalog.json
YYYY-MM-DDThh:mm:ss.sssZ INFO vrlcm[xxxx] [http-nio-xxxx-exec-x] [c.v.v.l.b.s.u.UnifiedManifestUtility] -- file /data/temp/PROD/metadata/productVersionCatalog/v1/productVersionCatalog.json exists : true
YYYY-MM-DDThh:mm:ss.sssZ INFO vrlcm[xxxx] [http-nio-xxxx-exec-x] [c.v.v.l.c.c.ContentRepositoryController] -- Creating content operation.
- however, shortly after the productVersionCatalog.json is **not** seen in the directory ("false")
INFO vrlcm[YYYY-MM-DDThh:mm:ss.sssZxxxx] [http-nio-xxxx-exec-xx] [c.v.v.l.b.s.u.UnifiedManifestUtility] -- file /data/temp/PROD/metadata/manifest/v1/vcfManifest.json exists : false
VCF 9.0.1.0
The vcfManifest.json and productVersionCatalog.json files are not found where they are expected to be.
The workflow deletes them initially and when the workflow looks for them later - they are not found.
Confirm that the Offline Depot type Local Path required is configured on the VCF Operations UI > Fleet Management > Lifecycle > VCF Management > Depot Configuration page
Copy the vcfManifest.json and productVersionCatalog.json files again from the computer that the VCF Download Tool was run on to the respective path being used on the VCF Operations fleet management appliance.
Example using /data/ -
/data/temp/PROD/metadata/manifest/v1/vcfManifest.json
/data/temp/PROD/metadata/productVersionCatalog/v1/productVersionCatalog.json
On VCF Operations UI, again go to Depot Configuration > Offline Depot, click EDIT DEPOT SETTINGS, and then click OK without making any changes.
The issue is expected to be resolved - the Binary Management tab is now expected to be populated with the expected binaries.