Thanks a lot Oleg
Is there a way track the PR ?

--
Noua Toukourou
Infrastructure and architecture engineer
System Administrator

UNIVERSITÉ DU LUXEMBOURG

LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDECINE
Campus Belval | House of Biomedicine II
6, avenue du Swing
L-4367 Belvaux
T +352 46 66 44 9638<tel:+352%2046%2066%2044%209638>
F +352 46 66 44 39638<tel:+352%2046%2066%2044%2039638>
noua.toukou...@uni.lu<mailto:noua.toukou...@uni.lu>
https://lcsb.uni.lu<mailto:noua.toukou...@uni.lu>

If ‘Plan A’ didn’t work, the alphabet has 25 more letters! Stay cool.
________________________________
De : Oleg Bulatov <obula...@redhat.com>
Envoyé : Wednesday, November 4, 2020 8:41:42 PM
À : Noua TOUKOUROU <noua.toukou...@uni.lu>
Cc : users-boun...@lists.openshift.redhat.com 
<users-boun...@lists.openshift.redhat.com>; users@lists.openshift.redhat.com 
<users@lists.openshift.redhat.com>
Objet : Re: Image Registry fails when Swift not available on Openstack

You are right about BZ. I created a PR to backport its fix to 4.5.z.

While it's not merged, you can try to create a registry config manually:

~~~
apiVersion: imageregistry.operator.openshift.io/v1
kind: Config
metadata:
  name: cluster
spec:
  httpSecret: 
9a41816505dde21fa72a8d1d79fe3758be6046e4e5a9cebe81f4969a0227bb27b53f946eda18ac5fe37adf8d443c90df16b6300675dd04dd4dbc6844bdf0a49a
  managementState: Managed
  logging: 2
  replicas: 2
  rolloutStrategy: RollingUpdate
~~~

(You can generate your own httpSecret.)

Oleg

On Wed, Nov 04, 2020 at 01:43:49PM +0000, Noua TOUKOUROU wrote:
> I also found this : https://bugzilla.redhat.com/show_bug.cgi?id=1846263
>
> ________________________________
> From: users-boun...@lists.openshift.redhat.com 
> <users-boun...@lists.openshift.redhat.com>
> Sent: Wednesday, November 4, 2020 2:35:10 PM
> To: Oleg Bulatov
> Cc: users@lists.openshift.redhat.com
> Subject: {Possibly Forged} Re: Image Registry fails when Swift not available 
> on Openstack
>
>
> the logs is full of this:
>
>
> bootstrap.go:47] generating registry custom resource
> E1104 13:25:42.762275      14 controllerimagepruner.go:313] (image pruner) 
> unable to sync: unable to apply objects: failed to create object 
> *v1beta1.CronJob, Namespace=openshift-image-registry, Name=image-pruner: 
> config.imageregistry.operator.openshift.io "cluster" not found, requeuing
> unable to sync: Get http://192.168.20.119:80/swift/v1/: dial tcp 
> 192.168.20.119:80: i/o timeout, requeuing
> I1104 13:26:12.827091      14 bootstrap.go:47] generating registry custom 
> resource
> I1104 13:26:26.924042      14 caconfig.go:75] unable to get the service name 
> to add service-ca.crt
> E1104 13:26:26.924439      14 imageregistrycertificates.go:94] 
> ImageRegistryCertificatesController: unable to sync: 
> config.imageregistry.operator.openshift.io "cluster" not found, requeuing
>
> FYI, I don't have swift enabled on the openstack platform.
>
>
>
> ________________________________
> From: Oleg Bulatov <obula...@redhat.com>
> Sent: Wednesday, November 4, 2020 1:24:06 PM
> To: Noua TOUKOUROU
> Cc: users@lists.openshift.redhat.com
> Subject: Re: Image Registry fails when Swift not available on Openstack
>
> On Wed, Nov 04, 2020 at 10:31:14AM +0000, Noua TOUKOUROU wrote:
> > Hi Oleg,
> >
> > Thanks for your reply.
> >
> > When I tried to list all the cluster operators with the "oc" command line, 
> > I can see all the operators and their status. But the image-registry line 
> > is blank (no status)
> >
> > Also from the gui console I can see that is in unknown status "failed to 
> > initialize the cluster: Cluster operator image-registry is still updating". 
> > I checked all the pods are there.
>
> The operator doesn't work properly. Let's check the operator logs first.
> You can get them using
>
> oc -n openshift-image-registry logs deploy/cluster-image-registry-operator
>
> Do you have any errors there?
>
> [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1889663
>
> Oleg
>

_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to