Failed to deploy kibana

Bug #1819246 reported by Mai Ngoc Duong
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Undecided
Mai Ngoc Duong

Bug Description

Hi,

I'm trying to deploy openstack with monasca enabled with kolla-ansible master, but failed in TASK [kibana : Restart kibana container].

- which kolla version you are using: kolla-ansible master branch
- what's the install type and distro: docker with centos based and install type is binary
- where and when the kolla image is built: images from docker kolla hub and build at 2019-03-07

TASK [kibana : Check kibana containers] ***********************************************************************************************************************************************************
changed: [compute01] => (item={'value': {u'haproxy': {u'kibana_external': {u'mode': u'http', u'auth_user': u'kibana', u'auth_pass': u'Kva10wZDsIugR8LDe7UAvgFVpLlIaSaxWJkLY6Bx', u'enabled': u'yes', u'port': u'5601', u'external': True}, u'kibana': {u'mode': u'http', u'auth_user': u'kibana', u'auth_pass': u'Kva10wZDsIugR8LDe7UAvgFVpLlIaSaxWJkLY6Bx', u'enabled': u'yes', u'port': u'5601', u'external': False}}, u'group': u'kibana', u'dimensions': {}, u'volumes': [u'/etc/kolla//kibana/:/var/lib/kolla/config_files/:ro', u'/etc/localtime:/etc/localtime:ro', u'kolla_logs:/var/log/kolla/'], u'container_name': u'kibana', u'image': u'192.168.1.221:5000/kolla/centos-binary-kibana:master', u'enabled': True}, 'key': u'kibana'})

RUNNING HANDLER [kibana : Restart kibana container] ***********************************************************************************************************************************************
fatal: [compute01]: FAILED! => {"msg": "The conditional check 'config_json.changed | bool or kibana_conf.changed | bool or kibana_container.changed | bool' failed. The error was: error while evaluating conditional (config_json.changed | bool or kibana_conf.changed | bool or kibana_container.changed | bool): 'ansible.utils.unsafe_proxy.AnsibleUnsafeText object' has no attribute 'key'\n\nThe error appears to have been in '/root/kolla-ansible/ansible/roles/kibana/handlers/main.yml': line 2, 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: Restart kibana container\n ^ here\n"}

NO MORE HOSTS LEFT ********************************************************************************************************************************************************************************
 to retry, use: --limit @/root/kolla-ansible/ansible/site.retry

Mai Ngoc Duong (duongmn)
Changed in kolla-ansible:
assignee: nobody → Mai Ngoc Duong (duongmn)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (master)

Fix proposed to branch: master
Review: https://review.openstack.org/642197

Changed in kolla-ansible:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.openstack.org/642197
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=2519451696de8bb46430c55982997c95d5cf9cd6
Submitter: Zuul
Branch: master

commit 2519451696de8bb46430c55982997c95d5cf9cd6
Author: Duong Mai <email address hidden>
Date: Sat Mar 9 11:46:04 2019 +0700

    Edit ansible script for deploy kibana

    Kibana deployment failed becaused of kibana_confs variable does not have attribute key,
    So handlers failed to check conditional kibana_conf.changed | bool becaused of
    kibana_confs.results|selectattr(item.key) does not exits.

    Change variable name kibana_confs to kibana_conf.

    Change-Id: If5e0a25b270a6f05c435a6dc32e2ac49406389c5
    Closes-Bug: #1819246

Changed in kolla-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 8.0.0.0rc1

This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.