After performing an rsync operation on a regional VMware Telco Cloud Automation (TCA) Airgap server, the build information displayed by agctl show readyz remains unchanged, reflecting the initial build version rather than the updated version.
root@virt4ca1vd191 [ ~ ]# cat /etc/vmware/cap/product.info{"product_name": "TCA AIRGAP APPLIANCE","version": "3.4.0","build_number": "25412912"
agctl show readyz
productName: TCA AIRGAP APPLIANCEproductVersion: 3.1.1productBuild: 23915909buildSynced:3.1.1-12345678 2.3.0-22010335:
TCA 3.4.0.1
Airgap 3.4.0.1
TCP 5.1.1
This behavior is by design. The readyz header is only refreshed automatically during a sync operation (e.g., following an upgrade). An rsync operation does not trigger a header refresh unless the header template file is missing. Consequently, on regional Airgap servers, the readyz build info typically persists from the first time an rsync was performed.
If you need to update the readyz build information to reflect the current state after an rsync, you must manually trigger a header refresh by removing the existing template file.
Log in to the regional Airgap server as a root user.
Remove the header template file to force a regeneration during the next operation.
This command will make changes to your system. Review it carefully before running.
rm -f /photon-reps/readyz/templates/000headerTemplate.yamlTrigger the rsync operation.
Once the rsync is complete, the header will be refreshed, and agctl show readyz will display the updated build information.