Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1547972

Summary: Failed to deploy logging with the same node selector for logging components
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED DUPLICATE QA Contact: Anping Li <anli>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.9.0CC: aos-bugs, rmeggins
Target Milestone: ---   
Target Release: 3.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-22 15:12:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ansible log
none
logging dump output none

Description Junqi Zhao 2018-02-22 12:41:39 UTC
Created attachment 1399352 [details]
ansible log

Description of problem:
1 master and 5 nodes, and 4 nodes were labeled with same value purpose=infra,
in this case, set the same value purpose=infraopenshift_logging_elasticsearch_nodeselector and openshift_logging_curator_nodeselector,
but it failed at task  [openshift_logging_curator : Ensure that logging curator has nodes to run on]
TASK [openshift_logging_curator : Ensure that logging curator has nodes to run on] ********************************************************************************************************************************
task path: /usr/share/ansible/openshift-ansible/roles/openshift_logging_curator/tasks/main.yaml:17
fatal: [ec2-35-171-191-40.compute-1.amazonaws.com]: FAILED! => {
    "msg": "The conditional check 'openshift_schedulable_node_labels | lib_utils_oo_has_no_matching_selector(openshift_logging_curator_nodeselector)' failed. The error was: 'unicode' object has no attribute 'items'\n\nThe error appears to have been in '/usr/share/ansible/openshift-ansible/roles/openshift_logging_curator/tasks/main.yaml': line 17, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Ensure that logging curator has nodes to run on\n  ^ here\n"
}

openshift_logging_image_prefix=registry.reg-aws.openshift.com:443/openshift3/
openshift_logging_image_version=v3.9
openshift_logging_elasticsearch_cpu_limit=500m
openshift_logging_elasticsearch_memory_limit=1Gi
openshift_logging_es_ops_cpu_limit=500m
openshift_logging_es_ops_memory_limit=512Mi
openshift_hosted_logging_deploy=true
openshift_hosted_logging_storage_kind=dynamic
openshift_hosted_logging_elasticsearch_cluster_size=1
openshift_logging_elasticsearch_nodeselector="{'purpose': 'infra'}"
openshift_logging_curator_nodeselector="{'purpose': 'infra'}"
openshift_logging_curator_default_days=90
openshift_logging_curator_run_hour=0
openshift_logging_curator_run_minute=0

Version-Release number of selected component (if applicable):
# rpm -qa | grep openshift-ansible
openshift-ansible-docs-3.9.0-0.47.0.git.0.f8847bb.el7.noarch
openshift-ansible-roles-3.9.0-0.47.0.git.0.f8847bb.el7.noarch
openshift-ansible-3.9.0-0.47.0.git.0.f8847bb.el7.noarch
openshift-ansible-playbooks-3.9.0-0.47.0.git.0.f8847bb.el7.noarch

logging component version:v3.9.0-0.47.0.0

How reproducible:
Always

Steps to Reproduce:
1. See the description part
2.
3.

Actual results:
Failed to deploy logging with the same node selector

Expected results:


Additional info:

Comment 1 Junqi Zhao 2018-02-22 12:42:19 UTC
Created attachment 1399353 [details]
logging dump output

Comment 2 Jeff Cantrill 2018-02-22 15:12:00 UTC

*** This bug has been marked as a duplicate of bug 1547210 ***