murano fails to deploy - cannot check core lib

Bug #1634531 reported by Vladislav Belogrudov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
High
Vladislav Belogrudov
Newton
Fix Released
High
Vladislav Belogrudov
Ocata
Fix Released
High
Vladislav Belogrudov

Bug Description

when deploying murano it sometimes fails to check if core lib has already been uploaded. This happens because active murano-api containers still are to be discovered by haproxy. The latter has 2 sec check interval. Typical error message:

TASK [murano : Waiting for Murano API service to be ready] *********************
ok: [10.196.10.201]
ok: [10.196.10.203]
ok: [10.196.10.202]

TASK [murano : Checking if Murano core library package exists] *****************
fatal: [10.196.10.201]: FAILED! => {"changed": false, "cmd": ["docker", "exec", "murano_api", "murano", "--os-username", "admin", "--os-password", "password", "--os-project-name", "admin", "--os-auth-url", "http://10.196.10.222:35357/v3", "package-list"], "delta": "0:00:01.120635", "end": "2016-10-18 15:11:09.517623", "failed": true, "rc": 1, "start": "2016-10-18 15:11:08.396988", "stderr": "503 Service Unavailable: No server is available to handle this request. (HTTP 503)", "stdout": "", "stdout_lines": [], "warnings": []}

The second run will deploy murano because api services have been identified by haproxy.

summary: - murano fails on first start
+ murano fails to deploy - cannot check core lib
Changed in kolla:
assignee: nobody → Vladislav Belogrudov (vlad-belogrudov)
Changed in kolla:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (master)

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

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

Reviewed: https://review.openstack.org/388068
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=d7d8fc8069eb15e4b705ccf3d5620faf7c3c28b5
Submitter: Jenkins
Branch: master

commit d7d8fc8069eb15e4b705ccf3d5620faf7c3c28b5
Author: Vladislav Belogrudov <email address hidden>
Date: Tue Oct 18 18:00:45 2016 +0300

    Murano fails to deploy - cannot check core library

    Murano sometimes fails to deploy due to delay in haproxy
    identifying started API services. Instead of waiting for all the
    services and checking existance of core library via VIP deploy
    task should connect to one of the services directly for testing
    service status and for package import.

    Change-Id: I2934579edc910e81730dd89dbd8ff9eb11a2cc1c
    Closes-Bug: #1634531

Changed in kolla:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (stable/newton)

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/388583

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (stable/newton)

Reviewed: https://review.openstack.org/388583
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=b6cf81387d216de8f941bb0a748740a29b86eb23
Submitter: Jenkins
Branch: stable/newton

commit b6cf81387d216de8f941bb0a748740a29b86eb23
Author: Vladislav Belogrudov <email address hidden>
Date: Tue Oct 18 18:00:45 2016 +0300

    Murano fails to deploy - cannot check core library

    Murano sometimes fails to deploy due to delay in haproxy
    identifying started API services. Instead of waiting for all the
    services and checking existance of core library via VIP deploy
    task should connect to one of the services directly for testing
    service status and for package import.

    Change-Id: I2934579edc910e81730dd89dbd8ff9eb11a2cc1c
    Closes-Bug: #1634531
    (cherry picked from commit d7d8fc8069eb15e4b705ccf3d5620faf7c3c28b5)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla 3.0.1

This issue was fixed in the openstack/kolla 3.0.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla 4.0.0.0b1

This issue was fixed in the openstack/kolla 4.0.0.0b1 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla 3.0.1

This issue was fixed in the openstack/kolla 3.0.1 release.

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.