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

CP4D 4.8.0 fails if licence service already installed #624

Closed m-g-k closed 5 months ago

m-g-k commented 5 months ago

We had followed the manual Airgap CP4D install docs as far as running this command to install the licence service and scheduler before switching to use the deployer.

CP4D Manual projects Create Docs oc new-project ${PROJECT_LICENSE_SERVICE} We had set ${PROJECT_LICENSE_SERVICE} to be ibm-licensing

CP4D Shared Components Install Docs

cpd-cli manage apply-cluster-components \
--release=${VERSION} \
--license_acceptance=true \
--cert_manager_ns=${PROJECT_CERT_MANAGER} \
--licensing_ns=${PROJECT_LICENSE_SERVICE}
cpd-cli manage apply-scheduler \
--release=${VERSION} \
--license_acceptance=true \
--scheduler_ns=${PROJECT_SCHEDULING_SERVICE}

However this then failed as it seemed to not like the namespace the licence service was deployed into. Talking to Arthur the suggestion was made to add --extra-vars cs_control_project=ibm-licensing to our install command to accept the different namespace and the install was able to continue. This was the full install command we used:

./cp-deploy.sh env apply --accept-all-licenses --air-gapped --skip-mirror-images --extra-vars cs_control_project=ibm-licensing

However, we believe the Deployer should tolerate the licence service already being installed into the namespace suggested by the docs and so this should not fail and the --extra-vars cs_control_project=ibm-licensing should not be necessary in this scenario.