JR65049: WITH PROXY SETTING IN OCP, YOU'LL SEE "503 SERVICE UNAVAILABLE" BETWEEN SERVICE COMMUNICATION

APAR status

• Closed as program error.

Error description

• If the OCP Cluster has a proxy setting, you may see error
  "<urlopen error Tunnel connection failed: 503 Service
  Unavailable" from Ansible log when deploying CP4BA, this is a
  communication issue between services. Because each internal
  service communication also went through the proxy and it is not
  recognized by the proxy.
  
  In general you would add ".svc" to the NO_PROXY list, but in
  this issue, CP4BA Operator is not using the full qualified host
  name with ".svc" suffix which result in this communication
  issue.
  

Local fix

• You can workaround this by adding the problematic service name
  to NO_PROXY list.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * A component can't talk to another component by using its     *
  * service name.                                                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When a cluster has proxy enabled, you may see error          *
  * "<urlopen error Tunnel connection failed: 503 Service        *
  * Unavailable" from Ansible log when deploying CP4BA, this is  *
  * a communication issue between services. Because each         *
  * internal service communication also went through the proxy   *
  * and it is not recognized by the proxy.                       *
  *                                                              *
  * In general you would add ".svc" to the NO_PROXY list, but in *
  * this issue, CP4BA Operator is not using the full qualified   *
  * host name with ".svc" suffix which result in this            *
  * communication                                                *
  * issue.                                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * By adding the problematic service name to NO_PROXY list can  *
  * workaround the issue.                                        *
  ****************************************************************
  

Problem conclusion

• Defect created.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  CLOUD PAK FOR A

• Fixed component ID

  5737I2300

Applicable component levels