-
Bug
-
Resolution: Done
-
Normal
-
None
-
None
-
False
-
None
-
False
-
No
-
-
-
-
-
-
No
-
No
My attempt of re-installing RHODS on the CEE-OSD4 cluster (ID: c4e0dd70-1568-41e2-9411-f4132e45b07f) fails, most likely due to an inconsistency state of the add-on leftover. The cluster in fact was recently upgraded to 4.9.37 OHSS-13037, where previously the add-on used to work.
The logs of the rhods-deployer container in the rhods-operator pod shows the following:
Error from server (AlreadyExists): project.project.openshift.io "redhat-ods-applications" already exists INFO: redhat-ods-applications project already exists. namespace/redhat-ods-applications not labeled Error from server (AlreadyExists): project.project.openshift.io "rhods-notebooks" already exists INFO: rhods-notebooks project already exists. namespace/rhods-notebooks not labeled Error from server (AlreadyExists): project.project.openshift.io "redhat-ods-monitoring" already exists INFO: redhat-ods-monitoring project already exists. namespace/redhat-ods-monitoring not labeled namespace/redhat-ods-monitoring not labeled no addon-managed-odh-pullsecret secret, default SA unchanged Error from server (Forbidden): error when creating "monitoring/jupyterhub-prometheus-token-secrets.yaml": secrets "jupyterhub-prometheus-token-secrets" is forbidden: unable to create new content in namespace redhat-ods-applications because it is being terminated INFO: Jupyterhub scrape token already exist. Error from server (Forbidden): error when creating "jupyterhub/jupyterhub-configmap.yaml": configmaps "jupyterhub-cfg" is forbidden: unable to create new content in namespace redhat-ods-applications because it is being terminated INFO: Jupyterhub ConfigMap already created INFO: Deploying on AWS. Creating CRO for deployment of RDS Instance Error from server (AlreadyExists): project.project.openshift.io "redhat-ods-operator" already exists INFO: redhat-ods-operator project already exists. namespace/redhat-ods-operator not labeled customresourcedefinition.apiextensions.k8s.io/blobstorages.integreatly.org configured customresourcedefinition.apiextensions.k8s.io/postgres.integreatly.org configured customresourcedefinition.apiextensions.k8s.io/postgressnapshots.integreatly.org configured customresourcedefinition.apiextensions.k8s.io/redis.integreatly.org configured customresourcedefinition.apiextensions.k8s.io/redissnapshots.integreatly.org configured clusterrole.rbac.authorization.k8s.io/cloud-resource-operator-cluster-role unchanged clusterrolebinding.rbac.authorization.k8s.io/cloud-resource-operator-cluster-rolebinding unchanged Error from server (Forbidden): error when creating "cloud-resource-operator/rbac/cloud-resource-operator-role.yaml": roles.rbac.authorization.k8s.io "cloud-resource-operator-role" is forbidden: unable to create new content in namespace redhat-ods-applications because it is being terminated Error from server (Forbidden): error when creating "cloud-resource-operator/rbac/cloud-resource-operator-rolebinding.yaml": rolebindings.rbac.authorization.k8s.io "cloud-resource-operator-rolebinding" is forbidden: unable to create new content in namespace redhat-ods-applications because it is being terminated
The pod is left in a crash-backloop state and the add-on is not installed
- account is impacted by
-
-
- Closed
-