yahoo-eng-team team mailing list archive

[John Griffith <1357677@xxxxxxxxxxxxxxxxxx>]

I'm not sure why this is logged as a Cinder bug?  Other than the fact
that it's boot from volume perhaps, but the instance appears to boot
correctly and is in ACTIVE state.  The issue here seems to be networking
as the ssh connection fails...  no?

http://logs.openstack.org/75/113175/1/gate/check-tempest-dsvm-neutron-
full/827c854/console.html.gz#_2014-08-14_11_23_29_423

Not sure if this is on the Neutron side or the Nova side, but I suspect
it's a networking issue, regardless doesn't seem like a Cinder issue as
far as I can tell.

** No longer affects: cinder

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1357677

Title:
  Instances failes to boot from volume

Status in OpenStack Compute (Nova):
  New

Bug description:
  Logstash query for full console outputs which does not contains 'info:
  initramfs loading root from /dev/vda' , but contains the previous boot
  message.

  These issues look like ssh connectivity issue, but the instance is not
  booted and it happens regardless to the network type.

  message: "Freeing unused kernel memory" AND message: "Initializing
  cgroup subsys cpuset" AND NOT message: "initramfs loading root from"
  AND tags:"console"

  49 incident/week.

  Example console log:
  http://logs.openstack.org/75/113175/1/gate/check-tempest-dsvm-neutron-full/827c854/console.html.gz#_2014-08-14_11_23_30_120

  It failed when it's tried to ssh 3th server.
  WARNING: The conole.log contains two instances serial console output,  try no to mix them when reading.

  The fail point in the test code was here:
  https://github.com/openstack/tempest/blob/b7144eb08175d010e1300e14f4f75d04d9c63c98/tempest/scenario/test_volume_boot_pattern.py#L175

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1357677/+subscriptions