SDDC manager is unable to reach the depot for bundles: Retrieving available bundles failed
search cancel

SDDC manager is unable to reach the depot for bundles: Retrieving available bundles failed

book

Article ID: 369142

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

Accessing Bundle Management in the UI gives errors similar to:

Retrieving available bundles failed. Could not reach the server, possible reasons could be network connectivity issue or server going down
Retrieving all available bundles failed. Could not reach the server, possible reasons could be network connectivity issue or server going down

Similar errors are seen in /var/log/vmware/vcf/lcm/lcm.log:

Error starting Tomcat context. Exception: org.springframework.beans.factory.UnsatisfiedDependencyException. Message: Error creating bean with name 'appConfig': Unsatisfied dependency expressed through field 'lcmSecurityService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'lcmSecurityService' defined in URL [jar:file:/opt/vmware/vcf/lcm/lcm-app/lib/lcm-vmware-primitive-common-4.5.1-vcf4510chpRELEASE.jar!/com/vmware/evo/sddc/lcm/primitive/common/security/LcmSecurityService.class]: Unsatisfied dependency expressed through constructor parameter 8; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.vmware.evo.sddc.lcm.adapter.inventory.impl.InventoryClientImpl': Unsatisfied dependency expressed through field 'versionAliasFileService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'versionAliasFileService': Invocation of init method failed; nested exception is com.fasterxml.jackson.dataformat.yaml.snakeyaml.error.MarkedYAMLException: while parsing a block mapping
 in 'reader', line 1, column 1:
    allowedBaseVersionsForAliasing:
    ^
expected <block end>, but found '<block mapping start>'
 in 'reader', line 77, column 2:
     LCM:
     ^

 at [Source: (File); line: 77, column: 2]

Environment

VMware Cloud Foundation 4.x
VMware Cloud Foundation 5.x

Cause

This issue is caused by invalid formatting in the file /opt/vmware/vcf/lcm/lcm-app/conf/VersionAlias.yml

Resolution

Make sure to backup the VersionAlias.yml file before editing.

  • In order to resolve the issue, fix the invalid formatting in versionalias.yml.

  • In the example above, the error was caused by the spacing on line 77

  • YAML formatting is sensitive to line indentation.

Additional Information