SDDC has errors fetching data and subtasks - No bundles to display under Bundle Management

Products

• VMware SDDC Manager

Issue/Introduction

• The SDDC UI displays multiple red-banner errors:
• Fetching assessment ID failed
• Retrieving available bundles failed
• Retrieving all applicable bundles failed
• Getting Upgradable API call failed
• Failed to retrieve silenced health checks
• It is clear that the lcm service is not running or not running properly

LCM logging (/var/log/vmware/vcf/lcm/lcm-debug.log):

2023-05-21T14:15:17.196+0000 INFO  [vcf_lcm,000000000000000,000] [o.s.b.f.s.DefaultListableBeanFactory,main] Bean 'vcfAnnotationConfiguration' of type [com.vmware.vcf.annotations.common.VcfAnnotationConfiguration$$EnhancerBySpringCGLIB$$f8d1f3] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-05-21T14:15:34.376+0000 INFO  [vcf_lcm,000000000000000,000] [o.a.c.c.StandardContext,main] Tomcat initialized with port(s): 7400 (http)
2023-05-21T14:15:34.376+0000 INFO  [vcf_lcm,000000000000000,000] [o.a.c.h.Http11NioProtocol,main] Initializing ProtocolHandler ["http-nio-127.0.0.1-7400"]
2023-05-21T14:15:34.376+0000 INFO  [vcf_lcm,000000000000000,000] [o.a.c.c.StandardService,main] Starting service [Tomcat]
2023-05-21T14:15:34.376+0000 INFO  [vcf_lcm,000000000000000,000] [o.a.c.c.StandardEngine,main] Starting Servlet engine: [Apache Tomcat/10.1.25]
2023-05-21T14:15:38.924+0000 INFO  [vcf_lcm,000000000000000,000] [o.s.b.d.LoggingFailureAnalysisReporter,main] Application failed to start
2023-05-21T14:15:38.924+0000 ERROR [vcf_lcm,000000000000000,000] [o.a.c.c.StandardService,main] Error starting Tomcat context. Exception: org.springframework.beans.factory.UnsatisfiedDependencyException. Message: Error creating bean with name 'com.vmware.vcf.lcm.primitives.common.security.LcmSecurityService': Unsatisfied dependency expressed through field 'lcmSecurityService'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.vmware.evo.sddc.lcm.adapter.inventory.InventoryClient' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true)}
2023-05-21T14:15:38.924+0000 ERROR [vcf_lcm,000000000000000,000] [o.a.c.c.StandardContext,main] Context [ROOT] startup failed due to previous errors
2023-05-21T14:15:38.658+0000 INFO  [vcf_lcm,000000000000000,000] [o.a.c.c.StandardService,main] Stopping service [Tomcat]
2023-05-21T14:15:38.659+0000 WARN  [vcf_lcm,000000000000000,000] [o.s.b.f.s.DefaultListableBeanFactory,main] Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.vmware.vcf.lcm.primitives.common.security.LcmSecurityService': Unsatisfied dependency expressed through field 'lcmSecurityService'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.vmware.evo.sddc.lcm.adapter.inventory.InventoryClient' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true)}
2023-05-21T14:15:38.659+0000 INFO  [vcf_lcm,000000000000000,000] [o.s.b.a.l.ConditionEvaluationReportLoggingListener,main] Condition evaluation report available (logging level: DEBUG)
2023-05-21T14:15:38.659+0000 ERROR [vcf_lcm,000000000000000,000] [o.s.b.d.LoggingFailureAnalysisReporter,main]
APPLICATION FAILED TO START
Description:
Parameter 7 of constructor in com.vmware.evo.sddc.lcm.primitives.common.security.LcmSecurityService required a bean of type 'com.vmware.evo.sddc.lcm.adapter.inventory.InventoryClient' that could not be found.
The injection point has the following annotations:
- @org.springframework.beans.factory.annotation.Autowired(required=true)
  
  Action:
  
  Consider defining a bean of type 'com.vmware.evo.sddc.lcm.adapter.inventory.InventoryClient' in your configuration.
  
  (END)

 

 

 

Environment

VCF 5.2.x

Cause

The lcm logging suggests that the /opt/vmware/vcf/lcm/lcm-app/conf/application-prod.properties has been altered in some way or it has become corrupted.

LCM service pulls it's config from this file - any deviation from expected state will cause issues with the stability of the lcm service.

 

Resolution

Please contact VCF Support should you encounter any of these symptoms, citing this KB.