Getting 404 error from postman when consuming an api exposed on wso2 apim 3.1.0 after migrating from aws kubernetes to OKE (kubernetes on OCI)

[Godfriend]

Description

Experiencing issues on WSO2 APIM 3.1.0 after migrating from AWS Kubernetes to OCI Kubernetes (OKE). Publisher and Devportal are accessible, displaying exposed APIs and API products. However, attempts to consume these APIs via Postman result in a 404 error.

Note: The apis are configured as a product on the publisher and I can reach the individual api added to the product

Actions taken:

1. Republished APIs but the issue still persists
2. Removed and re-added APIs to products. I was able to start consuming some products after doing this however many products are returning 404 errors when consuming from postman

The error gotten is this
<am:fault xmlns:am="http://wso2.org/apimanager"> <am:code>404</am:code> <am:type>Status report</am:type> <am:message>Not Found</am:message> <am:description>The requested resource is not available.</am:description> </am:fault>

and by the time i checked the wso2 apim-gateway logs, am seeing this warning::
[2023-12-15 11:42:07,582] INFO - LogMediator STATUS = Message dispatched to the main sequence. Invalid URL., RESOURCE = /valiant/user/login, HEALTH CHECK URL = /valiant/user/login

However, if the api for this /user/login is called directly, its working but the one added to /valiant product is returning 404.

Kindly assist on this

Steps to Reproduce

N/A

Affected Component

APIM

Version

3.1.0

Environment Details (with versions)

kubernetes

Relevant Log Output

[2023-12-15 11:42:07,582]  INFO - LogMediator STATUS = Message dispatched to the main sequence. Invalid URL., RESOURCE = /valiant/user/login, HEALTH CHECK URL = /valiant/user/login

Related Issues

No response

Suggested Labels

api-m product