Comment 1 for bug 1775934

Same instance data plus instance_extra for the instance from penick: http://paste.openstack.org/show/u61jzSxy3y3k9ri496Ms/

^ Shows that the embedded flavor is present (I was concerned the instance was old and had not had its flavor migrated).

The lazy-load of flavor at the REST API level (in nova/api/openstack/compute/servers.py) failing makes sense in that at the REST API level in Ocata, we are not targeted to any cell and thus lazy-loads like this would fail. HOWEVER, we should be pre-loading attributes like 'flavor' (a join with the instance_extra table) when we get_all instances in the compute/api before this instance.get_flavor() call, so the flavor should be cached already and not looked for in the database.

But a lazy-load is definitely happening in the traceback. I don't yet find how this is happening. Continuing to investigate.