Failed CWPS Upgrade

Products

• Cloud Workload Protection for Storage

Issue/Introduction

 

During an upgrade from CWPS 2.0.1 to 2.0.2 the upgrade fails with the following errors.

 

2023-03-07 18:21:56,529 [main] ERROR ServiceHost:29 - Exception Stack Trace:
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'adapter': Unsatisfied dependency expressed through field 'scanHandler'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'SPEScanHandler': Unsatisfied dependency expressed through field 'dispositionHandler'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'azureDispositionHandler': Unsatisfied dependency expressed through field 'reporter'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'reporter': Unsatisfied dependency expressed through field 'eventReporterFacade'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'eventReporterFacadeImpl' defined in URL [jar:file:/usr/local/symantec/spe/spe-azure-protection-adapter-service/lib/spe-reporting-fx-2.0.0.318.jar!/com/symantec/spe/reporting/implementations/EventReporterFacadeImpl.class]: Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'rabbitMqViolationEventReporter' defined in class path resource [servicehost-context.xml]: Invocation of init method failed; nested exception is com.symantec.spe.messagequeue.client.exceptions.MessageQueueException: Publisher initialization failed, check if message queue configuration is valid.
        at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.resolveFieldValue(AutowiredAnnotationBeanPostProcessor.java:659)
        at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:639)
        at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:119)
        at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessProperties(AutowiredAnnotationBeanPostProcessor.java:399)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1431)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:619)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542)
        at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335)
        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:953)
        at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583)
        at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:144)
        at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:85)
        at com.symantec.spe.servicehost.ServiceHost.init(ServiceHost.java:21)
        at com.symantec.spe.servicehost.SelfHostApplication.run(SelfHostApplication.java:81)
        at com.symantec.spe.servicehost.SelfHostApplication.main(SelfHostApplication.java:62)
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'SPEScanHandler': Unsatisfied dependency expressed through field 'dispositionHandler'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'azureDispositionHandler': Unsatisfied dependency expressed through field 'reporter'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'reporter': Unsatisfied dependency expressed through field 'eventReporterFacade'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'eventReporterFacadeImpl' defined in URL [jar:file:/usr/local/symantec/spe/spe-azure-protection-adapter-service/lib/spe-reporting-fx-2.0.0.318.jar!/com/symantec/spe/reporting/implementations/EventReporterFacadeImpl.class]: Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'rabbitMqViolationEventReporter' defined in class path resource [servicehost-context.xml]: Invocation of init method failed; nested exception is com.symantec.spe.messagequeue.client.exceptions.MessageQueueException: Publisher initialization failed, check if message queue configuration is valid.

 

 

Cause

The PU could not ping the CU and this was not allowing the update to continue.   During the upgrade the IP address for the new PU changed and the network rules did not allow for the new PU ip address to communicate with the CU. 

Resolution

The networking rules were changed on the CU to allow for the new PU IP address.  Once configured the problem was resolved.