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
140 stars 69 forks source link

Cognos Analytics instance provisioning fails #327

Closed SaschaFromF closed 1 year ago

SaschaFromF commented 1 year ago

Describe the bug After creation of the CA instance all pods come up, but the status of the CA instance is failed. Cognos requires a content store (here the integrated db2oltp service) and a connection to it. Deployer configures the connection SSL encrypted but leaves the certificate blank - and this seems to be an issue. This is verified with. CP4D 4.6.1 and 4.6.2 on ROKS

To Reproduce Steps to reproduce the behavior: Run the deployer with services db2 and cognos analytics installed, configure db2 instance as cognos metastore.

Expected behavior Db2, Db2 Connection and CA instance will be deployed. Cognos Instance will not be working

Screenshots If applicable, add screenshots to help explain your problem.

Additional context Steps to successfully create the CA instance:

fketelaars commented 1 year ago

Thank you for providing the solution steps. We have observed the failure since CP4D 4.6.1 but so far did not see any solution. I will try it out and fix using the above steps.

fketelaars commented 1 year ago

I have tested the steps and this seems to work. Also, the instance now shows up as "Provisioned", which used to be "Failed" all the time (despite that CA was working ok).

fketelaars commented 1 year ago

I've managed to automate the Db2 connection with a CA certificate. Automation went through fine. This change will be merged with the next PR.

fketelaars commented 1 year ago

Please note that although the above steps worked repetitively with CP4D 4.6.2, in 4.6.3 I'm seeing the same issue as before.