Skip to main content

Log 1 🛫

· 2 min read

Objectives​

  • Get IDZ up and running in client's environment

Accomplishments​

  • Team resolved network errors within the client's environment
  • Resolved pod errors within the clients environment

Work in Progress​

  • The team experienced some difficulty using host names instead of IP addresses due to IT issues on client’s side.
  • The problem stemmed from how the client was provisioning system was configured, which did not allow for the use of fully qualified domain names.
  • The team opened ticket TS015447064. This issue was resolve by changing priority to IPv4 instead of IPv6.
  • The client was having issues related to container management. The team explained using the stop.sh --all command ensures that all containers are stopped. And the client was able to restart pods with out issues.
  • Inconsistencies and errors were observed in the client's environment, particularly regarding certificate errors.
  • The team suspected that these issues were related to the network provisioning for client's systems.

Currently Tracking​

  • The team will work with the client to setup the outbound connectivity to the firewall for accessing IBM DB Cloud DB2.

    • This flight log is being submitted via PR "02/20/2024 Documentation"

Tracking​

Cases open: 0

Cases closed: 2

  • Case TS015447064 - Unable to use the host name instead of IP address in client's Windows VM

  • Case TS015362785