[Openstack] nova error migrating with floating ips: 'FixedIP' object has no attribute '_sa_instance_state'

Noel Burton-Krahn noel at pistoncloud.com
Wed Jun 25 06:39:29 UTC 2014


Thanks a lot for the quick reply, Dan.  It's good to know that _context is
expected to be a RequestContext.  We do have some changes to nova, although
none are obviously in this area.  I'll look there and file a bug if this is
from pure nova.

--
Noel



On Tue, Jun 24, 2014 at 3:33 PM, Dan Smith <dansmith at redhat.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > floating_ip.save() Exception during message handling: 'FixedIP'
> > object has no attribute '_sa_instance_state'
> >
> >
> > The floating_ip object's context did appears to be a
> > RequestContext object, not a SQLAlchemy object
>
> I think you're confusing NovaObjects with SA objects. A NovaObject's
> _context *should* be a RequestContext.
>
> > floating_ip.__dict__={'_address': IPAddress('10.35.4.6'),
> > '_interface': u'public', '_updated_at': datetime.datetime(2014, 6,
> > 24, 20, 38, 28, tzinfo=<iso8601.iso8601.Utc object at
> > 0x7f97cad18e10>), '_context': <nova.context.RequestContext object
> > at 0x7f97cac4acd0>, '_auto_assigned': False, '_pool': u'nova',
> > '_deleted_at': None, '_deleted': False, '_created_at':
> > datetime.datetime(2014, 6, 24, 16, 14, 50,
> > tzinfo=<iso8601.iso8601.Utc object at 0x7f97cad18dd0>),
> > '_fixed_ip_id': 10, '_host': u'10.35.0.15', '_changed_fields':
> > set([]), '_id': 6, '_project_id':
> > '96164da78025487daf0b7a20cb338939'}
>
> This is a NovaObject, but the reference to "_sa_instance_state" is a
> SQLAlchemy thing, AFAIK. The commit of mine you reference is about
> converting the use of some SA objects and bare dicts to NovaObjects.
> If your object looks like the above, but you're getting the above
> message about _sa_instance_state, the something is very (very) confused.
>
> > I'm still working through why
> > floating_ip_obj.FloatingIP.get_by_address() may return an object
> > that doesn't work.
> >
> > Dan, does this ring any bells?
>
> This looks highly fishy. Is the code modified in any way? If not, file
> a bug with all these details please.
>
> - --Dan
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJTqfy0AAoJEBeZxaMESjNVrakIANBBYbr+EOHTv8fPYE/Gb4jo
> zoNKuixNZFEJk19qTY2Fdk4OsKw1qq1aJ+kXH/G9WZEQQjNwkrbOhyb2gTEk4rF/
> HQEKRoHVMAa3cOtwzCRsyYVQ/Q0MdNJFug+CYPcGHQYT1en+c8kdVhLAfnXD/pBu
> XO9l2elQr4uBq2fmkG0Biet35qqb62g5p6o1haxhzLWM83X+9yTwTalyqcdCmgKz
> Uzy1V2A9pYxpiPyPC1R3y6onq8R9HlLrGH1SMtPgDNyno+HsWrokbLvgWKJr0tfU
> asAfamRkS92BkeyCx4SoCcIho+NIq7ySILRhDx2ojGtIKjelI6KYAcqQQoKHcT0=
> =qvTt
> -----END PGP SIGNATURE-----
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140624/0dd81f25/attachment.html>


More information about the Openstack mailing list