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.
ls -lta /photon-reps/updates/photon-updates/
rm -rf /photon-reps/updates/photon-updates/.repodata/
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.
root@photon-machine [ ~/airgap ]# helm repo rm <repo-name> root@photon-machine [ ~/airgap ]# scripts/bin/run.sh sync
3. Disk is out of space.
dfcommand and find the one that is out of space.
root@photon-machine [ ~/airgap ]# df -h
- 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.
- Power On airgap VM if needed.
- 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.
root@photon-machine [ ~/airgap ]# scripts/bin/run.sh techsupport root@photon-machine [ ~/airgap ]# df -h
root@tca-ag-tmp [ /tmp/support-bundle ]# ls airgap-support-bundle-20220701084921.tar.gz