You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
oc get all,cassdc -n cass
NAME READY STATUS RESTARTS AGE
pod/development-dc1-rack1-sts-0 0/2 Init:ImagePullBackOff 0 3m14s
pod/development-dc1-rack2-sts-0 0/2 Init:ImagePullBackOff 0 3m14s
pod/development-dc1-rack3-sts-0 0/2 Init:ErrImagePull 0 3m14s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/development-dc1-additional-seed-service ClusterIP None <none><none> 3m14s
service/development-dc1-all-pods-service ClusterIP None <none> 9042/TCP,8080/TCP,9103/TCP,9000/TCP 3m14s
service/development-dc1-service ClusterIP None <none> 9042/TCP,9142/TCP,8080/TCP,9103/TCP,9000/TCP 3m14s
service/development-seed-service ClusterIP None <none><none> 3m14s
NAME READY AGE
statefulset.apps/development-dc1-rack1-sts 0/1 3m14s
statefulset.apps/development-dc1-rack2-sts 0/1 3m14s
statefulset.apps/development-dc1-rack3-sts 0/1 3m14s
NAME IMAGE REPOSITORY TAGS UPDATED
imagestream.image.openshift.io/cass-config-builder image-registry.openshift-image-registry.svc:5000/cass/cass-config-builder 1.0-ubi7 14 minutes ago
NAME AGE
cassandradatacenter.cassandra.datastax.com/dc1 3m14s
What did you expect to happen?
Pods should load their respective container images and start to run.
How can we reproduce it (as minimally and precisely as possible)?
Part 1: Install Cassandra Operator to openshift-operators namespace.
Log into Openshift 4.12 console, navigate to Operators, then OperatorHub. Search for Cassandra. Select "DataStax Kubernetes Operator for Apache Cassandra". Select Install.
In the Install Operator page, select Installation mode: "All namespaces on the cluster". Click "Install" and wait for the operator to finish installing. When this is done, click "View operator".
Part 2: Create CassandraDataCenter CR
Create namespace "cass"
Apply SecurityContextConstraint (below) with oc apply -f scc.yaml
Link SecurityContextConstraint to default ServiceAccount with oc adm policy add-scc-to-user cassandra-scc system:serviceaccount:cass:default
Log into docker registry for image: docker login registry.connect.redhat.com
Events from oc describe pod/development-dc1-rack1-sts-0 -n cass:
Events:
Type Reason Age From Message---- ------ ---- ---- -------Warning FailedScheduling 20m default-scheduler 0/6 nodes are available: 6 pod has unbound immediate PersistentVolumeClaims. preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling.Normal Scheduled 20m default-scheduler Successfully assigned cass/development-dc1-rack1-sts-0 to cluster6-kswdj-worker-h5p46Normal SuccessfulAttachVolume 20m attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-1b00dd75-d60b-47eb-8a95-ccf3ae0d8d81"Normal AddedInterface 20m multus Add eth0 [172.23.27.7/21] from openshift-sdnWarning Failed 18m (x6 over 20m) kubelet Error: ImagePullBackOffNormal Pulling 18m (x4 over 20m) kubelet Pulling image "datastax/cass-config-builder:1.0-ubi7"Warning Failed 18m (x4 over 20m) kubelet Failed to pull image "datastax/cass-config-builder:1.0-ubi7": rpc error: code = Unknown desc = unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/articles/3399531Warning Failed 18m (x4 over 20m) kubelet Error: ErrImagePullNormal BackOff 7s (x87 over 20m) kubelet Back-off pulling image "datastax/cass-config-builder:1.0-ubi7"
Events say that the image can't be pulled, but there's a Pull Secret with the appropriate credentials, which are linked to the ServiceAccount in the Namespace, and the image can be imported as an ImageStream but not used by the Pods. What am I missing?
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: CASS-19
The text was updated successfully, but these errors were encountered:
What happened?
Pods can't pull images on OCP 4.12:
What did you expect to happen?
Pods should load their respective container images and start to run.
How can we reproduce it (as minimally and precisely as possible)?
Part 1: Install Cassandra Operator to
openshift-operators
namespace.Part 2: Create CassandraDataCenter CR
oc apply -f scc.yaml
oc adm policy add-scc-to-user cassandra-scc system:serviceaccount:cass:default
docker login registry.connect.redhat.com
oc create secret generic pull-secret -n cass --from-file=.dockerconfigjson=/home/travis/docker/config.json --type=kubernetes.io/dockerconfigjson
oc secrets link default pull-secret -n cass --for=pull
cass
Namespace:oc import-image datastax/cass-config-builder:1.0-ubi7 --from=registry.connect.redhat.com/datastax/cass-config-builder:1.0-ubi7 --confirm -n cass
scc.yaml:
CassandraDataCenter CR:
cass-operator version
1.16.0
Kubernetes version
1.25.4
Method of installation
OCP dashboard
Anything else we need to know?
Events from
oc describe pod/development-dc1-rack1-sts-0 -n cass
:Events say that the image can't be pulled, but there's a Pull Secret with the appropriate credentials, which are linked to the ServiceAccount in the Namespace, and the image can be imported as an ImageStream but not used by the Pods. What am I missing?
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: CASS-19
The text was updated successfully, but these errors were encountered: