OpenStack Compute (nova)

Clean up warnings about UUIDField invalid values

Bug #1554230 reported by Jay Pipes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
In Progress
Low
Rahul U Nair

Bug Description

Nova test logs are full of the following:

Captured stderr:
~~~~~~~~~~~~~~~~
    /home/jaypipes/repos/nova/.tox/py27/local/lib/python2.7/site-packages/oslo_versionedobjects/fields.py:325: FutureWarning: fake-instance 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. See http://docs.openstack.org/developer/oslo.versionedobjects/api/fields.html#oslo_versionedobjects.fields.UUIDField for further details
      "for further details" % value, FutureWarning)

Should be an easy task to go through and change all the invalid UUID values to use nova.tests.uuidsentinel values instead.

Rahul U Nair (rahulunair)
Changed in nova:
assignee: nobody → Rahul U Nair (rahulunair)
Rahul U Nair (rahulunair)
Changed in nova:
status: Triaged → In Progress
Revision history for this message
Matt Riedemann (mriedem) wrote :

Since there are no patches up for this yet I'm going to mark it as a duplicate of bug 1557378 which is the same issue but has patches up against it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.