If you encounter problems when setting up the airgap server, you can use a troubleshooting topic to understand and solve the problem, if there is a workaround.

1. Seeing issue with /path/to/repo/.repodata/ exists

This issue occurs in the build metadata of the Photon repository after all packages are synched to local. The command createrepo verifies if there is a temp folder named .repodata under the repo folder. If a .repodata folder is found, the createrepo command considers that another createrepo session is running and will exit. If you encounter this error, remove the folder .repodata and all its contents and retry the repo sync operation.

1. Check the log file. Generally, in ansible.log or upgrade_repo.log if this issue occurs during a repo upgrade.

2. Check the folder that reports the errors. For example, if the error occurs in the /photon-reps/updates/photon-updates/.repodata/ folder, list the items in its parent folder. For example,
ls -lta /photon-reps/updates/photon-updates/
3. Remove the existing .repodata folder and all its content.
rm -rf /photon-reps/updates/photon-updates/.repodata/
4. Rerun the failed set up/upgrade process.
root@photon-machine [ ~/airgap ]# scripts/bin/run.sh setup
root@photon-machine [ ~/airgap ]# scripts/bin/run.sh sync

2. Repository name already exists when upgrading Helm charts.

This issue is fixed in the current release but may be seen in older release scripts when you update Helm charts. To fix this issue, perform the following steps:
root@photon-machine [ ~/airgap ]# helm repo rm <repo-name>
root@photon-machine [ ~/airgap ]# scripts/bin/run.sh sync

3. Disk is out of space.

This solution is only applicable when multiple disks are assigned to the airgap VM. Check the disk usage using the df command and find the one that is out of space.
root@photon-machine [ ~/airgap ]# df -h
  1. From the vCenter Server user interface, click the airgap VM Edit Settings and resize the target disk. If the disk size is dimmed, it is likely that the VM has snapshots. You must power off the VM and then delete all the snapshots before you can expand the disks.
  2. Power On airgap VM if needed.
  3. Run resize playbook and check the disk usage.
root@photon-machine [ ~/airgap ]# scripts/bin/run.sh resize
root@photon-machine [ ~/airgap ]# df -h

4. Generate Airgap Server tech support bundle.

If you require assistance from VMware engineering, generate a tech support bundle and attach it with the problem description.
root@photon-machine [ ~/airgap ]# scripts/bin/run.sh techsupport
root@photon-machine [ ~/airgap ]# df -h
The generated support bundle tar ball is located at /tmp/support-bundle folder to copy out. For example:
root@tca-ag-tmp [ /tmp/support-bundle ]# ls