AWS autoscaling

[Shane_Harvey]

Hi,

We have AWS autoscaling failure where management is not building new gateways or removing terminated gateways. They are reporting as unhealthy in AWS target group. API failure messages from cme.log below. The cme test is successful and discovers correctly the provisioned gateways.

Management is R81.10 with CME Version:
Build: 991592157
Take: 186

API call failed: show-package. Message: : Runtime error: Could not commit JPA transaction; nested exception is javax.persistence.RollbackException: Transaction rolled back because transaction was set to RollbackOnly.
2022-05-06 14:31:22,831 CME_SERVICE INFO ********** End of the iteration number 50 for gateway instances. Iteration time: 0:00:00.961466 **********
2022-05-06 14:31:22,831 CME_SERVICE INFO
2022-05-06 14:31:52,862 CME_SERVICE INFO ********** Starting loop iteration number 51 for gateway instances **********
2022-05-06 14:31:53,758 CME_SERVICE ERROR Failed to get the provisioned gateway instances because of a Management API failure (show-package).
2022-05-06 14:31:53,762 CME_SERVICE ERROR Error during loop iteration for gateway instances
Error details: Management API failure (show-package)..
2022-05-06 14:31:53,764 CME_SERVICE ERROR Error traceback: Traceback (most recent call last):
cme_exceptions.cme_exceptions.ManagementApiException: Error Code: Management API error

Any help would be appreciated.

Thanks

[Danny]

Because this is a Management API failure which needs to be investigated I suggest to open a Service Request with TAC.

[the_rock]

Agree with @Danny . Its possible this may need R&D involvement, but TAC case would be your best bet.

[Roman_Kats]

Hi

It appears to be known issue that was resolved in Jumbo HFs
You can find more info here:
https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut... 

[Shane_Harvey]

Thanks but I am already running the latest R81.10 GA hotfix take45.

I will log a TAC case.