SDDC Manager Upgrade in VCF 5.1.1 fails on "SDDC Manager Deployment Drift stage"
Article ID: 327212
Updated On:
Products
Issue/Introduction
Symptoms:
The follow error is observed in the SDDC UI.
A similar error is observed in the sddcmanager_migration_app_upgrade.log (Path to log is present in SDDC UI error)
2024-03-28T13:22:21.241+0000 ERROR [vcf_migration,0000000000000000,0000] [c.v.e.s.m.s.s.ExportDataService,pool-4-thread-4] Error while fetching credentials data
org.springframework.web.client.HttpServerErrorException$GatewayTimeout: 504 Gateway Time-out: "<html><EOL><EOL><head><title>504 Gateway Time-out</title></head><EOL><EOL><body><EOL><EOL><center><h1>504 Gateway Time-out</h1></center><EOL><EOL><hr><center>nginx</center><EOL><EOL></body><EOL><EOL></html><EOL><EOL>"
at org.springframework.web.client.HttpServerErrorException.create(HttpServerErrorException.java:114)
at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:186)
at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:137)
at org.springframework.web.client.ResponseErrorHandler.handleError(ResponseErrorHandler.java:63)
at org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:915)
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:864)
at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:764)
at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:646)
Environment
VMware Cloud foundation 5.x
VMware Cloud Foundation 5.1.1
Cause
The large number of credentialhistory records causes the credential export API to timeout.
SDDC < 5.1
psql -h localhost -U postgres -d platform -c "select count(*) from credentialhistory;"
Count = 10798
SDDC = 5.1
/usr/pgsql/13/bin/psql -h localhost -U postgres -d platform -c "select count(*) from credentialhistory;"
Count = 10798
Resolution
Engineering is aware of this issue and a permanent fix is planned for inclusion in a future release.
Workaround:
As this issue requires database-level modifications, we recommend you submit a Support Request with Broadcom Support mentioning this KB:327212 for guided assistance in implementing the workaround safely.
Feedback
