Comment 6 for bug 1199003

Ok, thanks. What's the proximity of these errors to puppet runs--e.g. does it appear immediately after the catalog run is complete, immediately after it starts, somewhere in between? I'm having a hard time figuring out how Puppet might be triggering this, so trying to pin down the proximity to see if it might be coincidental to a Puppet run.

If you're doing a rebuild, it would also be interesting to see:

1.) Does the error appear before any instances have launched?

2.) Does it appear after starting an instance or two?

3.) Does it appear after terminating one of those instances?

4.) Does it appear if you get an instance into an error state (say, by telling nova to boot an instance while your compute nodes are rebooting)?

I'm basically wondering if the interface table is somehow getting entries for ports that don't have an endpoint due to the instance having been terminated and the IP returned to the pool. I've seen only one occurance of this error in my logs, and I know I had an instance in error state around that time (due to me having tried to launch an instance while my compute nodes were down....oops). I'll try to test that theory later today.