yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #70319
[Bug 1742760] [NEW] InstanceMapping uses invalid UUID
Public bug reported:
The InstanceMapping class contains the 'instance_uuid' field. When
mapping instances, they can be done in batches, and in order to do this,
a marker containing the UUID of the last mapped instance is created in
the table. However, since the instance_uuid column has a unique
constraint, the value is munged by replacing the dashes ('-') with
spaces.
The oslo_versionedobjects module was recently updated to enforce the
validity of all values in UUID fields. As a transition, it only emits
warnings, but in the future, it will raise ValueErrors. Tests of the
mapping marker behavior show the warning:
oslo_versionedobjects/fields.py:348: FutureWarning: 655662b2 6573 42f9
abbf de92533e20a8 is an invalid UUID. Using UUIDFields with invalid
UUIDs is no longer supported, and will be removed in a future release.
Please update your code to input valid UUIDs or accept ValueErrors for
invalid UUIDs.
We need to update the InstanceMapping marker code to avoid creating
invalid UUIDs.
** Affects: nova
Importance: Medium
Assignee: Ed Leafe (ed-leafe)
Status: New
** Tags: instancemapping uuid
--
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/1742760
Title:
InstanceMapping uses invalid UUID
Status in OpenStack Compute (nova):
New
Bug description:
The InstanceMapping class contains the 'instance_uuid' field. When
mapping instances, they can be done in batches, and in order to do
this, a marker containing the UUID of the last mapped instance is
created in the table. However, since the instance_uuid column has a
unique constraint, the value is munged by replacing the dashes ('-')
with spaces.
The oslo_versionedobjects module was recently updated to enforce the
validity of all values in UUID fields. As a transition, it only emits
warnings, but in the future, it will raise ValueErrors. Tests of the
mapping marker behavior show the warning:
oslo_versionedobjects/fields.py:348: FutureWarning: 655662b2 6573 42f9
abbf de92533e20a8 is an invalid UUID. Using UUIDFields with invalid
UUIDs is no longer supported, and will be removed in a future release.
Please update your code to input valid UUIDs or accept ValueErrors for
invalid UUIDs.
We need to update the InstanceMapping marker code to avoid creating
invalid UUIDs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1742760/+subscriptions
Follow ups