Red Hat Bugzilla – Bug 1466657
logging-curator 3.6.126.1 container not found - logging-curator won't start
Last modified: 2018-01-23 12:57:29 EST
Description of problem: Deployed logging with the inventory below on v3.6.126.1. The logging-curator pod fails to start because there is no container with that image. The rest of the logging pods (elasticsearch, fluentd, fluentd-mux and kibana) start ok. Warning Failed kubelet, 172.16.0.7 Failed to pull image "registry.ops.openshift.com/openshift3/logging-curator:v3.6.126.1": rpc error: code = 2 desc = manifest unknown: manifest unknown Version-Release number of selected component (if applicable): 3.6.126.1 How reproducible: Always Steps to Reproduce: 1. Deploy logging with the inventory below Actual results: logging-curator fails to start - container not found Expected results: no error Additional info: [oo_first_master] 172.16.0.8 [oo_first_master:vars] openshift_deployment_type=openshift-enterprise openshift_release=v3.6.0 openshift_logging_install_logging=true openshift_logging_use_ops=false openshift_logging_master_url=https://172.16.0.20:8443 openshift_logging_master_public_url=https://10.12.70.33:8443 openshift_logging_kibana_hostname=kibana.ocp.net openshift_logging_namespace=logging openshift_logging_image_prefix=registry.ops.openshift.com/openshift3/ openshift_logging_image_version=v3.6.126.1 openshift_logging_es_pvc_dynamic=true openshift_logging_es_pvc_size=250Gi openshift_logging_fluentd_use_journal=true openshift_logging_use_mux=true openshift_logging_use_mux_client=true
This image was not being built alongside OCP. I've added it and it should begin being published for all future builds.
Verified on 3.6.133
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0113