yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #67195
[Bug 1713095] Re: Nova compute driver init happens before conductor is ready
Reviewed: https://review.openstack.org/497966
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=361287debf7c2cd5751517cedda8c960c5b5eb66
Submitter: Jenkins
Branch: master
commit 361287debf7c2cd5751517cedda8c960c5b5eb66
Author: Dan Smith <dansmith@xxxxxxxxxx>
Date: Fri Aug 25 08:48:49 2017 -0700
Move hash ring initialization to init_host() for ironic
The hash ring initialization code requires calling to conductor over
RPC. Nova's service startup initializes the manager and the virt
driver, then goes into a polling loop waiting for a conductor to
respond to make sure it is ready. Finally, it calls init_host()
once things are expected to be working. That is where we should
do our initialization that requires conductor to be up.
This patch moves the initial refresh into the Ironic driver's
init_host() routine.
Change-Id: If92f4b1df061f91ffffa7900532a978649efb933
Closes-Bug: #1713095
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1713095
Title:
Nova compute driver init happens before conductor is ready
Status in OpenStack Compute (nova):
Fix Released
Bug description:
In nova/service.py we poll for conductor readiness before we allow
normal service startup behavior. The ironic driver does RPC to
conductor in its _refresh_hash_ring() code, which may expect conductor
be up before it's not. If so, we'll fail to start up because we called
to conductor, waited a long time, and then timed out.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1713095/+subscriptions
References