[Yahoo-eng-team] [Bug 1568436] [NEW] Neutron: postgresql db migration alter_enum issue

2016-04-09 Thread Yi Jing Zhu
Public bug reported:

when postgresql is used and we want migration enum type fields. The old type of 
enum will be dropped in alter_enum function.
But when the old enum type is used by another table, drop will failed, thus db 
migration fail.

Solution:
Add do_drop as one arg of alter_enum, let developer to decide when to drop old 
type.

The issue I met is:
2016-04-09 18:28:54.134 | 2016-04-09 18:28:54.095 | {4} 
neutron_vpnaas.tests.functional.openswan.test_openswan_driver.TestOpenSwanDeviceDriver.test_status_reporting
 [0.696702s] ... ok
2016-04-09 18:28:54.134 | 2016-04-09 18:28:54.097 | {3} 
neutron_vpnaas.tests.functional.common.test_migrations_sync.TestModelsMigrationsPsql.test_models_sync
 [4.424209s] ... FAILED
2016-04-09 18:28:54.134 | 2016-04-09 18:28:54.099 | 
2016-04-09 18:28:54.134 | 2016-04-09 18:28:54.101 | Captured stdout:
2016-04-09 18:28:54.135 | 2016-04-09 18:28:54.102 | 
2016-04-09 18:28:54.135 | 2016-04-09 18:28:54.104 | Running upgrade for 
neutron ...
2016-04-09 18:28:54.135 | 2016-04-09 18:28:54.106 | OK
2016-04-09 18:28:54.135 | 2016-04-09 18:28:54.108 | Running upgrade for 
neutron-vpnaas ...
2016-04-09 18:28:54.135 | 2016-04-09 18:28:54.109 | 
2016-04-09 18:28:54.135 | 2016-04-09 18:28:54.111 | Captured traceback:
2016-04-09 18:28:54.136 | 2016-04-09 18:28:54.113 | ~~~
2016-04-09 18:28:54.136 | 2016-04-09 18:28:54.115 | Traceback (most recent 
call last):
2016-04-09 18:28:54.137 | 2016-04-09 18:28:54.117 |   File 
"/opt/stack/new/neutron-vpnaas/.tox/dsvm-functional/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/test_migrations.py",
 line 599, in test_models_sync
2016-04-09 18:28:54.139 | 2016-04-09 18:28:54.119 | 
self.db_sync(self.get_engine())
2016-04-09 18:28:54.141 | 2016-04-09 18:28:54.121 |   File 
"neutron_vpnaas/tests/functional/common/test_migrations_sync.py", line 35, in 
db_sync
2016-04-09 18:28:54.143 | 2016-04-09 18:28:54.122 | 
migration.do_alembic_command(conf, 'upgrade', 'heads')
2016-04-09 18:28:54.145 | 2016-04-09 18:28:54.124 |   File 
"/opt/stack/new/neutron/neutron/db/migration/cli.py", line 131, in 
do_alembic_command
2016-04-09 18:28:54.176 | 2016-04-09 18:28:54.126 | 
getattr(alembic_command, cmd)(config, *args, **kwargs)
2016-04-09 18:28:54.176 | 2016-04-09 18:28:54.128 |   File 
"/opt/stack/new/neutron-vpnaas/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/command.py",
 line 174, in upgrade
2016-04-09 18:28:54.176 | 2016-04-09 18:28:54.130 | script.run_env()
2016-04-09 18:28:54.176 | 2016-04-09 18:28:54.132 |   File 
"/opt/stack/new/neutron-vpnaas/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/script/base.py",
 line 397, in run_env
2016-04-09 18:28:54.177 | 2016-04-09 18:28:54.134 | 
util.load_python_file(self.dir, 'env.py')
2016-04-09 18:28:54.177 | 2016-04-09 18:28:54.135 |   File 
"/opt/stack/new/neutron-vpnaas/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/util/pyfiles.py",
 line 81, in load_python_file
2016-04-09 18:28:54.177 | 2016-04-09 18:28:54.137 | module = 
load_module_py(module_id, path)
2016-04-09 18:28:54.177 | 2016-04-09 18:28:54.139 |   File 
"/opt/stack/new/neutron-vpnaas/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/util/compat.py",
 line 79, in load_module_py
2016-04-09 18:28:54.177 | 2016-04-09 18:28:54.141 | mod = 
imp.load_source(module_id, path, fp)
2016-04-09 18:28:54.178 | 2016-04-09 18:28:54.143 |   File 
"neutron_vpnaas/db/migration/alembic_migrations/env.py", line 87, in 
2016-04-09 18:28:54.178 | 2016-04-09 18:28:54.145 | 
run_migrations_online()
2016-04-09 18:28:54.178 | 2016-04-09 18:28:54.147 |   File 
"neutron_vpnaas/db/migration/alembic_migrations/env.py", line 78, in 
run_migrations_online
2016-04-09 18:28:54.178 | 2016-04-09 18:28:54.149 | 
context.run_migrations()
2016-04-09 18:28:54.178 | 2016-04-09 18:28:54.151 |   File "", line 
8, in run_migrations
2016-04-09 18:28:54.178 | 2016-04-09 18:28:54.152 |   File 
"/opt/stack/new/neutron-vpnaas/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/runtime/environment.py",
 line 797, in run_migrations
2016-04-09 18:28:54.178 | 2016-04-09 18:28:54.154 | 
self.get_context().run_migrations(**kw)
2016-04-09 18:28:54.179 | 2016-04-09 18:28:54.156 |   File 
"/opt/stack/new/neutron-vpnaas/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/runtime/migration.py",
 line 312, in run_migrations
2016-04-09 18:28:54.179 | 2016-04-09 18:28:54.158 | 
step.migration_fn(**kw)
2016-04-09 18:28:54.180 | 2016-04-09 18:28:54.160 |   File 
"/opt/stack/new/neutron-vpnaas/neutron_vpnaas/db/migration/alembic_migrations/versions/newton/expand/fe637dc3f042_support_sha256.py",
 line 41, in upgrade
2016-04-09 18:28:54.182 | 2016-04-09 18:28:54.161 | nullable=False)
2016-04-09 18:28:54.184 | 2016-04-09 18:28:54.163 |  

[Yahoo-eng-team] [Bug 1568414] [NEW] Database Poison Warnings

2016-04-09 Thread Diana Clarke
Public bug reported:

The following warning appears a number of times in the unit test logs.
Use this bug to track the patches that eliminate these warnings.

"UserWarning: This test uses methods that set internal oslo_db state,
but it does not claim to use the database. This will conflict with the
setup of tests that do use the database and cause failures later."

Note that this warning is only emitted once per unit test worker, so new
offenders will show up in the logs each time you fix a test until they
are all gone.

Once all of these warnings are removed, change the warning to an
exception so that we don't get more of these in the future.

** Affects: nova
 Importance: Undecided
 Assignee: Diana Clarke (diana-clarke)
 Status: Confirmed

** Changed in: nova
 Assignee: (unassigned) => Diana Clarke (diana-clarke)

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

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

Title:
  Database Poison Warnings

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  The following warning appears a number of times in the unit test logs.
  Use this bug to track the patches that eliminate these warnings.

  "UserWarning: This test uses methods that set internal oslo_db state,
  but it does not claim to use the database. This will conflict with the
  setup of tests that do use the database and cause failures later."

  Note that this warning is only emitted once per unit test worker, so
  new offenders will show up in the logs each time you fix a test until
  they are all gone.

  Once all of these warnings are removed, change the warning to an
  exception so that we don't get more of these in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1568414/+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 1568400] [NEW] Pecan does not route to QoS extension

2016-04-09 Thread Brandon Logan
Public bug reported:

When using the pecan wsgi framework and the QoS extension and service
plugin, any requests to /v2.0/qos/policies.json fails with a 400.

** Affects: neutron
 Importance: Undecided
 Assignee: Brandon Logan (brandon-logan)
 Status: In Progress

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

Title:
  Pecan does not route to QoS extension

Status in neutron:
  In Progress

Bug description:
  When using the pecan wsgi framework and the QoS extension and service
  plugin, any requests to /v2.0/qos/policies.json fails with a 400.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1568400/+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 1568386] [NEW] Integration tests fail due to slow creation of an instance

2016-04-09 Thread Timur Sufiev
Public bug reported:

If you ever encounter traceback like this in the results of gate-
horizon-dsvm-integration job

2016-04-09 19:32:21.451 | 2016-04-09 19:32:21.432 | Traceback (most recent call 
last):
2016-04-09 19:32:21.453 | 2016-04-09 19:32:21.433 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/tests/test_instances.py",
 line 197, in test_filter_instances
2016-04-09 19:32:21.455 | 2016-04-09 19:32:21.435 | 
self.assertTrue(instances_page.is_instance_active(instance_list[0]))
2016-04-09 19:32:21.456 | 2016-04-09 19:32:21.437 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/project/compute/instancespage.py",
 line 115, in is_instance_active
2016-04-09 19:32:21.458 | 2016-04-09 19:32:21.438 | lambda: 
row.cells[self.INSTANCES_TABLE_STATUS_COLUMN], 'Active')
2016-04-09 19:32:21.460 | 2016-04-09 19:32:21.440 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/regions/tables.py",
 line 158, in is_cell_status
2016-04-09 19:32:21.462 | 2016-04-09 19:32:21.443 | 
self._wait_till_text_present_in_element(cell_getter, status)
2016-04-09 19:32:21.464 | 2016-04-09 19:32:21.444 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 110, in _wait_till_text_present_in_element
2016-04-09 19:32:21.466 | 2016-04-09 19:32:21.446 | 
self._wait_until(predicate, timeout)
2016-04-09 19:32:21.468 | 2016-04-09 19:32:21.448 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 94, in _wait_until
2016-04-09 19:32:21.469 | 2016-04-09 19:32:21.449 | predicate)
2016-04-09 19:32:21.471 | 2016-04-09 19:32:21.451 |   File 
"/opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/support/wait.py",
 line 71, in until
2016-04-09 19:32:21.472 | 2016-04-09 19:32:21.453 | value = 
method(self._driver)
2016-04-09 19:32:21.474 | 2016-04-09 19:32:21.454 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 107, in predicate
2016-04-09 19:32:21.476 | 2016-04-09 19:32:21.456 | elt = element() if 
hasattr(element, '__call__') else element
2016-04-09 19:32:21.478 | 2016-04-09 19:32:21.458 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/project/compute/instancespage.py",
 line 115, in 
2016-04-09 19:32:21.479 | 2016-04-09 19:32:21.460 | lambda: 
row.cells[self.INSTANCES_TABLE_STATUS_COLUMN], 'Active')
2016-04-09 19:32:21.481 | 2016-04-09 19:32:21.462 | AttributeError: 'NoneType' 
object has no attribute 'cells'

It most likely means that an instance row was tested for the presence of
a specific status even before this row had appeared. This (slow Nova
response) could happen, but it shouldn't cause tests to fail.

** Affects: horizon
 Importance: Undecided
 Status: New

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

Title:
  Integration tests fail due to slow creation of an instance

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  If you ever encounter traceback like this in the results of gate-
  horizon-dsvm-integration job

  2016-04-09 19:32:21.451 | 2016-04-09 19:32:21.432 | Traceback (most recent 
call last):
  2016-04-09 19:32:21.453 | 2016-04-09 19:32:21.433 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/tests/test_instances.py",
 line 197, in test_filter_instances
  2016-04-09 19:32:21.455 | 2016-04-09 19:32:21.435 | 
self.assertTrue(instances_page.is_instance_active(instance_list[0]))
  2016-04-09 19:32:21.456 | 2016-04-09 19:32:21.437 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/project/compute/instancespage.py",
 line 115, in is_instance_active
  2016-04-09 19:32:21.458 | 2016-04-09 19:32:21.438 | lambda: 
row.cells[self.INSTANCES_TABLE_STATUS_COLUMN], 'Active')
  2016-04-09 19:32:21.460 | 2016-04-09 19:32:21.440 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/regions/tables.py",
 line 158, in is_cell_status
  2016-04-09 19:32:21.462 | 2016-04-09 19:32:21.443 | 
self._wait_till_text_present_in_element(cell_getter, status)
  2016-04-09 19:32:21.464 | 2016-04-09 19:32:21.444 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 110, in _wait_till_text_present_in_element
  2016-04-09 19:32:21.466 | 2016-04-09 19:32:21.446 | 
self._wait_until(predicate, timeout)
  2016-04-09 19:32:21.468 | 2016-04-09 19:32:21.448 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 94, in _wait_until
  2016-04-09 19:32:21.469 | 2016-04-09 19:32:21.449 | predicate)
  2016-04-09 19:32:21.471 | 2016-04-09 19:32:21.451 |   File 
"/opt/stack/new/horiz

[Yahoo-eng-team] [Bug 1568387] [NEW] Integration tests fail due to slow creation of an instance

2016-04-09 Thread Timur Sufiev
Public bug reported:

If you ever encounter traceback like this in the results of gate-
horizon-dsvm-integration job

2016-04-09 19:32:21.451 | 2016-04-09 19:32:21.432 | Traceback (most recent call 
last):
2016-04-09 19:32:21.453 | 2016-04-09 19:32:21.433 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/tests/test_instances.py",
 line 197, in test_filter_instances
2016-04-09 19:32:21.455 | 2016-04-09 19:32:21.435 | 
self.assertTrue(instances_page.is_instance_active(instance_list[0]))
2016-04-09 19:32:21.456 | 2016-04-09 19:32:21.437 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/project/compute/instancespage.py",
 line 115, in is_instance_active
2016-04-09 19:32:21.458 | 2016-04-09 19:32:21.438 | lambda: 
row.cells[self.INSTANCES_TABLE_STATUS_COLUMN], 'Active')
2016-04-09 19:32:21.460 | 2016-04-09 19:32:21.440 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/regions/tables.py",
 line 158, in is_cell_status
2016-04-09 19:32:21.462 | 2016-04-09 19:32:21.443 | 
self._wait_till_text_present_in_element(cell_getter, status)
2016-04-09 19:32:21.464 | 2016-04-09 19:32:21.444 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 110, in _wait_till_text_present_in_element
2016-04-09 19:32:21.466 | 2016-04-09 19:32:21.446 | 
self._wait_until(predicate, timeout)
2016-04-09 19:32:21.468 | 2016-04-09 19:32:21.448 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 94, in _wait_until
2016-04-09 19:32:21.469 | 2016-04-09 19:32:21.449 | predicate)
2016-04-09 19:32:21.471 | 2016-04-09 19:32:21.451 |   File 
"/opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/support/wait.py",
 line 71, in until
2016-04-09 19:32:21.472 | 2016-04-09 19:32:21.453 | value = 
method(self._driver)
2016-04-09 19:32:21.474 | 2016-04-09 19:32:21.454 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 107, in predicate
2016-04-09 19:32:21.476 | 2016-04-09 19:32:21.456 | elt = element() if 
hasattr(element, '__call__') else element
2016-04-09 19:32:21.478 | 2016-04-09 19:32:21.458 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/project/compute/instancespage.py",
 line 115, in 
2016-04-09 19:32:21.479 | 2016-04-09 19:32:21.460 | lambda: 
row.cells[self.INSTANCES_TABLE_STATUS_COLUMN], 'Active')
2016-04-09 19:32:21.481 | 2016-04-09 19:32:21.462 | AttributeError: 'NoneType' 
object has no attribute 'cells'

It most likely means that an instance row was tested for the presence of
a specific status even before this row had appeared. This (slow Nova
response) could happen, but it shouldn't cause tests to fail.

** Affects: horizon
 Importance: Medium
 Status: New

** Changed in: horizon
   Importance: Undecided => Medium

** Changed in: horizon
Milestone: None => newton-1

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

Title:
  Integration tests fail due to slow creation of an instance

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  If you ever encounter traceback like this in the results of gate-
  horizon-dsvm-integration job

  2016-04-09 19:32:21.451 | 2016-04-09 19:32:21.432 | Traceback (most recent 
call last):
  2016-04-09 19:32:21.453 | 2016-04-09 19:32:21.433 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/tests/test_instances.py",
 line 197, in test_filter_instances
  2016-04-09 19:32:21.455 | 2016-04-09 19:32:21.435 | 
self.assertTrue(instances_page.is_instance_active(instance_list[0]))
  2016-04-09 19:32:21.456 | 2016-04-09 19:32:21.437 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/project/compute/instancespage.py",
 line 115, in is_instance_active
  2016-04-09 19:32:21.458 | 2016-04-09 19:32:21.438 | lambda: 
row.cells[self.INSTANCES_TABLE_STATUS_COLUMN], 'Active')
  2016-04-09 19:32:21.460 | 2016-04-09 19:32:21.440 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/regions/tables.py",
 line 158, in is_cell_status
  2016-04-09 19:32:21.462 | 2016-04-09 19:32:21.443 | 
self._wait_till_text_present_in_element(cell_getter, status)
  2016-04-09 19:32:21.464 | 2016-04-09 19:32:21.444 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 110, in _wait_till_text_present_in_element
  2016-04-09 19:32:21.466 | 2016-04-09 19:32:21.446 | 
self._wait_until(predicate, timeout)
  2016-04-09 19:32:21.468 | 2016-04-09 19:32:21.448 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 94, in _wait_until
  2016-04-09 19:32:21.469 | 2016-04-09 1

[Yahoo-eng-team] [Bug 1568342] [NEW] Ubuntu Mitaka package fails to upgrade

2016-04-09 Thread György Szombathelyi
Public bug reported:

Upgrading Mitaka from Liberty fails with:
Unpacking openstack-dashboard (2:9.0.0-0ubuntu1~cloud0) over 
(2:8.0.1-0ubuntu1~cloud0) ...
.
.
.
Collecting and compressing static assets...
CommandError: An error occurred during rendering 
/usr/share/openstack-dashboard/openstack_dashboard/templates/_stylesheets.html: 
Error evaluating expression:
$helpPanelWidthDefault

on line 51 of framework/widgets/help-panel/help-panel.scss
imported from line 50 of framework/widgets/widgets.scss
imported from line 50 of framework/framework.scss
imported from line 6 of dashboard/scss/horizon.scss
imported from line 1 of u'string:ed963272ebc1da4e:\n// My Themes\n@import 
"/themes/ubuntu/variables";\n\n// Horizon\n@import "/dashboard/scss/horizon.s'
Traceback:
  File "/usr/lib/python2.7/dist-packages/scss/calculator.py", line 141, in 
evaluate_expression
return ast.evaluate(self, divide=divide)
  File "/usr/lib/python2.7/dist-packages/scss/ast.py", line 346, in evaluate
raise SyntaxError("Undefined variable: '%s'." % self.name)
SyntaxError: Undefined variable: '$helpPanelWidthDefault'.
dpkg: error processing package openstack-dashboard (--configure):
 subprocess installed post-installation script returned error exit status 1


The workaround is to clean up the compiled static assets before upgrading 
(/usr/share/openstack-dashboard/openstack_dashboard/static). I think it should 
be done in the pre-install script.

** Affects: horizon
 Importance: Undecided
 Status: New

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

Title:
  Ubuntu Mitaka package fails to upgrade

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Upgrading Mitaka from Liberty fails with:
  Unpacking openstack-dashboard (2:9.0.0-0ubuntu1~cloud0) over 
(2:8.0.1-0ubuntu1~cloud0) ...
  .
  .
  .
  Collecting and compressing static assets...
  CommandError: An error occurred during rendering 
/usr/share/openstack-dashboard/openstack_dashboard/templates/_stylesheets.html: 
Error evaluating expression:
  $helpPanelWidthDefault

  on line 51 of framework/widgets/help-panel/help-panel.scss
  imported from line 50 of framework/widgets/widgets.scss
  imported from line 50 of framework/framework.scss
  imported from line 6 of dashboard/scss/horizon.scss
  imported from line 1 of u'string:ed963272ebc1da4e:\n// My Themes\n@import 
"/themes/ubuntu/variables";\n\n// Horizon\n@import "/dashboard/scss/horizon.s'
  Traceback:
File "/usr/lib/python2.7/dist-packages/scss/calculator.py", line 141, in 
evaluate_expression
  return ast.evaluate(self, divide=divide)
File "/usr/lib/python2.7/dist-packages/scss/ast.py", line 346, in evaluate
  raise SyntaxError("Undefined variable: '%s'." % self.name)
  SyntaxError: Undefined variable: '$helpPanelWidthDefault'.
  dpkg: error processing package openstack-dashboard (--configure):
   subprocess installed post-installation script returned error exit status 1

  
  The workaround is to clean up the compiled static assets before upgrading 
(/usr/share/openstack-dashboard/openstack_dashboard/static). I think it should 
be done in the pre-install script.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1568342/+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 1568325] [NEW] Phantom is causing JS tests to fail constantly

2016-04-09 Thread Rob Cresswell
Public bug reported:

An error downloading PhantomJS is causing the JS tests to fail on many
patches. We should consider working around this until there is a more
reliable solution.

** Affects: horizon
 Importance: Undecided
 Assignee: Rob Cresswell (robcresswell)
 Status: In Progress

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

Title:
  Phantom is causing JS tests to fail constantly

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  An error downloading PhantomJS is causing the JS tests to fail on many
  patches. We should consider working around this until there is a more
  reliable solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1568325/+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 1568292] [NEW] broken review priorities link in devref

2016-04-09 Thread Matt Riedemann
Public bug reported:

The 2nd to last section here:

http://docs.openstack.org/developer/nova/how_to_get_involved.html#why-
do-code-reviews-if-i-am-not-in-nova-core

There is a busted link:

https://etherpad.openstack.org/p/ -nova-priorities-tracking

That should be this now: https://etherpad.openstack.org/p/newton-nova-
priorities-tracking

Also, in the "TODO - I think there is more to add here" section, we
could list these gerrit review dashboards for nova:

1. from the IRC channel topic: https://goo.gl/1vTS0Z

2. small bug fixes: http://ow.ly/WAw1J

** Affects: nova
 Importance: Medium
 Status: Confirmed


** Tags: devref doc low-hanging-fruit

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

Title:
  broken review priorities link in devref

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  The 2nd to last section here:

  http://docs.openstack.org/developer/nova/how_to_get_involved.html#why-
  do-code-reviews-if-i-am-not-in-nova-core

  There is a busted link:

  https://etherpad.openstack.org/p/ -nova-priorities-tracking

  That should be this now: https://etherpad.openstack.org/p/newton-nova-
  priorities-tracking

  Also, in the "TODO - I think there is more to add here" section, we
  could list these gerrit review dashboards for nova:

  1. from the IRC channel topic: https://goo.gl/1vTS0Z

  2. small bug fixes: http://ow.ly/WAw1J

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1568292/+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 1377308] Re: booting cloud image without initramfs broken

2016-04-09 Thread Scott Moser
** Also affects: cloud-init (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Trusty)
   Status: New => Triaged

** Changed in: cloud-init (Ubuntu Trusty)
   Importance: Undecided => Medium

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

Title:
  booting cloud image without initramfs broken

Status in cloud-init:
  Triaged
Status in cloud-init package in Ubuntu:
  Triaged
Status in cloud-init source package in Trusty:
  Triaged

Bug description:
  Booting without a initramfs was broken by the cloud-init change for
  bug 1353008 (http://pad.lv/1353008).

  This affects arm guests where a bootloader is not used that would load
  kernel and initramfs.

  There are 2 workarounds:
  a.) remove the offensive code
    sudo mount-image-callback ubuntu.img -- \
   sh -c 'f="$MOUNTPOINT/etc/init/cloud-init-local.conf";
  sed -e "/^start on/s/ and mounted .*//" -i.dist $f &&
  diff -u $f.dist $f'

  b.) register and boot with an initramfs
    This is done by
     i.) getting the initramfs out of the image:
   sudo mount-image-callback ubuntu.img -- \
     sh -c 'cp $MOUNTPOINT/boot/initrd* . && chmod ugo+r initrd*'
     ii.) upload the initramfs to glance
   glance image-create --name=ubuntu-ramdisk --public \
  --container-format ari --disk-format ari < initrd*
   record the ramdisk id
     iii.) register with --property ramdisk_id=$RAMDISK_ID
   normally for "ami" style images on arm, the user had been
   uploading with --property kernel_id=.
   now, you need to upload with:
     glance image-create --name="$NAME" \
    --public --container-format ami --disk-format ami \
    --property "kernel_id=$KERNEL_ID" \
    --property "ramdisk_id=$RAMDISK_ID" \ < ubuntu.img

   c.) register 'kernel command line' to include 'rw'.
   glance image-create  --property kernel_args="root=/dev/vda rw"

  Related bugs:
   * bug 1031065:cloud-init-nonet runs 'start networking' explicitly
   * bug 643289: [mountall] idmapd does not starts to work after system reboot
   * bug 1353008:[cloud-init] MAAS Provider: LXC did not get DHCP address, 
stuck in "pending"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cloud-init 0.7.5-0ubuntu1.2
  ProcVersionSignature: User Name 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic aarch64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: arm64
  Date: Thu Jan  1 00:02:09 1970
  Ec2AMI: ami-0007
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.5GB
  Ec2Kernel: aki-0005
  Ec2Ramdisk: ari-0003
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.cloud.init.local.conf: 2014-10-03T19:49:16.813801

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1377308/+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 1568063] Re: Batch buttons enabled/disabled state is lost on table rows update

2016-04-09 Thread OpenStack Infra
Reviewed:  https://review.openstack.org/303551
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=ac63c15c9406c4d6b32ddf148b82775bd7c784dc
Submitter: Jenkins
Branch:master

commit ac63c15c9406c4d6b32ddf148b82775bd7c784dc
Author: Timur Sufiev 
Date:   Fri Apr 8 20:38:33 2016 +0300

Fix batch action buttons state loosening

Now the batch button correctly reacts to toggling row checkboxes.

Change-Id: I28435cf5a396a83aaf471ded142db88f6a64ac5c
Closes-Bug: #1568063


** Changed in: horizon
   Status: In Progress => Fix Released

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

Title:
  Batch buttons enabled/disabled state is lost on table rows update

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Steps to reproduce:

  1. Launch an instance
  2. While the row is being updated, select it - notice that 'Delete Instances' 
button became enabled
  3. Once row update finishes, 'Delete Instances' becomes disabled although an 
Instance row is still marked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1568063/+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 1564551] Re: initialize_connection failure can result in 'exceptions.TypeError' object has no attribute 'code'

2016-04-09 Thread OpenStack Infra
Reviewed:  https://review.openstack.org/300751
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=2135a3f55ffec9c0fe7064aa339a430af4ee
Submitter: Jenkins
Branch:master

commit 2135a3f55ffec9c0fe7064aa339a430af4ee
Author: Wenzhi Yu 
Date:   Sat Apr 2 23:34:22 2016 +0800

Check if a exception has a code on it before read the code

In 'nova.volume.cinder.API.initialize_connection' method, all exceptions
threw by 'terminate_connection' will be caught and logged. When log the
exceptions, the code try to record the 'code' attribute of the exception
since the code is expecting a CinderClientException or NovaException[1].
But if the some else exception(like TypeError) which doesn't have a code
on it was threw up, we will got a AttributeError.

This commit add logic to check if the exception has a code on it before
try to read it.


[1]https://github.com/openstack/nova/blob/13.0.0.0rc3/nova/volume/cinder.py#L437

Change-Id: I42fd2f2b77c41a60dfaf0cc882a344596d50daf5
Closes-Bug: #1564551


** Changed in: nova
   Status: In Progress => Fix Released

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

Title:
  initialize_connection failure can result in 'exceptions.TypeError'
  object has no attribute 'code'

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) liberty series:
  New
Status in OpenStack Compute (nova) mitaka series:
  New

Bug description:
  Doing an initialize_connection() results in the following partial code
  stack:

  2016-03-29 06:51:06.882 25713 ERROR nova.compute.manager [instance: 
4c8d25b3-b136-4c72-a381-4b80dcca5c49]   File 
"/usr/lib/python2.7/dist-packages/nova/volume/cinder.py", line 232, in wrapper
  2016-03-29 06:51:06.882 25713 ERROR nova.compute.manager [instance: 
4c8d25b3-b136-4c72-a381-4b80dcca5c49] res = method(self, ctx, *args, 
**kwargs)
  2016-03-29 06:51:06.882 25713 ERROR nova.compute.manager [instance: 
4c8d25b3-b136-4c72-a381-4b80dcca5c49]   File 
"/usr/lib/python2.7/dist-packages/nova/volume/cinder.py", line 259, in wrapper
  2016-03-29 06:51:06.882 25713 ERROR nova.compute.manager [instance: 
4c8d25b3-b136-4c72-a381-4b80dcca5c49] res = method(self, ctx, volume_id, 
*args, **kwargs)
  2016-03-29 06:51:06.882 25713 ERROR nova.compute.manager [instance: 
4c8d25b3-b136-4c72-a381-4b80dcca5c49]   File 
"/usr/lib/python2.7/dist-packages/nova/volume/cinder.py", line 437, in 
initialize_connection
  2016-03-29 06:51:06.882 25713 ERROR nova.compute.manager [instance: 
4c8d25b3-b136-4c72-a381-4b80dcca5c49] 'code': exc.code})
  2016-03-29 06:51:06.882 25713 ERROR nova.compute.manager [instance: 
4c8d25b3-b136-4c72-a381-4b80dcca5c49] AttributeError: 'exceptions.TypeError' 
object has no attribute 'code'

  
  Here is the method:

  @translate_volume_exception
  def initialize_connection(self, context, volume_id, connector):
  try:
  connection_info = cinderclient(
  context).volumes.initialize_connection(volume_id, connector)
  connection_info['connector'] = connector
  return connection_info
  except cinder_exception.ClientException as ex:
  with excutils.save_and_reraise_exception():
  LOG.error(_LE('Initialize connection failed for volume '
'%(vol)s on host %(host)s. Error: %(msg)s '
'Code: %(code)s. Attempting to terminate '
'connection.'),
{'vol': volume_id,
 'host': connector.get('host'),
 'msg': six.text_type(ex),
 'code': ex.code})
  try:
  self.terminate_connection(context, volume_id, connector)
  except Exception as exc:
  LOG.error(_LE('Connection between volume %(vol)s and host 
'
'%(host)s might have succeeded, but attempt 
'
'to terminate connection has failed. '
'Validate the connection and determine if '
'manual cleanup is needed. Error: %(msg)s '
'Code: %(code)s.'),
{'vol': volume_id,
 'host': connector.get('host'),
 'msg': six.text_type(exc),
 'code': exc.code})   <-- 
blows up

  @translate_volume_exception
  def terminate_connection(self, context, volume_id, connector):
  return cinderclient(context).volumes.terminate_connection(volume_id,