created an all-in-one (with parameters to configure IBM Cloud storage) ArgoCD application
I confirmed that I am able to login to the cp.icr.io registry using the Entitlement Key that I used to update the global image pull secret:
docker login cp.icr.io --username cp
Password:
Login Succeeded
The global image pull secret (named pull-secret in the openshift-config namespace) is configured as follows:
Registry server address: cp.icr.io
Username: cp
Password: <ENTITLEMENT_KEY_HERE>
I also created a secret in the cp4waiops namespace with the following configuration, which did not solve my issue:
Name: ibm-entitlement-key
Registry server address: cp.icr.io
Username: cp
Password: <ENTITLEMENT_KEY_HERE>
I also reloaded my cluster's nodes after both pull-secret and ibm-entitlement-key secrets existed with the Entitlement Key value, which did not solve my issue.
All ArgoCD apps are Healthy and Synced except for the in-cluster-cp4waiops-aimanager application, which is stuck Progressing and Synced. I noticed all ArgoCD applications' Target Revision is release-3.6 except for the following ArgoCD apps:
argocd-custom
cp-shared
in-cluster-cp4waiops-aimanager
in-cluster-cp4waiops-eventmanager
I confirmed that I specified a Revision of release-3.6 when creating my config/argocd/openshift and config/all-in-one Argo CD apps.
I have repeated these steps a few times and the results are the same.
Hello,
I am configuring IBM Cloud Pak for Watson AIOps (CP4WAIOPS) all-in-one using a custom build and the following pods are stuck in a
Pending
state:oc get pods --field-selector 'status.phase=Pending' -A
Here are my infrastructure and configuration details:
Currently, I have completed the following steps:
I confirmed that I am able to login to the
cp.icr.io
registry using the Entitlement Key that I used to update the global image pull secret:docker login cp.icr.io --username cp
The global image pull secret (named
pull-secret
in theopenshift-config
namespace) is configured as follows:I also created a secret in the
cp4waiops
namespace with the following configuration, which did not solve my issue:I also reloaded my cluster's nodes after both
pull-secret
andibm-entitlement-key
secrets existed with the Entitlement Key value, which did not solve my issue.All ArgoCD apps are
Healthy
andSynced
except for thein-cluster-cp4waiops-aimanager
application, which is stuckProgressing
andSynced
. I noticed all ArgoCD applications'Target Revision
isrelease-3.6
except for the following ArgoCD apps:I confirmed that I specified a
Revision
ofrelease-3.6
when creating myconfig/argocd/openshift
andconfig/all-in-one
Argo CD apps. I have repeated these steps a few times and the results are the same.