Description of problem: free-int cluster, logging-fluentd image version is v3.10.15, it should be v3.11.0 image: registry.reg-aws.openshift.com:443/openshift3/logging-fluentd:v3.10.15 other component version is v3.11.0-0.10.0 for example: registry.reg-aws.openshift.com:443/openshift3/ose-logging-curator5:v3.11.0-0.10.0 Version-Release number of selected component (if applicable): OpenShift Master:v3.11.0-0.10.0 Kubernetes Master:v1.11.0+d4cacc0 OpenShift Web Console:v3.11.0-0.10.0 logging version: v3.11.0-0.10.0 How reproducible: Always Steps to Reproduce: 1. Check logging component images version 2. 3. Actual results: logging-fluentd image version is v3.10.15 Expected results: logging-fluentd image version should be v3.11.0 Additional info:
Do we need a special provision here or move logging to the default namespace for new deployments of 'openshift-logging' ?
@liggitt seems like your name in this area of code. Can you provide some guidance?
system-priority level pods are allowed in kube-system and openshift-... namespaces only
Modifying this bug to reflect the need of a priority class for scheduling. The original fact the version was wrong I'm certain was related to the deployment timing out. Per #c5, fluent is unable to be scheduled because this is an upgrade where the logging stack still lives in a namespace that is not 'openshift-'. At the recommendation of D.Carr, logging needs a priority class that is below system-priority level: * reason 1 - the restriction for priority class you are hitting is specific to cluster critical * reason 2 - fluentd should be second tier to other cluster components We should create a priority class for cluster-logging. We need this class regardless but is a stop gap until we can migrate deployments to 'openshift-logging' in the 4.0 uprades. Example from avesh: apiVersion: scheduling.k8s.io/v1beta1 kind: PriorityClass metadata: name: high-priority value: 100000 globalDefault: false description: "This priority class for high priority Applications" ref: https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/
https://github.com/openshift/openshift-ansible/pull/9686
Move the verified. The logging applications in logging namespace can be upgrade to v3.11. It is using priorityClassName: cluster-logging. $ oc get ds -o yaml |grep priorityClassName priorityClassName: cluster-logging
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:2652