Using Tridion Sites 9.5.
We got a scaled-up CM servers setup and use a load balancer to distribute the load on CM servers. When content porter is connected with LB URL for importing a package, the import process is often failing with the reason "invalid import package". If the URL of the individual CM instance is used in the content porter, the portering succeeds without any error. Hence there is no issue with the package itself. We don't prefer directly connecting with individual CM instance for security reasons.
It looks like content porter doesn't always maintain "sticky session" with the same CM instance while using the load balancer URL. The package is uploaded on one CM instance and but the sub-sequent processing of the package doesn't always run on the same CM instance which is resulting in "invalid import package".
Any fix for this issue? I see an article in SDL documentation that talks about high availability storage. Can the mentioned solution fix this issue? If so, can you please explain what will then happen on each CM instance? Will the import package be uploaded on each CM instance?