Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • How to fix "image-registry Available: The deployment does not exist..."

    Posted on

    Hi,
    have a OS Cluster that hang with update.

    $ oc get clusterversion
    NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
    version 4.16.14 True True 43h Unable to apply 4.16.15: the cluster operator image-registry is not available

    $ oc get clusteroperator image-registry
    NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
    image-registry 4.16.14 False True True 8d Available: The deployment does not exist...

    oc get co image-registry -o json |jq -r '.status.conditions[]'
    {
    "lastTransitionTime": "2024-10-08T08:47:04Z",
    "message": "Available: The deployment does not exist\nNodeCADaemonAvailable: The daemon set node-ca has available replicas\nImagePrunerAvailable: Pruner CronJob has been created",

    "reason": "DeploymentNotFound",
    "status": "False",
    "type": "Available"
    }
    {
    "lastTransitionTime": "2024-10-08T08:47:04Z",
    "message": "Progressing: Unable to apply resources: unable to sync storage configuration: exactly one storage type should be configured at the same time, got 2: [EmptyDir PVC]\nNodeCADaemonProgressing: The daemon set node-ca is deployed",

    "reason": "Error",
    "status": "True",
    "type": "Progressing"
    }
    {
    "lastTransitionTime": "2024-10-08T08:49:46Z",
    "message": "Degraded: The deployment does not exist",
    "reason": "Unavailable",
    "status": "True",
    "type": "Degraded"

    How to fix this ?
    That the "image-registry " is working and the Update is go to the end

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2025 Red Hat