yahoo-eng-team team mailing list archive

[John Griffith <1270608@xxxxxxxxxxxxxxxxxx>]

Turns out this does appear to be a side effect of commit: e2e0ed80799c1ba04b37278996a171fc74b6f9eb
does seem to be the root of the problem.  It appears that the initialize is in some cases doing a delete of 
the targets.

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

** Changed in: cinder
       Status: New => Confirmed

** Changed in: cinder
   Importance: Undecided => Critical

** Changed in: cinder
     Assignee: (unassigned) => John Griffith (john-griffith)

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

Title:
  n-cpu 'iSCSI device not found' log causes gate-tempest-dsvm-*-full to
  fail

Status in Cinder:
  Confirmed
Status in OpenStack Compute (Nova):
  Fix Committed

Bug description:
  Changes are failing the gate-tempest-*-full gate due to an error message in the logs.
  The error message is like

  2014-01-18 20:13:19.437 | Log File: n-cpu
  2014-01-18 20:13:20.482 | 2014-01-18 20:04:05.189 ERROR nova.compute.manager [req-25a1842c-ce9a-4035-8975-651f6ee5ddfc tempest.scenario.manager-tempest-1060379467-user tempest.scenario.manager-tempest-1060379467-tenant] [instance: 0b1c1b55-b520-4ff2-bac2-8457ba3f4b6a] Error: iSCSI device not found at /dev/disk/by-path/ip-127.0.0.1:3260-iscsi-iqn.2010-10.org.openstack:volume-a6e86002-dc25-4782-943b-58cc0c68238d-lun-1

  Here's logstash for the query:

  http://logstash.openstack.org/#eyJzZWFyY2giOiJmaWxlbmFtZTpcImxvZ3Mvc2NyZWVuLW4tY3B1LnR4dFwiIEFORCBtZXNzYWdlOlwiRXJyb3I6IGlTQ1NJIGRldmljZSBub3QgZm91bmQgYXQgL2Rldi9kaXNrL2J5LXBhdGgvaXAtMTI3LjAuMC4xOjMyNjAtaXNjc2ktaXFuLjIwMTAtMTAub3JnLm9wZW5zdGFjazp2b2x1bWUtXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjEzOTAxNTA4NTU5NTJ9

  shows several failures starting at 2014-01-17T14:00:00

  Maybe tempest is doing something that generates the ERROR message and then isn't accepting the error message it should?
  Or nova is logging an error message when it shouldn't?

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