LI82047: PGBOUNCER CANNOT START DUE TO DNS SERVER ISSUES.

APAR status

• Closed as Vendor Solution.

Error description

• Deployed the management subsystem with v10.0.1.2 OVA
  freshly.
  'apic status' shows missing some pods in output.
  mgmt
  cluster state shows 'pending' state.
  404 not found returns When
  accessing Cloud Manager UI.
  
  pgbouncer log shows DNS lookup
  failed
  2021-03-10 13:58:39.441 UTC [16] WARNING DNS lookup
  failed: mgmt-site1-postgres: result=0
  2021-03-10 13:58:39.441
  UTC [16] LOG S-0x559fe14ea4a0: lur/apicuser@(bad-af):0 closing
  because: server DNS lookup failed (age=0s)
  
  operator log shows
  failed to connect to pgbouncer
  2021-03-11T15:08:14.173Z ERROR
  controller Reconciler error {"reconcilerGroup":
  "management.apiconnect.ibm.com", "reconcilerKind":
  "ManagementCluster", "controller": "managementcluster", "name":
  "mgmt", "namespace": "default", "error": "bouncer connect:
  Unable to establish connection: failed to connect to
  `host=mgmt-site1-postgres-pgbouncer.default.svc user=apicuser
  database=lur`: server error (ERROR: pgbouncer cannot connect to
  server (SQLSTATE 08P01))"}
  

Local fix

Problem summary

• The new pgbouncer microservice which is released as part of
  10.0.1.2-eus have a client DNS mechanism that may not work with
  all upstream DNS servers and can cause DNS resolution problems
  

Problem conclusion

• The solution is to switch back to stable client DNS client
  implementation in pgbouncer container. Fixed in
  10.0.1.2-ifix1-eus
  

Temporary fix

Comments

• The new pgbouncer microservice which is released as part of 10.
  0.1.2-eus have a client DNS mechanism that may not work with
  all upstream DNS servers and can cause DNS resolution problems
  

APAR Information

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

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

Fix information

Applicable component levels