Oleg,
Problem is no longer present so I don't know if sending you the yamls
will make a difference. Around the time that I had posted my request for
help, I had tried bouncing the image registry by scaling the pod down to 0
and scaling it back up to 1, but that didn't work. But a few hours later,
one of the support people did the same thing and service was restored.
I suspect that the problem was caused by me rebooting the node that was
running the single image registry pod. [Why, you ask, would I do such a
thing? Because I'm working on a demo that is trying to showcase how well
OpenShift addresses node failures]. If the problem recurs again, I'll add
in the details you asked for.
Regards,
Marvin
On Thu, Jun 4, 2020 at 10:18 AM Oleg Bulatov <obula...@redhat.com> wrote:
> Hi Marvin,
>
> On Thu, Jun 04, 2020 at 08:01:57AM -0400, Just Marvin wrote:
> > I went digging around for clues and found this in the image-registry pod
> logs:
> >
> > [zaphod@oc3027208274 exam]$ oc logs image-registry-5c54f5b447-lg4tx
> > p11-kit: couldn't complete writing file:
> > /etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt: Operation not
> > permitted
> > p11-kit: couldn't complete writing file:
> > /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem: Operation not
> > permitted
> > p11-kit: couldn't complete writing file:
> > /etc/pki/ca-trust/extracted/pem/email-ca-bundle.pem: Operation not
> > permitted
> > p11-kit: couldn't complete writing file:
> > /etc/pki/ca-trust/extracted/pem/objsign-ca-bundle.pem: Operation not
> > permitted
> > p11-kit: couldn't complete writing file:
> > /etc/pki/ca-trust/extracted/java/cacerts: Operation not permitted
> > [zaphod@oc3027208274 exam]$
>
> The registry pod cannot add CAs to its trust store.
>
> Can you share yamls of config.imageregistry/cluster and
> image.config/cluster? And also the cluster version. I want to reproduce
> it.
>
> > The image registry operator logs show this:
> >
> > [zaphod@oc3027208274 exam]$ oc logs
> > cluster-image-registry-operator-6f78cddbbc-5qcth -c
> > cluster-image-registry-operator | tail
> > I0604 11:51:20.563865 58 clusteroperator.go:98] event from
> > workqueue successfully processed
> > I0604 11:51:20.564105 58 clusteroperator.go:98] event from
> > workqueue successfully processed
> > I0604 11:51:58.508989 58 clusteroperator.go:98] event from
> > workqueue successfully processed
> > I0604 11:52:11.852526 58 clusteroperator.go:98] event from
> > workqueue successfully processed
> > I0604 11:52:11.863955 58 caconfig.go:123] missing the
> > cloud-provider-config configmap: configmap "cloud-provider-config" not
> > found
> > I0604 11:52:11.870390 58 clusteroperator.go:98] event from
> > workqueue successfully processed
> > I0604 11:52:11.877891 58 controller.go:254] event from workqueue
> > successfully processed
> > I0604 11:52:11.885976 58 caconfig.go:123] missing the
> > cloud-provider-config configmap: configmap "cloud-provider-config" not
> > found
> > I0604 11:52:11.902534 58 controller.go:254] event from workqueue
> > successfully processed
> > I0604 11:53:12.869816 58 clusteroperator.go:98] event from
> > workqueue successfully processed
> >
> > Any clues as to what this all means, and any suggestions on how I
> > can recover?
>
> That's OK, all messages are informational (the first letter is I), the
> operator reacts on object changes ("events"). The configmap
> cloud-provider-config is not required for the operator, this notice will
> be removed in 4.5.
>
> Oleg
>
>
_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
