solidfire drivers generate request id is not usable

Bug #1199198 reported by John Griffith on 2013-07-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
John Griffith

Bug Description

The SolidFire driver generates a request-id for each API call by converting a UUID into an int. Unfortunately if you're using an "int" for request ID in the Solidfire API it actually needs to be limited to an int.

Fix proposed to branch: master

Changed in cinder:
status: New → In Progress
tags: added: grizzly-backport-potential

Submitter: Jenkins
Branch: master

commit 723486b120f3b2cc106c94191e8de9dc0b4c185f
Author: John Griffith <email address hidden>
Date: Mon Jul 8 19:22:34 2013 -0600

    SolidFire API RequestID is useless.

    The SolidFire API can take an int or a string for a request-id,
    when using an int however it needs to actually be a valid int.

    The driver currently was doing an int(uuid) which is too large and
    as a result get's truncated making it difficult or impossible to track

    This patch chanes the generate request-id to form a hash of the uuid so
    that it can be tracked.

    Fixed bug: 1199198

    Change-Id: I38d5e3d189e679678898c329a9fa173a47853d47

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2013-07-17
Changed in cinder:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2013-10-17
Changed in cinder:
milestone: havana-2 → 2013.2
Alan Pevec (apevec) on 2014-03-31
tags: removed: grizzly-backport-potential
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers