Bug #112862 Image pull error
Submitted: 27 Oct 2023 13:56 Modified: 31 Oct 2023 20:07
Reporter: Jose Gonzalez Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Docker Image Severity:S3 (Non-critical)
Version: OS:Ubuntu
Assigned to: CPU Architecture:x86

[27 Oct 2023 13:56] Jose Gonzalez
Description:
After creating the CRD & RBAC with the "trunk" tag the mysql-operator is created successful. 

But after creating the InnoDBCluster with Kubectl, the images cannot be pulled for the clusters.

Failed to pull image "container-registry.oracle.com/mysql/community-server:8.0.35": rpc error: code = NotFound desc = failed to pull and unpack image "container-registry.oracle.com/mysql/community-server:8.0.35": failed to resolve reference "container-registry.oracle.com/mysql/community-server:8.0.35": container-registry.oracle.com/mysql/community-server:8.0.35: not found

Similar behavior with other TAGs and even with the HELM procedure from the documentation.

What can I do?

How to repeat:

Install CRD
 kubectl apply -f https://raw.githubusercontent.com/mysql/mysql-operator/trunk/deploy/deploy-crds.yaml

and RBAC
kubectl apply -f https://raw.githubusercontent.com/mysql/mysql-operator/trunk/deploy/deploy-operator.yaml

create the secret
kubectl create secret generic mypwds \
        --from-literal=rootUser=root \
        --from-literal=rootHost=% \
        --from-literal=rootPassword="sakila"

and apply the basic InnoDB cluster YAML:
apiVersion: mysql.oracle.com/v2
kind: InnoDBCluster
metadata:
  name: mycluster
spec:
  secretName: mypwds
  tlsUseSelfSigned: true
  instances: 3
  router:
    instances: 1

kubectl apply -f mycluster.yaml

Suggested fix:
is this address correct for the repository? 

container-registry.oracle.com/mysql/community-server:8.0.35
[31 Oct 2023 0:37] MySQL Verification Team
Hi,

Thank you for your report. URL is good but looks like .35 is not yet uploaded
[31 Oct 2023 20:07] Balasubramanian Kandasamy
Thanks for the bug report. The images were not visible even after the publish due to a glitch in the OCR publishing tool. We have published the Server 8.0.35 images to OCR now.