-
Bug
-
Resolution: Done
-
Major
-
None
-
rhos-18.0.4
-
None
-
False
-
-
False
-
?
-
None
-
-
-
Moderate
It seems that the OctaviaRsyslog pods are not starting because the image is not correct:
~~~
$ oc get pods | grep octavia-rsyslog
octavia-rsyslog-97n57 0/1 ImagePullBackOff 0 3m50s
octavia-rsyslog-ckdvq 0/1 ImagePullBackOff 0 3m50s
octavia-rsyslog-z9hdv 0/1 ImagePullBackOff 0 3m50s
$ oc get pod octavia-rsyslog-97n57 -o yaml
...
containers:
image: registry-proxy.engineering.redhat.com/rh-osbs/rhoso18-openstack-rsyslog:18.0
imagePullPolicy: IfNotPresent
...
containerStatuses:
- image: registry-proxy.engineering.redhat.com/rh-osbs/rhoso18-openstack-rsyslog:18.0
imageID: ""
lastState: {}
name: octavia-rsyslog
ready: false
restartCount: 0
started: false
state:
waiting:
message: Back-off pulling image "registry-proxy.engineering.redhat.com/rh-osbs/rhoso18-openstack-rsyslog:18.0"
reason: ImagePullBackOff
—
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
annotations:
controller-gen.kubebuilder.io/version: v0.11.1
operatorframework.io/installed-alongside-3a116431ca684376: openstack-operators/octavia-operator.v1.0.5
labels:
olm.managed: "true"
operators.coreos.com/octavia-operator.openstack-operators: ""
name: octaviarsyslogs.octavia.openstack.org
...
containerImage:
default: registry-proxy.engineering.redhat.com/rh-osbs/rhoso18-openstack-rsyslog:18.0
description: ContainerImage - Amphora Controller Container Image URL
~~~