Adding some notes here which we gathered by talking to James Page who in turn was talking to <forgotwho>... One thing to get hold of is real crashdumps. But those will be relatively big and Chris is currently trying to see whether we can trigger this on a devstack environment.
>From what I understand, when forcing the config drive off, the process preparing the image (which I assume runs in its own namespace) will mount the image just before providing it to the guest and write some config data directly into the image. So this makes the namespace of that process have modified mount information and that might be our problem. Not sure there is also some timing side to it or whether it only depends on doing these steps. But at least this gets us ahead in understanding what goes on (and why it would happen more frequently just now). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273386 Title: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1273386/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
