nova-conductor should start earlier

Bug #1665836 reported by Jeffrey Zhang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Undecided
Jeffrey Zhang
Ocata
Fix Released
Undecided
Jeffrey Zhang

Bug Description

Get error in gate when start nova-conductor and nova-compute almost the same time.

2017-02-17 17:39:31.808 7 CRITICAL nova [req-85b349a7-c0b7-43a6-be37-bc87a1b35d25 - - - - -] MessagingTimeout: Timed out waiting for a reply to message ID 3faa1a286dab42258c34933f9c5a9165

[0] http://logs.openstack.org/71/434371/5/check/gate-kolla-dsvm-deploy-oraclelinux-binary-centos-7-nv/3d32dfd/logs/kolla/nova/nova-compute.txt.gz#_2017-02-17_17_38_31_804

[1] http://logs.openstack.org/71/434371/5/check/gate-kolla-dsvm-deploy-oraclelinux-binary-centos-7-nv/3d32dfd/logs/kolla/nova/nova-conductor.txt.gz#_2017-02-17_17_38_46_118

Changed in kolla-ansible:
milestone: none → pike-1
assignee: nobody → Jeffrey Zhang (jeffrey4l)
Changed in kolla-ansible:
status: New → In Progress
caoyuan (cao-yuan)
summary: - nova-conductor should start ealier
+ nova-conductor should start earlier
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.openstack.org/435647
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=7e9e5fd75a9763b0bbb37f164149840437f874cf
Submitter: Jenkins
Branch: master

commit 7e9e5fd75a9763b0bbb37f164149840437f874cf
Author: Jeffrey Zhang <email address hidden>
Date: Sat Feb 18 11:23:49 2017 +0800

    Start nova-conductor earlier

    nova-compute will try to connect nova-conductor when upgrade.level is
    auto. So nova-conductor need run more earlier. Otherwise, nova-compute
    will failed to connect nova-conductor through message queue.

    Closes-Bug: #1665836
    Change-Id: If6296a84305bc283fb071b9650e629c6b1b71e61

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

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/441789

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

Reviewed: https://review.openstack.org/441789
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=36351b94e07045b517c1069a9f4ead22d04737c4
Submitter: Jenkins
Branch: stable/ocata

commit 36351b94e07045b517c1069a9f4ead22d04737c4
Author: Jeffrey Zhang <email address hidden>
Date: Sat Feb 18 11:23:49 2017 +0800

    Start nova-conductor earlier

    nova-compute will try to connect nova-conductor when upgrade.level is
    auto. So nova-conductor need run more earlier. Otherwise, nova-compute
    will failed to connect nova-conductor through message queue.

    Closes-Bug: #1665836
    Change-Id: If6296a84305bc283fb071b9650e629c6b1b71e61
    (cherry picked from commit 7e9e5fd75a9763b0bbb37f164149840437f874cf)

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

This issue was fixed in the openstack/kolla-ansible 4.0.0.0rc2 release candidate.

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

This issue was fixed in the openstack/kolla-ansible 5.0.0.0b2 development milestone.

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.