[Yahoo-eng-team] [Bug 1332788] [NEW] AttributeError: 'MeteringAgentWithStateReport' object has no attribute '_periodic_last_run'

2014-06-21 Thread Attila Fazekas
Public bug reported:

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

All screen-q-metering.log contains a similar exception:
2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall 
Traceback (most recent call last):
2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall   File 
/opt/stack/new/neutron/neutron/openstack/common/loopingcall.py, line 76, in 
_inner
2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall 
self.f(*self.args, **self.kw)
2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall   File 
/opt/stack/new/neutron/neutron/service.py, line 294, in periodic_tasks
2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall 
self.manager.periodic_tasks(ctxt, raise_on_error=raise_on_error)
2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall   File 
/opt/stack/new/neutron/neutron/manager.py, line 45, in periodic_tasks
2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall 
self.run_periodic_tasks(context, raise_on_error=raise_on_error)
2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall   File 
/opt/stack/new/neutron/neutron/openstack/common/periodic_task.py, line 160, 
in run_periodic_tasks
2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall 
last_run = self._periodic_last_run[task_name]
2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall 
AttributeError: 'MeteringAgentWithStateReport' object has no attribute 
'_periodic_last_run'
2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall

** Affects: neutron
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1332788

Title:
  AttributeError: 'MeteringAgentWithStateReport' object has no attribute
  '_periodic_last_run'

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  
http://logstash.openstack.org/#eyJmaWVsZHMiOltdLCJzZWFyY2giOiJtZXNzYWdlOlwiQXR0cmlidXRlRXJyb3JcXDogJ01ldGVyaW5nQWdlbnRXaXRoU3RhdGVSZXBvcnQnIFwiIiwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJvZmZzZXQiOjAsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIiwic3RhbXAiOjE0MDMzNDAzMDI5MjB9

  All screen-q-metering.log contains a similar exception:
  2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall 
Traceback (most recent call last):
  2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall   
File /opt/stack/new/neutron/neutron/openstack/common/loopingcall.py, line 76, 
in _inner
  2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall 
self.f(*self.args, **self.kw)
  2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall   
File /opt/stack/new/neutron/neutron/service.py, line 294, in periodic_tasks
  2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall 
self.manager.periodic_tasks(ctxt, raise_on_error=raise_on_error)
  2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall   
File /opt/stack/new/neutron/neutron/manager.py, line 45, in periodic_tasks
  2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall 
self.run_periodic_tasks(context, raise_on_error=raise_on_error)
  2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall   
File /opt/stack/new/neutron/neutron/openstack/common/periodic_task.py, line 
160, in run_periodic_tasks
  2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall 
last_run = self._periodic_last_run[task_name]
  2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall 
AttributeError: 'MeteringAgentWithStateReport' object has no attribute 
'_periodic_last_run'
  2014-06-21 07:20:37.543 14529 TRACE neutron.openstack.common.loopingcall

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1332789] [NEW] frightful ERROR level messages in the screen-q-vpn.txt

2014-06-21 Thread Attila Fazekas
Public bug reported:

http://logstash.openstack.org/#eyJmaWVsZHMiOltdLCJzZWFyY2giOiJtZXNzYWdlOlwiU3RkZXJyOiAnRGV2aWNlIFwiIEFORCBtZXNzYWdlOiBcImRvZXMgbm90IGV4aXN0XCIiLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsIm9mZnNldCI6MCwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwibW9kZSI6IiIsImFuYWx5emVfZmllbGQiOiIiLCJzdGFtcCI6MTQwMzM0MDY3ODk1Nn0=

865671 hit.

2014-06-21 08:32:12.391 14321 ERROR neutron.agent.linux.utils [-]
Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 
'ip', 'netns', 'exec', 'qrouter-09b99e41-f9a6-4427-97b6-eb99c7c8f107', 'ip', 
'-o', 'link', 'show', 'qr-8f7490f2-9d']
Exit code: 1
Stdout: ''
Stderr: 'Device qr-8f7490f2-9d does not exist.\n'

q-vpn tries to manipulate a not yet created device and reports it as an
ERROR.

The device at this time only could exists if it were created before the q-vpn 
started or another service would create it.
None of them true. 

Please decrease this message verbosity or use different interface
creation strategy.

The DEBUG or INFO level is appropriate level at this time.

** Affects: neutron
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1332789

Title:
  frightful  ERROR level messages in the screen-q-vpn.txt

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  
http://logstash.openstack.org/#eyJmaWVsZHMiOltdLCJzZWFyY2giOiJtZXNzYWdlOlwiU3RkZXJyOiAnRGV2aWNlIFwiIEFORCBtZXNzYWdlOiBcImRvZXMgbm90IGV4aXN0XCIiLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsIm9mZnNldCI6MCwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwibW9kZSI6IiIsImFuYWx5emVfZmllbGQiOiIiLCJzdGFtcCI6MTQwMzM0MDY3ODk1Nn0=

  865671 hit.

  2014-06-21 08:32:12.391 14321 ERROR neutron.agent.linux.utils [-]
  Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 
'ip', 'netns', 'exec', 'qrouter-09b99e41-f9a6-4427-97b6-eb99c7c8f107', 'ip', 
'-o', 'link', 'show', 'qr-8f7490f2-9d']
  Exit code: 1
  Stdout: ''
  Stderr: 'Device qr-8f7490f2-9d does not exist.\n'

  q-vpn tries to manipulate a not yet created device and reports it as
  an ERROR.

  The device at this time only could exists if it were created before the q-vpn 
started or another service would create it.
  None of them true. 

  Please decrease this message verbosity or use different interface
  creation strategy.

  The DEBUG or INFO level is appropriate level at this time.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1332855] Re: grenade test fails due to tempest.scenario.test_dashboard_basic_ops.TestDashboardBasicOps.test_basic_scenario[dashboard]

2014-06-21 Thread John Griffith
excerpts from Sean's email that just went out but hasn't hit archives
yet:

```
Horizon in icehouse is now 100% failing

 [Sat Jun 21 16:17:35 2014] [error] Internal Server Error: /
[Sat Jun 21 16:17:35 2014] [error] Traceback (most recent call last):
[Sat Jun 21 16:17:35 2014] [error]   File
/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py,
line 112, in get_response
[Sat Jun 21 16:17:35 2014] [error] response =
wrapped_callback(request, *callback_args, **callback_kwargs)
[Sat Jun 21 16:17:35 2014] [error]   File
/usr/local/lib/python2.7/dist-packages/django/views/decorators/vary.py, line
36, in inner_func
[Sat Jun 21 16:17:35 2014] [error] response = func(*args, **kwargs)
[Sat Jun 21 16:17:35 2014] [error]   File
/opt/stack/old/horizon/openstack_dashboard/wsgi/../../openstack_dashboard/views.py,
line 35, in splash
[Sat Jun 21 16:17:35 2014] [error] form = views.Login(request)
[Sat Jun 21 16:17:35 2014] [error] AttributeError: 'module' object has
no attribute 'Login'

This suspiciously times with django_openstack_auth 1.1.6 being released.
http://logstash.openstack.org/#eyJzZWFyY2giOiJcIkF0dHJpYnV0ZUVycm9yOiAnbW9kdWxlJyBvYmplY3QgaGFzIG5vIGF0dHJpYnV0ZSAnTG9naW4nXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MDMzNjk0MjQ4NjR9

Because this breaks smoke tests on icehouse, it means that any project
with upgrade testing fails.

Would be great if horizon folks code make this a top priority. Also, in
future, releasing new library versions on a saturday maybe best avoided. :)

-Sean


** Project changed: tempest = horizon

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

Title:
  grenade test fails due to
  
tempest.scenario.test_dashboard_basic_ops.TestDashboardBasicOps.test_basic_scenario[dashboard]

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Grenade dsvm-jobs are failing.  Console output doesn't offer much, but
  looking at the grenade summary logs the culprit seems to be a
  dashboard ops test:

  http://logs.openstack.org/52/101252/1/check/check-grenade-
  dsvm/25e55c2/logs/grenade.sh.log.2014-06-21-153223

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1332855] Re: grenade test fails due to tempest.scenario.test_dashboard_basic_ops.TestDashboardBasicOps.test_basic_scenario[dashboard]

2014-06-21 Thread David Lyle
** Also affects: django-openstack-auth
   Importance: Undecided
   Status: New

** Changed in: django-openstack-auth
   Status: New = In Progress

** Changed in: django-openstack-auth
   Importance: Undecided = Critical

** Changed in: django-openstack-auth
 Assignee: (unassigned) = David Lyle (david-lyle)

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

Title:
  grenade test fails due to
  
tempest.scenario.test_dashboard_basic_ops.TestDashboardBasicOps.test_basic_scenario[dashboard]

Status in Django OpenStack Auth:
  In Progress
Status in OpenStack Dashboard (Horizon):
  Confirmed

Bug description:
  Grenade dsvm-jobs are failing.  Console output doesn't offer much, but
  looking at the grenade summary logs the culprit seems to be a
  dashboard ops test:

  http://logs.openstack.org/52/101252/1/check/check-grenade-
  dsvm/25e55c2/logs/grenade.sh.log.2014-06-21-153223

To manage notifications about this bug go to:
https://bugs.launchpad.net/django-openstack-auth/+bug/1332855/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp