VIC / VCH Shows No Existing Volumes

[KLEPTOROTH]

Summary

VIC & VCH show no volumes, both on the VIC management web ui, or via docker volume ls cli. Containers still function but I'm worried about attempting to redeploy a container if it cannot find the existing volumes.

Environment information

vSphere and vCenter Server version

vCenter Server Appliance 6.7.0.44100, VMware ESXi, 6.7.0, 16316930

VIC version

v1.5.5-21324-50a44954

VCH configuration

    --target=https://CCS-vCenter.crimsoncomputer.lan
    --thumbprint=-removed-
    --name=CCS-VCH-1
    --compute-resource=/CCS/host/CCS/Resources
    --ops-user=screw@crimsoncomputer.lan
    --image-store=ds://CCS-NAS-DS
    --container-name-convention=CCS-{name}
    --volume-store=ds://CCS-NAS-DS/ccs-container-data:ccs-container-vs
    --volume-store=nfs://CCS-NAS.crimsoncomputer.lan/mnt/CCS-NAS/CCS-NAS/ccs-container-data/nfs-datastore:ccs-nfs-container-vs
    --volume-store=ds://CCS-NAS-DS/ccs-container-data:default
    --dns-server=192.168.11.11
    --dns-server=192.168.11.12
    --bridge-network=CCS-VCH-Bridge
    --public-network=House Network

Details

Newly created volumes appear in the web ui and the cli, just no previously existing volumes.

Steps to reproduce

Actual behavior

No volumes listed.

Expected behavior

All previously created volumes in volume stores should be listed.

Logs

logs.zip

See also

Troubleshooting attempted

Rebooted both the VIC and the VCH, tried creating new datastores to see if that would wake it up.

• Searched GitHub for existing issues. (Mention any similar issues under "See also", above.)
• Searched the documentation for relevant troubleshooting guidance.
• Searched for a relevant VMware KB article.

[KLEPTOROTH]

Any ideas here? If there's any additional information I can provide to help figure this issue out, please let me know!