kernel-packages team mailing list archive

[Salvatore Orlando <1273386@xxxxxxxxxxxxxxxxxx>]

We have now rolled the new kernel in the nodes used for the experimental jobs.
This did not help anyway. In the logs the 'waiting for thing to become ACTIVE' failures are still present, but there is a different failure mode (no kernel crash).

However, openvswitch is just not working [1] and the vm boot times out after 120 seconds as it is unable to reach vswitchd [2].
I reckon we should install the saucy version of ovs (1.10) [3]

On another note, there still is something interesting happening during
nbd mount for key injection, as it seems no suitable nbd device is found
[4]. I am not sure this is desired behaviour, but at least it won't hang
VM boot.

Finally, the new kernel is also unable to resolve the hostname. This
might not be a problem but puts error-level statements in pretty much
all log files.

[1] http://logs.openstack.org/64/61964/21/experimental/experimental-tempest-dsvm-neutron-isolated/39133b0/logs/screen-q-agt.txt.gz?level=WARNING#_2014-01-29_15_46_25_922
[2] http://logs.openstack.org/64/61964/21/experimental/experimental-tempest-dsvm-neutron-isolated/39133b0/logs/screen-n-cpu.txt.gz?level=WARNING#_2014-01-29_15_48_34_969
[3] http://packages.ubuntu.com/saucy/openvswitch-switch
[4] http://logs.openstack.org/64/61964/21/experimental/experimental-tempest-dsvm-neutron-isolated/39133b0/logs/screen-n-cpu.txt.gz?level=WARNING#_2014-01-29_15_46_13_781

-- 
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):
  New
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