Operational Defect Database
BugZero updated this defect 45 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 97337
How to manually update the airgap FQDN in TCA-CP database for TCA 2.3
Last update date:
4/4/2024
Affected products:
Telco Cloud Automation
Affected releases:
2.3
Fixed releases:
No fixed releases provided.
Description:
Symptoms
Trying to open terminal for a workload cluster from TCA UI fails abruptly due to associated pods trying to pull images from public jfrog repo in an airgapped env.Running diagnosis tests for a mgmt/workload cluster from TCA UI fails due to associated pods trying to pull images from public jfrog repo in an airgapped env.
Purpose
This document contains the procedure to update the database manually with the airgapFqdn in the ApplianceConfig table on TCA-CP (where workload cluster is configured).
Cause
Airgap Server FQDN is missing for clusters in the database of TCA Control plane node. This could happen after cluster certs are renewed using manual/automated work arounds provided.
Impact / Risks
Impacts Telco Cloud Automation 2.3
Resolution
Update Airgap FQDN for management cluster in TCA-CP DB. SSH into the TCA-CP appliance as admin.Connect to the postgress database using the following command: connect-to-postgres Verify that the record exists SELECT * from "ApplianceConfig" WHERE val->'config'->>'clusterName'='<cluster_name>'; Check the entries for the cluster, you will find Airgap entry is missing. Run the following command on the postgress to update the airgap fqdn for the cluster(s) UPDATE "ApplianceConfig" SET "val" = jsonb_set("val", '{config,airgapFqdn}', '"<airgap_fqdn>"') WHERE "val"->'config'->>'clusterName'='<cluster_name>'; Sample:Below is the example of the DB entry before and after the changes:Before adding airgap FQDN:{ "_id" : ObjectId("63ee0fced91947fc27f9b96d"), "config" : { "url" : "[https://10.117.27.123:6443|https://10.117.27.123:6443/]", "clusterName" : "ci-pip-5g-ccdm-01", , "UUID" : "a7640b6b-f3b5-4a6d-98f3-b19e16c6dbe2", "version" : "1.22", "kubeSystemUUID" : "9f24e947-61bc-46c3-874f-2a430554befb", "clusterType" : "WORKLOAD" } , "section" : "kubernetes", "enterprise" : "HybridityAdmin", "organization" : "HybridityAdmin", "lastUpdated" : ISODate("2024-03-20T07:59:24.211Z"),"lastUpdateEnterprise" : "HybridityAdmin", "lastUpdateOrganization" : "HybridityAdmin", "lastUpdateUser" : "HybridityAdmin", "creationDate" : ISODate("2023-02-16T11:13:18.802Z"), "creationEnterprise" : "HybridityAdmin", "creationOrganization" : "HybridityAdmin", "creationUser" : "HybridityAdmin", "isDeleted" : false } After updating the changes in DB:{ "_id" : ObjectId("63ee0fced91947fc27f9b96d"), "config" : { "url" : "[https://10.117.27.123:6443|https://10.117.27.123:6443/]", "clusterName" : "ci-pip-5g-ccdm-01","kubeconfig" : "", "UUID" : "a7640b6b-f3b5-4a6d-98f3-b19e16c6dbe2", "version" : "1.22", "kubeSystemUUID" : "9f24e947-61bc-46c3-874f-2a430554befb", "clusterType" : "WORKLOAD", "airgapFqdn" : "[xyz02111.nvi-mgmt.vmware.test.com|http://xyz02001.nvi-mgmt.vmware.test.com/]" } , "section" : "kubernetes", "enterprise" : "HybridityAdmin", "organization" : "HybridityAdmin", "lastUpdated" : ISODate("2024-03-20T07:59:24.211Z"), "lastUpdateEnterprise" : "HybridityAdmin", "lastUpdateOrganization" : "HybridityAdmin", "lastUpdateUser" : "HybridityAdmin", "creationDate" : ISODate("2023-02-16T11:13:18.802Z"), "creationEnterprise" : "HybridityAdmin", "creationOrganization" : "HybridityAdmin", "creationUser" : "HybridityAdmin", "isDeleted" : false }
