wait for grafana ready failed

Bug #1821285 reported by lei zhang on 2019-03-22
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kolla-ansible
High
Chason Chan

Bug Description

- which kolla version you are using
  master
- what's the install type and distro
  source、centos
- where and when the kolla image is built?
  pull from dockerhub

When kolla deploying grafana, it will check whether grafana's login URL. After serval times deploy tests, I find some times it check failed. But after an interval, I can open the grafana's login page.

TASK [grafana : Wait for grafana application ready] **************************************************************************************************************************************************************
FAILED - RETRYING: Wait for grafana application ready (10 retries left).
FAILED - RETRYING: Wait for grafana application ready (9 retries left).
FAILED - RETRYING: Wait for grafana application ready (8 retries left).
FAILED - RETRYING: Wait for grafana application ready (7 retries left).
FAILED - RETRYING: Wait for grafana application ready (6 retries left).
FAILED - RETRYING: Wait for grafana application ready (5 retries left).
FAILED - RETRYING: Wait for grafana application ready (4 retries left).
FAILED - RETRYING: Wait for grafana application ready (3 retries left).
FAILED - RETRYING: Wait for grafana application ready (2 retries left).
FAILED - RETRYING: Wait for grafana application ready (1 retries left).
fatal: [localhost]: FAILED! => {"attempts": 10, "changed": false, "content": "", "msg": "Status code was -1 and not [200]: Request failed: <urlopen error [Errno 111] 拒绝连接>", "redirected": false, "status": -1, "url": "http://192.168.132.9:3000/login"}

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

PLAY RECAP *******************************************************************************************************************************************************************************************************
localhost : ok=405 changed=234 unreachable=0 failed=1

I think we should increase the delay of this task to prevent from such issue.

Chason Chan (chen-xing) on 2019-03-22
Changed in kolla-ansible:
assignee: nobody → Chason Chan (chen-xing)

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

Changed in kolla-ansible:
status: New → In Progress

Reviewed: https://review.opendev.org/645496
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=20ef211f6a045ebfdf786564b6af3936345bbdc3
Submitter: Zuul
Branch: master

commit 20ef211f6a045ebfdf786564b6af3936345bbdc3
Author: chenxing <email address hidden>
Date: Fri Mar 22 15:54:13 2019 +0800

    Increase retries numbers of grafana check task

    20 seconds may be too short to wait for grafana ready, Let's keep the
    check task 60 seconds.

    backport: rocky

    Change-Id: Ib219ad215d1ef2147ba3591f8c398feb4f3c8888
    Closes-Bug: #1821285

Changed in kolla-ansible:
status: In Progress → Fix Released
Changed in kolla-ansible:
milestone: none → 8.0.0
Changed in kolla-ansible:
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers