OpenStack Compute (Nova)

recursive zone calls hang when at least 1 child API call hangs

Reported by Chris Behrens on 2011-07-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
High
Unassigned

Bug Description

If a child zone API call hangs for some reason (I've had it happen due to another bug.. I think possibly lp:803168), the parent will wait forever. Parent needs to deal with this more gracefully.. either by timing out queries to children. If the scheduler is doing a select query to figure out available hosts for a build request, it should ignore zones that aren't responding. Other queries might need to return an error.

Related branches

Chris Behrens (cbehrens) wrote :

Attempting to fit this into my team's Sprint 9 work (due 7/15/2011)

Changed in nova:
assignee: nobody → Ozone (rackspace-ozone)
status: New → Confirmed
Thierry Carrez (ttx) on 2011-07-06
Changed in nova:
importance: Undecided → High
Thierry Carrez (ttx) on 2011-07-21
Changed in nova:
status: Confirmed → In Progress
Thierry Carrez (ttx) on 2011-07-25
Changed in nova:
assignee: Ozone (rackspace-ozone) → Ed Leafe (ed-leafe)
Chris Behrens (cbehrens) wrote :

I believe this was fixed by adding timeouts to nova-client. Going to change this to 'Invalid'. If there's a problem in the future, we'll open a new bug.

Changed in nova:
status: In Progress → Invalid
Ed Leafe (ed-leafe) wrote :

Just a heads-up: timeout exceptions were added to nova-client, but a subsequent merge removed them. You might want to double-check your "beliefs" before rejecting this.

Chris Behrens (cbehrens) on 2011-09-09
Changed in nova:
status: Invalid → New
Chris Behrens (cbehrens) wrote :

Ah, thanks. Fair point.

I knew you had fixed it in novaclient... at one time. I did not know it got removed, however. Interesting. Was there a specific reason for the removal from novaclient as far as you're aware... Ie, people felt it didn't belong there... or ?

Did you want to leave this bug assigned to yourself or want one of us to take it?

Ed Leafe (ed-leafe) wrote :

I don't believe that it was deliberately removed; at least no one said anything about doing so. Rather, it seems as though it was accidentally removed in a later pull request, and none of the approvers noticed.

I won't have time to work on this, so you should assign it to someone else.

Changed in nova:
assignee: Ed Leafe (ed-leafe) → nobody
Thierry Carrez (ttx) on 2011-09-09
Changed in nova:
status: New → Confirmed
Chris Behrens (cbehrens) wrote :

doesn't apply anymore now that zones code is removed.

Changed in nova:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers