That should have been solved by https://github.com/openshift/cluster-image-registry-operator/pull/406
nothing helped me, what am I supposed to do now for getting a working cluster?
thank you
Is it merged? What should I do now, waiting for new release? I can't test installation further until this is not fixed.
It seems to be a storage backend issue for the registry container.
I noticed the openshift version is 4.3, is it possible to install a previous stable one?
Does it mean all other openshift-installer providers are concerned by this bug?
Can you share `oc describe co/image-registry` ?
I finally manged to connect to the cluster:
./oc describe co/image-registry
Name: image-registry
Namespace:
Labels: <none>
Annotations: <none>
API Version: config.openshift.io/v1
Kind: ClusterOperator
Metadata:
Creation Timestamp: 2019-11-07T12:33:15Z
Generation: 1
Resource Version: 10637
Self Link: /apis/config.openshift.io/v1/clusteroperators/image-registry
UID: 28c491ad-7e89-4269-a6e3-8751085e7653
Spec:
Status:
Conditions:
Last Transition Time: 2019-11-07T12:31:52Z
Message: storage backend not configured
Reason: StorageNotConfigured
Status: False
Type: Available
Last Transition Time: 2019-11-07T12:31:52Z
Message: Unable to apply resources: storage backend not configured
Reason: Error
Status: False
Type: Progressing
Last Transition Time: 2019-11-07T12:31:52Z
Message: storage backend not configured
Reason: StorageNotConfigured
Status: True
Type: Degraded
Extension: <nil>
Related Objects:
Group: imageregistry.operator.openshift.io
Name: cluster
Resource: configs
Group:
Name: openshift-image-registry
Resource: namespaces
Events: <none>
-- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet@abes.fr