https://github.com/openshift/release/pull/2042

On 11/13/18 6:17 AM, devops036 devops036 wrote:
When installing okd 3.11 with the recently made available CentOS PaaS repo (http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/), I can't activate the logging module (openshift_logging_install_logging=true).

When investigating, the playbooks are searching for docker.io/openshift/origin-logging-elasticsearch5:v3.11 <http://docker.io/openshift/origin-logging-elasticsearch5:v3.11>, docker.io/openshift/origin-logging-kibana5:v3.11 <http://docker.io/openshift/origin-logging-kibana5:v3.11> and docker.io/openshift/origin-logging-curator5:v3.11 <http://docker.io/openshift/origin-logging-curator5:v3.11> container images. However, these images don't exist with the v3.11 tag.

To get the logging module installed, I have to remove the 5 at the end of each 
container image as follows:
openshift_logging_elasticsearch_image=docker.io/openshift/origin-logging-elasticsearch:v3.11
 <http://docker.io/openshift/origin-logging-elasticsearch:v3.11>
openshift_logging_kibana_image=docker.io/openshift/origin-logging-kibana:v3.11 
<http://docker.io/openshift/origin-logging-kibana:v3.11>
openshift_logging_curator_image=docker.io/openshift/origin-logging-curator:v3.11 
<http://docker.io/openshift/origin-logging-curator:v3.11>

Is it normal?

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


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

Reply via email to