kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #43084
[Bug 1273386] Re: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1273386
Title:
Neutron namespace metadata proxy triggers kernel crash on Ubuntu
12.04/3.2 kernel
Status in OpenStack Neutron (virtual network service):
Triaged
Status in OpenStack Compute (Nova):
New
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
In the past 9 days we have been seeing very frequent occurences of
this kernel crash: http://paste.openstack.org/show/61869/
Even if the particular crash pasted here is triggered by dnsmasq, in
almost all cases the crash is actually triggered by the neutron metada
proxy.
This also affects nova badly since this issue, which appears namespace
related, results in a hang while mounting the ndb device for key
injection.
logstash query:
http://logstash.openstack.org/#eyJzZWFyY2giOiJcImtlcm5lbCBCVUcgYXQgL2J1aWxkL2J1aWxkZC9saW51eC0zLjIuMC9mcy9idWZmZXIuYzoyOTE3XCIgYW5kIGZpbGVuYW1lOnN5c2xvZy50eHQiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImN1c3RvbSIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJmcm9tIjoiMjAxNC0wMS0xNlQxODo1MDo0OCswMDowMCIsInRvIjoiMjAxNC0wMS0yN1QxOToxNjoxMSswMDowMCIsInVzZXJfaW50ZXJ2YWwiOiIwIn0sInN0YW1wIjoxMzkwODUwMzI2ODY0fQ==
We have seen about 398 hits since the bug started to manifest.
Decreased hit rate in the past few days is due to less neutron patches being pushed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1273386/+subscriptions