Creating a server fails with an error about checksum field

Bug #1479869 reported by Thomas Herve
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Feodor Tersin

Bug Description

As seen here for example: http://logs.openstack.org/18/205018/2/gate/gate-heat-dsvm-functional-orig-mysql/aa761d5/

It gets the error: Caught error: Field `checksum' cannot be None

On logstash it's been happening for some hours: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiVmFsdWVFcnJvcjogRmllbGQgYGNoZWNrc3VtJyBjYW5ub3QgYmUgTm9uZVwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI4NjQwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MzgyNzEwNjEyMTJ9

From bug https://bugs.launchpad.net/cinder/+bug/1308058 it seems that checksum ought to be able to be None, but obviously it's not all the time, so I suppose there is a race condition somewhere. We ought to get a better error if it's transient.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :
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/207679

Changed in nova:
assignee: nobody → Davanum Srinivas (DIMS) (dims-v)
status: New → In Progress
Changed in nova:
importance: Undecided → Critical
importance: Critical → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by Davanum Srinivas (dims) (<email address hidden>) on branch: master
Review: https://review.openstack.org/207679
Reason: in favor of https://review.openstack.org/#/c/208932/

Changed in nova:
assignee: Davanum Srinivas (DIMS) (dims-v) → Feodor Tersin (ftersin)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/208932
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a59f22d27819bc02d548b92198243e20bb2e0014
Submitter: Jenkins
Branch: master

commit a59f22d27819bc02d548b92198243e20bb2e0014
Author: Feodor Tersin <email address hidden>
Date: Tue Aug 4 11:54:39 2015 +0300

    Honour nullability constraints of Glance schema in ImageMeta

    Currently ImageMeta object doesn't allow Null values in fields, which
    are nullable in Glance DB schema.

    By this reason since that Iac034d864cd0265759aaa7c8049fafa276763cc0 is
    merged, Nova fails to boot from any volume-backed image.

    This patch makes ImageMeta class to accept Null values to these fields,
    but converts Null to default empty values for backward compatibility.

    Closes-Bug: #1481220
    Closes-Bug: #1479869
    Change-Id: I770d394f65e5be6a5f8f36c673806f91509e0abe

Changed in nova:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to nova (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/211048

Thierry Carrez (ttx)
Changed in nova:
milestone: none → liberty-3
status: Fix Committed → Fix Released
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/211048
Reason: This patch has been stalled for quite a while, so I am going to abandon it to keep the code review queue sane. Please restore the change when it is ready for review.

Thierry Carrez (ttx)
Changed in nova:
milestone: liberty-3 → 12.0.0
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.