resize failed because of instance's invalid availability zone property

Bug #1431194 reported by Lingxian Kong
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Low
Unassigned

Bug Description

steps to reproduce:

1. create a server with az(which doesn't exist) and force_host, e.g.
"availability_zone": "invalid_zone:devstack"
Creation will succeed, because nova-api will not check the existence of az if the force_host is specified.

2. resize the server, the operation will failed with error:
"No valid host was found. No valid host found for resize"

Lingxian Kong (kong)
Changed in nova:
assignee: nobody → Lingxian Kong (kong)
Changed in nova:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

Changed in nova:
status: Confirmed → In Progress
Revision history for this message
Matt Riedemann (mriedem) wrote :

Is bug 1444841 a duplicate of this?

Revision history for this message
Qin Zhao (zhaoqin) wrote :

I do not think my bug is duplicated with this one. I am attempting to solve AZ inconsistency between instance and its host.

Revision history for this message
Qin Zhao (zhaoqin) wrote :

This bug specifies invalid AZ value, I am not sure if this case will continue to be regarded as a valid one. Anyway, before making a patch, I feel we need to reconsider AZ property of instance. Why we need this property for instance? Az represents a set of host. Why do we have AZ property for host and instance both?

Revision history for this message
Lingxian Kong (kong) wrote :

hi, Qin,

FWIW, i don't like the idea of removal of az property of instance, it will break backward compatibility, which is not acceptable for a OpenStack based product.

Revision history for this message
Qin Zhao (zhaoqin) wrote :

As I mentioned in bug 1444841, two straight forward ways to solve this problem:

1. Keep instance.az, but make it obsolete. Set instance.az when booting, and always read host's az after that.

2. Make instance.az be consistent with host az. That means we always need to update instance.az in db, when host az changes.

The patch that I currently making is #1. Hope other good ideas.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by Michael Still (<email address hidden>) on branch: master
Review: https://review.openstack.org/163842
Reason: Abandoning this patch because it has been idle for a long time.

Matt Riedemann (mriedem)
Changed in nova:
status: In Progress → Confirmed
assignee: Lingxian Kong (kong) → nobody
Changed in nova:
assignee: nobody → Zhenyu Zheng (zhengzhenyu)
Revision history for this message
Sujitha (sujitha-neti) wrote :

There are no open reviews for this bug report since a long time.
To signal that to other contributors which might provide patches for
this bug, I'm removing the assignee.

Feel free to add yourself as assignee and push a review for it.

Changed in nova:
assignee: Zhenyu Zheng (zhengzhenyu) → nobody
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

Changed in nova:
assignee: nobody → Diana Clarke (diana-clarke)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by Diana Clarke (<email address hidden>) on branch: master
Review: https://review.openstack.org/389845

Changed in nova:
assignee: Diana Clarke (diana-clarke) → nobody
Changed in nova:
status: In Progress → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers