Description of problem: set openshift_logging_namespace=logging2 in inventory file, the es pod is still deployed to -n logging: logging logging-es-data-master-t4z30nt2-1-sczc4 1/1 Running 0 5m logging2 logging-curator-1-3rssj 0/1 Error 3 5m logging2 logging-fluentd-kgxks 1/1 Running 0 4m logging2 logging-fluentd-qwbfs 1/1 Running 0 4m logging2 logging-kibana-1-lpvgd 2/2 Running 0 5m Version-Release number of selected component (if applicable): openshift-ansible-playbooks-3.6.126.4-1.git.0.d25d828.el7.noarch How reproducible: Always Steps to Reproduce: 1.Deploy logging with the attached inventory file Actual results: es is still deployed to -n logging, not the namespace specified in ${openshift_logging_namespace} Expected results: es should be deployed into -n ${openshift_logging_namespace} Additional info:
Created attachment 1293153 [details] inventory file used for logging deployment to let this bz repro
Setting to 3.6.1 as I dont see this really as a blocker
https://github.com/openshift/openshift-ansible/pull/4656
It's fixed, verified with openshift-ansible-playbooks-3.6.135-1.git.0.5533fe3.el7.noarch all logging stacks can be deployed to namespace other than "logging": # oc project xiazhao Now using project "xiazhao" on server "https://host-8-175-189.host.centralci.eng.rdu2.redhat.com:8443". # oc get po NAME READY STATUS RESTARTS AGE logging-curator-1-lv9q0 1/1 Running 0 2m logging-es-data-master-0q37jjq2-1-ct6s4 1/1 Running 0 2m logging-fluentd-gxdn9 1/1 Running 0 2m logging-fluentd-zq421 1/1 Running 0 2m logging-kibana-1-fsb04 2/2 Running 0 2m
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/RHEA-2017:1716