Deployment of packages is failing when using HTTP vs HTTPS on TSPS.
The integration server tries to use tsps-server-name:8080 rather than tsps-load-balancer-name:443
What might cause the issue?

 

- The path to deploy KM in TSPS HA environment is from TSPS to IS directly, not via Load Balancer. Recommendation is to check the logs and the prerequisites for deployment in a non-secure environment  Verify the requirements have been met for using an HTTP configuration by following all steps in the link below:

-From the cmakmpush.log file it seems that the Integration Service is unable to connect to TSPS, based on the message below:

INFO  11/08 13:19:56.686 [Thread-1,IS_KM_PUSH-21260315-9934-42f1-bb34-14bb03000b24] c.b.b.p.d.j.i.ISWaitForISAckJobState Received Ack Message NGPKMPackageDeployAckMessage{MessageID='IS-0-0-1541704802288-86', CorrelationID='TS-0-0-1541704794557-14697', Timestamp=11/08/2018 13:20:02, Destination=NGPDestination{mAgentID=0, mType=TS, mServerID=41}, ReplyTo=NGPDestination{mAgentID=10004, mType=IS, mServerID=41}, Type='PKG_DEPLOY_ACK', Priority=4, IsAckNeeded=false, AcknowledgementType=Positive, DeliveryMode=NonPersistent, Values=CHUNK_ID=54737514-fdd4-47f7-886d-2d84c4be0172,JOB_ID=21260315-9934-42f1-bb34-14bb03000b24,STATUS=FAILURE,STATUS_MSG=DEPLOY not successful.Connect to myserver.mycompany.com:8080 [myserver.mycompany.com:8080 /123.45.678.90] failed: Connection refused: connect}

-Please check the following
1) Check on the port connectivity between the IS server and the TSPS server, make sure ports are open where firewalls are active.
2) Please check whether the IS server can ping TSPS and vice-versa.
3) We see from the log snippet above that the HTTP TSPS port is set to 8080 so that would be the port to check for connectivity.

The Integration Service is using the following url to download packages
http://myserver.mycompany.com:8080/tsws/10.0/api/unifiedadmin/int/package?id=62c62d5a-b289-45e6-ac4e-82b366fb0a9c,JOB_ID=21260315-9934-42f1-bb34-14bb03000b24,PACKAGE_NAME=PALinuxPatch10_7_00_02

Please verify if this port is correct and open to send and receive communication. If you need to change the port, please execute the following command:
tssh properties set server.port.websrv.http {portNo.}

4) Check whether the IS machine browser can access the following TSPS urls. Fill in the {portNo.} in the url
http://myserver.mycompany.com:8080:{portNo.}
http://myserver.mycompany.com:8080:{portNo.}/tsws/10.0/api/unifiedadmin/int/package
If the answer is No to either of the URLs then the root cause of the issue is port connectivity and firewall blockages which need to be alleviated.