NonFatal Error after upgrade

Products

• CA API Gateway

Issue/Introduction

We are in the process of applying CR03 to Layer 7 gateway 10.1. As a POC , it was done on one of DEV environment , however got following Non-Fatal exception :

2023-05-17T14:35:29.306+1000 WARNING 1 com.l7tech.server.util.GatewaySanityChecker: 1010: Upgrade task failed, but will attempt to boot anyway: Unable to load service resources, WSDL resources for Gateway Management services not upgraded.
com.l7tech.server.upgrade.NonfatalUpgradeException: Unable to load service resources, WSDL resources for Gateway Management services not upgraded.
        at com.l7tech.server.upgrade.a.upgrade(Unknown Source)
        at com.l7tech.server.upgrade.Upgrade71to80UpdateGatewayManagementWsdl.upgrade(Unknown Source)
        at com.l7tech.server.util.ae.doInTransactionWithoutResult(Unknown Source)
        at org.springframework.transaction.support.TransactionCallbackWithoutResult.doInTransaction(TransactionCallbackWithoutResult.java:36)
        at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140)
        at com.l7tech.server.util.GatewaySanityChecker.a(Unknown Source)
        at com.l7tech.server.util.GatewaySanityChecker.a(Unknown Source)
        at com.l7tech.server.util.GatewaySanityChecker.afterPropertiesSet(Unknown Source)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.lambda$invokeInitMethods$5(AbstractAutowireCapableBeanFactory.java:1836)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1835)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1782)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:602)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:524)
        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.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:322)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:322)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)

Patch applied : Layer7_API_Gateway_v10.1.00.15141-CR03

I have verified env looks fine after the patch , however as a concern raising with you to get your input for the same.

 

 

 

Environment

Release : 10.1

Cause

There is incomplete upgrade task artifact left in the DB from a previous upgrade.

In this case,

mysql> select * from cluster_properties where propkey like 'upgrade%'\G
*************************** 1. row ***************************
      goid: 0x0000000000000000FFFFFFFFFFF3CAFC
   version: 0
   propkey: upgrade.task.800004
 propvalue: com.l7tech.server.upgrade.Upgrade71to80UpdateGatewayManagementWsdl
properties: NULL
1 row in set (0.00 sec)

So, looks like it's trying to update a wsdl resource, but obviously there is no such thing for current 10.1 CR03 upgarde, because the resource is for upgrading from ssg 7 to 8.

Resolution

The error should not impact the upgrade.

To avoid the exception, delete the out-dated upgrade artifact before upgrade, 

delete from cluster_properties where propkey = 'upgrade.task.800004';

(when delete, it's better not using wildcard, so, select first, and remove the specific upgrade task aftifact(s))