search

IBM / cloud-pak-deployer

Configuration-based installation of OpenShift and Cloud Pak for Data/Integration/Watson AIOps on various private and public cloud infrastructure providers. Deployment attempts to achieve the end-state defined in the configuration. If something fails along the way, you only need to restart the process to continue the deployment.
https://ibm.github.io/cloud-pak-deployer/
Apache License 2.0
130 stars 65 forks source link

Watson Query instance provisioning fails with CP4D 4.8.0 #602

Closed fketelaars closed 6 months ago

fketelaars commented 6 months ago

Describe the bug As from CP4D 4.8.0 Watson Query instance provisioning fails.

FAILED - RETRYING: Retrieve running Data Virtualization instance (8 retries left).
FAILED - RETRYING: Retrieve running Data Virtualization instance (7 retries left).
FAILED - RETRYING: Retrieve running Data Virtualization instance (6 retries left).
FAILED - RETRYING: Retrieve running Data Virtualization instance (5 retries left).
FAILED - RETRYING: Retrieve running Data Virtualization instance (4 retries left).
FAILED - RETRYING: Retrieve running Data Virtualization instance (3 retries left).
FAILED - RETRYING: Retrieve running Data Virtualization instance (2 retries left).
FAILED - RETRYING: Retrieve running Data Virtualization instance (1 retries left).
fatal: [localhost]: FAILED! => changed=false
  attempts: 60
  cache_control: no-store, no-cache, must-revalidate
  connection: close
  content: |-
    {"limit":20,"offset":0,"service_instances":[],"total_count":0}
  content_length: '63'
  content_type: application/json
  cookies:
    2ac1df5a53d05af1ed3c0e46006c8757: 8f8fb73b0af09d28cd0139ad71ce2433
  cookies_string: 2ac1df5a53d05af1ed3c0e46006c8757=8f8fb73b0af09d28cd0139ad71ce2433
  date: Fri, 15 Dec 2023 00:25:15 GMT
  elapsed: 0
  json:
    limit: 20
    offset: 0
    service_instances: []
    total_count: 0
  msg: OK (63 bytes)
  pragma: no-cache
  redirected: false
  referrer_policy: strict-origin-when-cross-origin
  server: '---'
  set_cookie: 2ac1df5a53d05af1ed3c0e46006c8757=8f8fb73b0af09d28cd0139ad71ce2433; path=/; HttpOnly; Secure; SameSite=Lax
  status: 200
  strict_transport_security: max-age=31536000; includeSubDomains
  url: https://cpd-cpd.apps.657b1058f787d300116c2a8c.cloud.techzone.ibm.com/zen-data/v3/service_instances?addon_type=dv&display_name=watson-query
  x_content_type_options: nosniff
  x_frame_options: SAMEORIGIN
  x_xss_protection: 1; mode=block

PLAY RECAP *********************************************************************
localhost                  : ok=1540 changed=192  unreachable=0    failed=1    skipped=1105 rescued=0    ignored=0

Most-likely this is because of the introduction of a new property: namespace.