yahoo-eng-team team mailing list archive

[Attila Fazekas <afazekas@xxxxxxxxxx>]

The same logstash query founds this error in another jobs, and they are
runtime issues.

http://logs.openstack.org/94/105194/2/check/check-tempest-dsvm-postgres-
full/f029225/logs/screen-n-net.txt.gz#_2014-07-07_17_24_19_012

** Also affects: nova
   Importance: Undecided
       Status: New

-- 
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/1315095

Title:
  grenade nova network (n-net) fails to start

Status in Grenade - OpenStack upgrade testing:
  Confirmed
Status in OpenStack Compute (Nova):
  New

Bug description:
  Here we see that n-net never started logging to it's screen:

  http://logs.openstack.org/02/91502/1/check/check-grenade-
  dsvm/912e89e/logs/new/

  The errors in n-cpu seem to support that the n-net service never
  started.

  According to http://logs.openstack.org/02/91502/1/check/check-grenade-
  dsvm/912e89e/logs/grenade.sh.log.2014-05-01-042623, circa "2014-05-01
  04:31:15.580" the interesting bits should be in:

  /opt/stack/status/stack/n-net.failure

  But I don't see that captured.

  I'm not sure why n-net did not start.

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