LI79664: ADDING GATEWAY SERVER TO GATEWAY SERVICE IN CMC FAILS WITH PROXYERROR

apiconnect-2.7.28
5.0.8.0-APIConnect-Portal-Debian7-20170908-0855
5.0.8.0-APIConnect-Portal-Ubuntu16-20170908-0855.ova
APIConnect_Management_5.0.8.0_20170905-1133_a7fe4cd1d442_c04798a.ova
APIConnect_Management_5.0.8.0_20170905-1133_a7fe4cd1d442_c04798a.vcrypt2
apiconnect-2.7.26
microgateway-1.6.3
5.0.8.0-APIConnect-Essentials-Portal-Ubuntu16-20170908-0855.ova

APAR status

• Closed as program error.

Error description

• When adding a gateway server to a gateway service in CMC UI, if
  the addition process takes longer than 10 minutes, the user may
  receive an error saying "502 Proxy Error. The proxy server
  received an invalid response from an upstream server. The proxy
  server could not handle the request".  The addition operation
  may still proceed in the background, but the user of the CMC UI
  may only see the gateway server as standalone or unused in
  CREATED status and may incorrectly try to add it again to the
  gateway service instead of waiting for the earlier addition to
  complete.
  

Local fix

• Ignore the error that was shown in CMC UI.  Run 'debug tail file
  /var/log/cmc.out' from the management server's CLI to observe
  the progress of the addition of the gateway server. Wait for the
  gateway server to become ACTIVE in the CMC UI.
  

Problem summary

• When adding a gateway server to a gateway service in CMC UI, if
  the addition process takes longer than 10 minutes, the user may
  receive an error saying "502 Proxy Error. The proxy server
  received an invalid response from an upstream server. The proxy
  server could not handle the request".  The addition operation
  may still proceed in the background, but the user of the CMC UI
  may only see the gateway server as standalone or unused in
  CREATED status and may incorrectly try to add it again to the
  gateway service instead of waiting for the earlier addition to
  complete.
  
  The issue is caused by the gateway addition process making a
  synchronous HTTP request and taking longer than the 10-minute
  timeout on the proxy running on the management server.
  
  The solution for this issue moves the process of adding a
  gateway server to a gateway service into a non-blocking
  background thread. The user receives back control of the CMC UI
  after initiating the addition process. The gateway server's
  status is changed to JOINING to indicate that the addition
  process is in progress. The user may simply wait or may choose
  to run 'debug tail file /var/log/cmc.out' from the management
  server's CLI to observe the progress of the addition of the
  gateway server. For troubleshooting, look for messages
  containing text "GATEWAY ADDITION" in the '/var/log/cmc.out*'
  logs and any logging messages with the same "[T-NNN]" thread
  identifier. Once the addition process has completed, the system
  changes the gateway server's status to ACTIVE. The CMC UI may
  need to be refreshed after several minutes of inactivity to
  reflect the new status.
  
  If the addition of the gateway server fails for some reason, the
  system changes the gateway server's status to ERRORED. Only one
  gateway server may be added at a given time to prevent any
  conflicts. If the user wants to interrupt the addition process
  or if an error occurred during the addition process and the user
  wants to retry, the user can delete the gateway server (after
  about a 10-minute wait period to allow addition process to make
  some initial progress). During the deletion process, the system
  will attempt to delete on the DataPower server the domain
  associated with this gateway service, but a manual cleanup of
  the domain may be required sometimes (although is less likely to
  be necessary than prior to this fix)
  

Problem conclusion

• The fix for this issue is included in API Connect v5.0.8.0.
  

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

  API CONNECT ENT

• Fixed component ID

  5725Z2201

Applicable component levels

• R507 PSY

     UP