yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #53375
[Bug 1407936] Re: service_update in conductor can be a async call
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
Valid example: CONFIRMED FOR: LIBERTY
** Changed in: nova
Importance: Low => Undecided
** Changed in: nova
Status: Confirmed => Expired
--
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/1407936
Title:
service_update in conductor can be a async call
Status in OpenStack Compute (nova):
Expired
Bug description:
https://bugs.launchpad.net/nova/+bug/1331537 reported an error for
processing conductor returned data
actually ,the service_update is only a timely function to update conductor service data
and we don't need to keep it as a 'call' API, instead, a 'cast' is fine because we don't need to wait for the return data
to make it cast also can solve the bug 1331537 though we don't know
the real cause of the problem
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1407936/+subscriptions
References