[Yahoo-eng-team] [Bug 1462802] [NEW] Unable to update Firewall name, description and Admin state

2015-06-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After a firewall has been created, trying to update the firewall name or
description or Admin state from Horizon UI displays error message
Error: Failed to update firewall: Request Fail;ed: internal server
error while processing your request (see attached screenshot)

** Affects: neutron
 Importance: Undecided
 Status: New

-- 
Unable to update Firewall name, description and Admin state
https://bugs.launchpad.net/bugs/1462802
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to neutron.

-- 
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 1462802] [NEW] Unable to update Firewall name, description and Admin state

2015-06-07 Thread vishwanath jayaraman
Public bug reported:

After a firewall has been created, trying to update the firewall name or
description or Admin state from Horizon UI displays error message
Error: Failed to update firewall: Request Fail;ed: internal server
error while processing your request (see attached screenshot)

** Affects: neutron
 Importance: Undecided
 Assignee: vishwanath jayaraman (vishwanathj)
 Status: New

** Project changed: ddtp-ubuntu = neutron

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

Title:
  Unable to update Firewall name, description and Admin state

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  After a firewall has been created, trying to update the firewall name
  or description or Admin state from Horizon UI displays error message
  Error: Failed to update firewall: Request Fail;ed: internal server
  error while processing your request (see attached screenshot)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1462802/+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 1461251] Re: Stop using deprecated oslo_utils.timeutils.isotime

2015-06-07 Thread Brant Knudson
** Also affects: python-keystoneclient
   Importance: Undecided
   Status: New

** Changed in: python-keystoneclient
 Assignee: (unassigned) = Brant Knudson (blk-u)

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

Title:
  Stop using deprecated oslo_utils.timeutils.isotime

Status in OpenStack Identity (Keystone):
  Fix Committed
Status in Oslo utility library:
  New
Status in Python client library for Keystone:
  In Progress

Bug description:
  oslo_utils.timeutils.isotime() is deprecated as of 1.6 so we need to
  stop using it.

  This breaks unit tests in keystone since we've got a check for calling
  deprecated functions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1461251/+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 1462851] [NEW] invalid event status None

2015-06-07 Thread Kevin Benton
Public bug reported:

Spike of Invalid event status 'none' caused by recent event handler
change 70c6b57751cf67f5a2be80d7b2d2123c826a8a68

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

** Affects: nova
 Importance: Undecided
 Assignee: Kevin Benton (kevinbenton)
 Status: In Progress

** Changed in: nova
 Assignee: (unassigned) = Kevin Benton (kevinbenton)

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

Title:
  invalid event status None

Status in OpenStack Compute (Nova):
  In Progress

Bug description:
  Spike of Invalid event status 'none' caused by recent event handler
  change 70c6b57751cf67f5a2be80d7b2d2123c826a8a68

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1462851/+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 1462858] [NEW] Missing role argument when create new user in CLI

2015-06-07 Thread Canh Truong
Public bug reported:

On horizon dashboard, we have mandatory field  Role for creating new
user. However, using CLI to create new user that doesn't have argument
for Role option. I think we should update for this.

~/devstack$ keystone help user-create
/usr/local/lib/python2.7/dist-packages/keystoneclient/shell.py:65: 
DeprecationWarning: The keystone CLI is deprecated in favor of 
python-openstackclient. For a Python library, continue using 
python-keystoneclient.
  'python-keystoneclient.', DeprecationWarning)
usage: keystone user-create --name user-name [--tenant tenant]
[--pass [pass]] [--email email]
[--enabled true|false]

Create new user.

Arguments:
  --name user-nameNew user name (must be unique).
  --tenant tenant, --tenant-id tenant
New user default tenant.
  --pass [pass]   New user password; required for some auth backends.
  --email email   New user email address.
  --enabled true|false

** Affects: keystone
 Importance: Undecided
 Status: New

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

Title:
  Missing role argument when create new user in CLI

Status in OpenStack Identity (Keystone):
  New

Bug description:
  On horizon dashboard, we have mandatory field  Role for creating new
  user. However, using CLI to create new user that doesn't have argument
  for Role option. I think we should update for this.

  ~/devstack$ keystone help user-create
  /usr/local/lib/python2.7/dist-packages/keystoneclient/shell.py:65: 
DeprecationWarning: The keystone CLI is deprecated in favor of 
python-openstackclient. For a Python library, continue using 
python-keystoneclient.
'python-keystoneclient.', DeprecationWarning)
  usage: keystone user-create --name user-name [--tenant tenant]
  [--pass [pass]] [--email email]
  [--enabled true|false]

  Create new user.

  Arguments:
--name user-nameNew user name (must be unique).
--tenant tenant, --tenant-id tenant
  New user default tenant.
--pass [pass]   New user password; required for some auth backends.
--email email   New user email address.
--enabled true|false

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1462858/+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 1462858] Re: Missing role argument when create new user in CLI

2015-06-07 Thread Boris Bobrov
``keystone'' cli is deprecated, you should use ``openstack'' cli --
http://docs.openstack.org/developer/python-openstackclient/.

** Project changed: keystone = python-keystoneclient

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

Title:
  Missing role argument when create new user in CLI

Status in Python client library for Keystone:
  New

Bug description:
  On horizon dashboard, we have mandatory field  Role for creating new
  user. However, using CLI to create new user that doesn't have argument
  for Role option. I think we should update for this.

  ~/devstack$ keystone help user-create
  /usr/local/lib/python2.7/dist-packages/keystoneclient/shell.py:65: 
DeprecationWarning: The keystone CLI is deprecated in favor of 
python-openstackclient. For a Python library, continue using 
python-keystoneclient.
'python-keystoneclient.', DeprecationWarning)
  usage: keystone user-create --name user-name [--tenant tenant]
  [--pass [pass]] [--email email]
  [--enabled true|false]

  Create new user.

  Arguments:
--name user-nameNew user name (must be unique).
--tenant tenant, --tenant-id tenant
  New user default tenant.
--pass [pass]   New user password; required for some auth backends.
--email email   New user email address.
--enabled true|false

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-keystoneclient/+bug/1462858/+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 1462857] Re: Missing update primary project argument when updating user in CLI

2015-06-07 Thread Boris Bobrov
``keystone'' cli is deprecated, you should use ``openstack'' cli --
http://docs.openstack.org/developer/python-openstackclient/.

** Project changed: keystone = python-keystoneclient

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

Title:
  Missing update primary project argument  when updating user in CLI

Status in Python client library for Keystone:
  New

Bug description:
  On horizon dashboard, updating user have  Primary Project field.
  However, we don't have argument for updating this field when we update
  user in CLI

  ~/devstack$ keystone help user-update
  /usr/local/lib/python2.7/dist-packages/keystoneclient/shell.py:65: 
DeprecationWarning: The keystone CLI is deprecated in favor of 
python-openstackclient. For a Python library, continue using 
python-keystoneclient.
'python-keystoneclient.', DeprecationWarning)
  usage: keystone user-update [--name user-name] [--email email]
  [--enabled true|false]
  user

  Update user's name, email, and enabled status.

  Arguments:
--name user-nameDesired new user name.
--email email   Desired new email address.
--enabled true|false
  Enable or disable user.
userName or ID of user to update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-keystoneclient/+bug/1462857/+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 1462871] [NEW] L2Population on OVS broken due to ofctl resactoring

2015-06-07 Thread Mike Kolesnik
Public bug reported:

The refactor [1] to seperate ofctl logic to a driver broke L2pop on OVS.

The L2 agent shows this error when receiving a call to add_tunnel_port:

2015-06-08 04:33:50.287 DEBUG neutron.agent.l2population_rpc 
[req-a3dcc834-e97d-471b-8cae-02b6b0c58325 None None] 
neutron.plugins.openvswitch.
agent.ovs_neutron_agent.OVSNeutronAgent method fdb_add_tun called with 
arguments (neutron.context.Context object at 0x4421510, neutron.plug
ins.openvswitch.agent.openflow.ovs_ofctl.br_tun.DeferredOVSTunnelBridge object 
at 0x44213d0, neutron.plugins.openvswitch.agent.ovs_neutron_a
gent.LocalVLANMapping object at 0x3c43510, {u'10.35.6.102': 
[PortInfo(mac_address=u'00:00:00:00:00:00', ip_address=u'0.0.0.0'), 
PortInfo(mac_
address=u'fa:16:3e:c6:17:9f', ip_address=u'10.0.0.2'), 
PortInfo(mac_address=u'fa:16:3e:c6:17:9f', 
ip_address=u'fd59:ade1:1482:0:f816:3eff:fec6
:179f')]}, bound method OVSNeutronAgent._tunnel_port_lookup of 
neutron.plugins.openvswitch.agent.ovs_neutron_agent.OVSNeutronAgent object at
 0x3c43310) {} from (pid=14807) wrapper 
/usr/lib/python2.7/site-packages/oslo_log/helpers.py:45
2015-06-08 04:33:50.287 ERROR neutron.agent.common.ovs_lib 
[req-a3dcc834-e97d-471b-8cae-02b6b0c58325 None None] OVS flows could not be 
applied
 on bridge br-tun
2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib Traceback (most 
recent call last):
2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib   File 
/opt/openstack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.
py, line 448, in fdb_add
2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib agent_ports, 
self._tunnel_port_lookup)
2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib   File 
/usr/lib/python2.7/site-packages/oslo_log/helpers.py, line 46, in wrapper
2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib return 
method(*args, **kwargs)
2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib   File 
/opt/openstack/neutron/neutron/agent/l2population_rpc.py, line 234, in fdb
_add_tun
2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib lvm.network_type)
2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib   File 
/opt/openstack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.
py, line 1169, in setup_tunnel_port
2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib network_type)
2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib   File 
/opt/openstack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.
py, line 1135, in _setup_tunnel_port
2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib ofport = 
br.add_tunnel_port(port_name,
2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib   File 
/opt/openstack/neutron/neutron/plugins/openvswitch/agent/openflow/ovs_ofctl/br_tun.py,
 line 246, in __getattr__
2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib raise 
AttributeError(name)
2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib AttributeError: 
add_tunnel_port
2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib 

[1] https://review.openstack.org/#/c/160245/

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: l2-pop ovs

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

Title:
  L2Population on OVS broken due to ofctl resactoring

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  The refactor [1] to seperate ofctl logic to a driver broke L2pop on
  OVS.

  The L2 agent shows this error when receiving a call to
  add_tunnel_port:

  2015-06-08 04:33:50.287 DEBUG neutron.agent.l2population_rpc 
[req-a3dcc834-e97d-471b-8cae-02b6b0c58325 None None] 
neutron.plugins.openvswitch.
  agent.ovs_neutron_agent.OVSNeutronAgent method fdb_add_tun called with 
arguments (neutron.context.Context object at 0x4421510, neutron.plug
  ins.openvswitch.agent.openflow.ovs_ofctl.br_tun.DeferredOVSTunnelBridge 
object at 0x44213d0, neutron.plugins.openvswitch.agent.ovs_neutron_a
  gent.LocalVLANMapping object at 0x3c43510, {u'10.35.6.102': 
[PortInfo(mac_address=u'00:00:00:00:00:00', ip_address=u'0.0.0.0'), 
PortInfo(mac_
  address=u'fa:16:3e:c6:17:9f', ip_address=u'10.0.0.2'), 
PortInfo(mac_address=u'fa:16:3e:c6:17:9f', 
ip_address=u'fd59:ade1:1482:0:f816:3eff:fec6
  :179f')]}, bound method OVSNeutronAgent._tunnel_port_lookup of 
neutron.plugins.openvswitch.agent.ovs_neutron_agent.OVSNeutronAgent object at
   0x3c43310) {} from (pid=14807) wrapper 
/usr/lib/python2.7/site-packages/oslo_log/helpers.py:45
  2015-06-08 04:33:50.287 ERROR neutron.agent.common.ovs_lib 
[req-a3dcc834-e97d-471b-8cae-02b6b0c58325 None None] OVS flows could not be 
applied
   on bridge br-tun
  2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib Traceback (most 
recent call last):
  2015-06-08 04:33:50.287 TRACE neutron.agent.common.ovs_lib   File 

[Yahoo-eng-team] [Bug 1462857] [NEW] Missing update primary project argument when updating user in CLI

2015-06-07 Thread Canh Truong
Public bug reported:

On horizon dashboard, updating user have  Primary Project field.
However, we don't have argument for updating this field when we update
user in CLI

~/devstack$ keystone help user-update
/usr/local/lib/python2.7/dist-packages/keystoneclient/shell.py:65: 
DeprecationWarning: The keystone CLI is deprecated in favor of 
python-openstackclient. For a Python library, continue using 
python-keystoneclient.
  'python-keystoneclient.', DeprecationWarning)
usage: keystone user-update [--name user-name] [--email email]
[--enabled true|false]
user

Update user's name, email, and enabled status.

Arguments:
  --name user-nameDesired new user name.
  --email email   Desired new email address.
  --enabled true|false
Enable or disable user.
  userName or ID of user to update.

** Affects: keystone
 Importance: Undecided
 Status: New

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

Title:
  Missing update primary project argument  when updating user in CLI

Status in OpenStack Identity (Keystone):
  New

Bug description:
  On horizon dashboard, updating user have  Primary Project field.
  However, we don't have argument for updating this field when we update
  user in CLI

  ~/devstack$ keystone help user-update
  /usr/local/lib/python2.7/dist-packages/keystoneclient/shell.py:65: 
DeprecationWarning: The keystone CLI is deprecated in favor of 
python-openstackclient. For a Python library, continue using 
python-keystoneclient.
'python-keystoneclient.', DeprecationWarning)
  usage: keystone user-update [--name user-name] [--email email]
  [--enabled true|false]
  user

  Update user's name, email, and enabled status.

  Arguments:
--name user-nameDesired new user name.
--email email   Desired new email address.
--enabled true|false
  Enable or disable user.
userName or ID of user to update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1462857/+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 1441512] Re: neutron-lbaas tempest v2 api negative test-cases with invalid tenant-id fails

2015-06-07 Thread Launchpad Bug Tracker
[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
   Status: Incomplete = Expired

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

Title:
  neutron-lbaas tempest v2 api negative test-cases  with invalid tenant-
  id fails

Status in OpenStack Neutron (virtual network service):
  Expired

Bug description:
  Tempest v2 api negative tests for  invalid or empty tenantid fails  as
  tenant id is not validated at plugin layer.

  1. In Case of looging noop driver (no validation is done by driver ) , 
  In test , create returns success whereas it excepts BadRequest.

  0}
  
neutron_lbaas.tests.tempest.v2.api.test_members.MemberTestJSON.test_create_member_empty_tenant_id
  [0.590837s] ... FAILED

  Captured traceback:
  ~~~
  Traceback (most recent call last):
File neutron_lbaas/tests/tempest/v2/api/test_members.py, line 244, in 
test_create_member_empty_tenant_id
  self.pool_id, **member_opts)
File 
/opt/stack/neutron-lbaas/.tox/tempest/local/lib/python2.7/site-packages/testtools/testcase.py,
 line 422, in assertRaises
  self.assertThat(our_callable, matcher)
File 
/opt/stack/neutron-lbaas/.tox/tempest/local/lib/python2.7/site-packages/testtools/testcase.py,
 line 435, in assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: bound method type._create_member 
of class 'neutron_lbaas.tests.tempest.v2.api.test_members.MemberTestJSON' 
returned {u'protocol_port': 80, u'weight': 1, u'admin_state_up': True, 
u'subnet_id': u'e20c013e-33d0-4752-883d-b78bd45ef0ea', u'tenant_id': u'', 
u'address': u'127.0.0.1', u'id': u'3f8d811f-ab69-44f8-ae18-8fc20a94b228'}

  2.In case of if Backend Driver (Say NetScaler) ,driver   is raising 
BadRequest .
  ==
 return self._callable_object(*self._args, **self._kwargs)
File neutron_lbaas/tests/tempest/v2/api/base.py, line 252, in 
_create_member
  member = cls.members_client.create_member(pool_id, **member_kwargs)
File neutron_lbaas/tests/tempest/v2/clients/members_client.py, line 
51, in create_member
  resp, body = self.post(url, post_body)
File 
/opt/stack/neutron-lbaas/.tox/tempest/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py,
 line 252, in post
  return self.request('POST', url, extra_headers, headers, body)
File 
/opt/stack/neutron-lbaas/.tox/tempest/src/tempest/tempest/common/service_client.py,
 line 83, in request
  raise exceptions.ServerFault(ex)
  tempest.exceptions.ServerFault: Got server fault
  Details: Got server fault
  Details: An error happened in the driver
  ===

  Above behavior is observed as ,at plugin layer all Exceptions from
  Driver is raised as same  Driver Exception.

  plugin.y
   def _call_driver_operation(self, context, driver_method, db_entity,
 old_db_entity=None):
  manager_method = %s.%s % (driver_method.__self__.__class__.__name__,
  driver_method.__name__)
  LOG.info(_LI(Calling driver operation %s) % manager_method)
  try:
  if old_db_entity:
  driver_method(context, old_db_entity, db_entity)
  else:
  driver_method(context, db_entity)
  # catching and reraising agent issues
  except (lbaas_agentschedulerv2.NoEligibleLbaasAgent,
  lbaas_agentschedulerv2.NoActiveLbaasAgent) as no_agent:
  raise no_agent
  except Exception:
  LOG.exception(_LE(There was an error in the driver))
  self._handle_driver_error(context, db_entity)
  raise loadbalancerv2.DriverError()#--  
bad request is raised as Driver Error
 
  Negative Testcases:-

  test_create_listener_invalid_tenant_id()
  test_create_listener_invalid_empty_tenant_id()
  test_create_member_invalid_tenant_id()
  test_create_member_empty_tenant_id()

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1441512/+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 1367132] Re: quota delete api should do better input validation

2015-06-07 Thread Launchpad Bug Tracker
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
   Status: Incomplete = Expired

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

Title:
  quota delete api should do better input validation

Status in OpenStack Compute (Nova):
  Expired

Bug description:
  The quota delete rest api should have better input validation as bad
  input data can currently silently fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1367132/+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 1439861] Re: encrypted iSCSI volume attach fails to attach when multipath-tools installed

2015-06-07 Thread Launchpad Bug Tracker
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
   Status: Incomplete = Expired

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

Title:
  encrypted iSCSI volume attach fails to attach when multipath-tools
  installed

Status in OpenStack Compute (Nova):
  Expired

Bug description:
  An error was occurring in a devstack setup with nova version:

  commit ab25f5f34b6ee37e495aa338aeb90b914f622b9d
  Merge instance termination with update_dns_entries set fails

  A volume-type encrypted with CryptsetupEncryptor was being used.  A
  volume was created using this volume-type and an attempt to attach it
  to an instance was made.  This error also occurred when using the
  LuksEncryptor for the volume-type.

  The following error occurred in n-cpu during attachment:

  Stack Trace:

  2015-04-02 13:39:54.397 ERROR nova.virt.block_device 
[req-a8220e7d-8d1e-459d-be1f-4ddd65b7ff66 admin admin] [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5] Driver failed to attach volume 
81c5f69a-9b01-4f
  c0-a105-be9d3c966aaf at /dev/vdb
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5] Traceback (most recent call last):
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5]   File 
/opt/stack/nova/nova/virt/block_device.py, line 251, in attach
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5] device_type=self['device_type'], 
encryption=encryption)
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5]   File 
/opt/stack/nova/nova/virt/libvirt/driver.py, line 1064, in attach_volume
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5] 
self._disconnect_volume(connection_info, disk_dev)
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5]   File 
/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py, line 85, in 
__exit__
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5] six.reraise(self.type_, self.value, 
self.tb)
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5]   File 
/opt/stack/nova/nova/virt/libvirt/driver.py, line 1051, in attach_volume
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5] encryptor.attach_volume(context, 
**encryption)
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5]   File 
/opt/stack/nova/nova/volume/encryptors/cryptsetup.py, line 93, in 
attach_volume
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5] self._open_volume(passphrase, 
**kwargs)
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5]   File 
/opt/stack/nova/nova/volume/encryptors/cryptsetup.py, line 78, in _open_volume
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5] check_exit_code=True, 
run_as_root=True)
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5]   File /opt/stack/nova/nova/utils.py, 
line 206, in execute
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5] return processutils.execute(*cmd, 
**kwargs)
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5]   File 
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/processutils.py, line 
233, in execute
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5] cmd=sanitized_cmd)
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5] ProcessExecutionError: Unexpected error 
while running command.
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5] Command: sudo nova-rootwrap 
/etc/nova/rootwrap.conf cryptsetup create --key-file=- ip-10.50.3.20:3260-
  
iscsi-iqn.2003-10.com.lefthandnetworks:vsa-12-721:853:volume-81c5f69a-9b01-4fc0-a105-be9d3c966aaf-lun-0
 /dev/sdb
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5] Exit code: 5
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5] Stdout: u''
  2015-04-02 13:39:54.397 TRACE nova.virt.block_device [instance: 
41d0c192-a1ce-45eb-a5ff-bcb96ec0d8e5] Stderr: u'Cannot use device /dev/sdb 
which is in use (already mapped 

[Yahoo-eng-team] [Bug 1462708] Re: Mismatch argument name for keystone create new user

2015-06-07 Thread Boris Bobrov
1. ``keystone'' cli is deprecated, you should use ``openstack'' cli -- 
http://docs.openstack.org/developer/python-openstackclient/.
2. This is a long-standing issue of project vs tenant. In v3 there is 
``project'' everywhere, in v2 there is ``tenant''. ``keystone'' cli uses only 
v2 api, thus ``tenant'' is ok there. Horizon is more up to date.

** Project changed: keystone = python-keystoneclient

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

Title:
  Mismatch argument name for keystone create new user

Status in Python client library for Keystone:
  New

Bug description:
  Command to create new user:
  ~/devstack$ keystone help user-create
  /usr/local/lib/python2.7/dist-packages/keystoneclient/shell.py:65: 
DeprecationWarning: The keystone CLI is deprecated in favor of 
python-openstackclient. For a Python library, continue using 
python-keystoneclient.
'python-keystoneclient.', DeprecationWarning)
  usage: keystone user-create --name user-name [--tenant tenant]
  [--pass [pass]] [--email email]
  [--enabled true|false]

  Create new user.

  Arguments:
--name user-nameNew user name (must be unique).
--tenant tenant, --tenant-id tenant
  New user default tenant.
--pass [pass]   New user password; required for some auth backends.
--email email   New user email address.
--enabled true|false

  we have argument --tenant  name while on horizon dashboard, we have
  field Primary Project with the same function meaning. I think we
  should change to same name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-keystoneclient/+bug/1462708/+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 1462706] Re: Mandatory some fields when create new user by CLI

2015-06-07 Thread Boris Bobrov
``keystone'' cli is deprecated, you should use ``openstack'' cli --
http://docs.openstack.org/developer/python-openstackclient/.

** Project changed: keystone = python-keystoneclient

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

Title:
  Mandatory some fields when create new user by CLI

Status in Python client library for Keystone:
  New

Bug description:
  When create new user on horizon dashboard, some fields Password, Primary 
project are mandatory. However, these fields are optional in CLI. This leads 
that we don't know the password for new user. 
  keystone V2 is used here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-keystoneclient/+bug/1462706/+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