LI83242: CONSUMER CATALOG PODS FAILING IN FRESH CONFIGURATION WITH ERROR "ADDRESS FAMILY NOT SUPPORTED BY PROTOCOL"

APAR status

• Closed as program error.

Error description

• When trying to complete fresh configuration, the installation is
  getting stuck in Pending status.
  
  Error message is showed as ADDRESS FAMILY NOT SUPPORTED BY
  PROTOCOL and Consumer Catalog POD's are in CrashLoopBackOff
  Status Pointing to socket() [::]:3021.
  
  This issue prevents to complete a fresh configuration.
  

Local fix

• A workaround for the customer would be to force delete the pod,
  and on restart attempt to remove the line:
  
  listen [::]:3021 ssl;
  
  within /tmp/nginx.conf before the pod crashes. This resolve the
  problem as long as the pod remains running.
  

Problem summary

• Environments which have ipv6 explicitly disabled will experience
  startup issues with the Consumer Catalog pod.
  

Problem conclusion

• Fixed in the next release of API Connect v10.0.8.1
  

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