[Yahoo-eng-team] [Bug 1255876] Re: need to ignore swap files from getting into repository

2013-11-29 Thread Julien Danjou
** Changed in: ceilometer
   Status: In Progress => Invalid

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

Title:
  need to ignore swap files from getting into repository

Status in OpenStack Telemetry (Ceilometer):
  Invalid
Status in Heat Orchestration Templates and tools:
  New
Status in OpenStack Dashboard (Horizon):
  Fix Committed
Status in OpenStack Neutron (virtual network service):
  In Progress
Status in Oslo - a Library of Common OpenStack Code:
  In Progress
Status in Python client library for Ceilometer:
  In Progress
Status in Python client library for Cinder:
  In Progress
Status in Python client library for Glance:
  In Progress
Status in Python client library for heat:
  In Progress
Status in Python client library for Keystone:
  In Progress
Status in Python client library for Neutron:
  In Progress
Status in Python client library for Nova:
  In Progress
Status in Python client library for Swift:
  Fix Committed
Status in OpenStack Data Processing (Savanna):
  Invalid

Bug description:
  need to ignore swap files from getting into repository
  currently the implemented ignore in .gitignore is *.swp
  however vim goes beyond to generate these so to improve it could be done *.sw?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1255876/+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 1256043] Re: Need to add Development environment files to ignore list

2013-11-29 Thread Chmouel Boudjnah
** Changed in: python-swiftclient
   Status: In Progress => Won't Fix

** Changed in: swift
   Status: In Progress => Won't Fix

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

Title:
  Need to add Development environment files to ignore list

Status in OpenStack Telemetry (Ceilometer):
  In Progress
Status in OpenStack Dashboard (Horizon):
  Won't Fix
Status in OpenStack Neutron (virtual network service):
  In Progress
Status in Python client library for Ceilometer:
  In Progress
Status in Python client library for Cinder:
  In Progress
Status in Python client library for Glance:
  In Progress
Status in Python client library for heat:
  Won't Fix
Status in Python client library for Keystone:
  In Progress
Status in Python client library for Neutron:
  In Progress
Status in Python client library for Nova:
  In Progress
Status in Python client library for Swift:
  Won't Fix
Status in OpenStack Object Storage (Swift):
  Won't Fix
Status in Tempest:
  In Progress

Bug description:
  Following files generated by Eclipse development environment should be
  in ignore list to avoid their inclusion during a git push.

  .project
  .pydevproject

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1256043/+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 1198809] Re: fake rpc driver should raise timeout exception if no consumers registered

2013-11-29 Thread Mark McLoughlin
oslo-incubator fix is https://review.openstack.org/42739

** Changed in: oslo
   Status: Triaged => Fix Released

** Changed in: nova
   Status: Triaged => 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/1198809

Title:
  fake rpc driver should raise timeout exception if no consumers
  registered

Status in OpenStack Compute (Nova):
  Fix Released
Status in Oslo - a Library of Common OpenStack Code:
  Fix Released

Bug description:
  Seen here: https://review.openstack.org/3274

  If you do a call() with a real driver and no consumer responds, you
  get a timeout exception

  The fake driver should implement these semantics too. The patch is
  simple e.g.

try:
consumer = CONSUMERS[topic][0]
except (KeyError, IndexError):
   -return iter([None])
   +raise rpc_common.Timeout()

  but Nova's unit tests break massively with this change, so they'd need
  to be fixed first

  The oslo.messaging fake driver already does the right thing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1198809/+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 1078055] Re: Some id arguments for OSAPI are not verified to be numeric leading to false matches in mysql

2013-11-29 Thread Francisco Demontiê dos Santos Junior
** Changed in: nova
   Status: Fix Committed => 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/1078055

Title:
  Some id arguments for OSAPI are not verified to be numeric leading to
  false matches in mysql

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  Some id arguments for the OSAPI queries should only take numeric
  arguments, but this is not verified before passing the id to the db
  api. In case of mysql this leads for example to automatic truncation
  of non-numeric characters from the end of the string.

  Lets say there's a floating ip entry with id=123. If you issue a
  request to: "https://api/v1.1/tenant/os-floating-ips/123";, you
  will get the floating ip 123 in response. The following line will be
  logged:

  2012-11-12 18:11:03 WARNING nova.common.deprecated
  [req-21324670-f110-4eb1-8c35-bb1aa5581edb None None] Truncated
  incorrect DOUBLE value: '123'

  Although this is a trivial thing in this example, probably the code should be 
fixed or at least reviewed in case there's a possibility of circumventing some 
security check. (for example if the check passes for non-existant ids, but then 
allows access on a stripped id)
  This bug is likely to happen on more resources than just os-floating-ips.

  I believe this issue happens only with a mysql database, but this may
  not be correct - other ones may have a similar behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1078055/+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 1247142] Re: Live LDAP tests fail when trying to create user with an arbitrary attribute

2013-11-29 Thread Dolph Mathews
The above fix has not been released yet.

** Changed in: keystone
   Status: Fix Released => Fix Committed

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

Title:
  Live LDAP tests fail when trying to create user with an arbitrary
  attribute

Status in OpenStack Identity (Keystone):
  Fix Committed

Bug description:
  I ran _ldap_livetest and it failed with the following traceback:

  FAIL: 
keystone.tests.test_ldap_livetest.LiveLDAPIdentity.test_arbitrary_attributes_are_returned_from_create_user
  tags: worker-0
  --
  Traceback (most recent call last):
File "keystone/tests/test_backend.py", line 2646, in 
test_arbitrary_attributes_are_returned_from_create_user
  user = self.identity_api.create_user(user_data['id'], user_data)
File "keystone/notifications.py", line 44, in wrapper
  result = f(*args, **kwargs)
File "keystone/identity/core.py", line 179, in wrapper
  return f(self, *args, **kwargs)
File "keystone/identity/core.py", line 324, in create_user
  ref = driver.create_user(user_id, user)
File "keystone/identity/backends/ldap.py", line 95, in create_user
  user_ref = self.user.create(user)
File "keystone/identity/backends/ldap.py", line 229, in create
  values = super(UserApi, self).create(values)
File "keystone/common/ldap/core.py", line 738, in create
  ref = super(EnabledEmuMixIn, self).create(values)
File "keystone/common/ldap/core.py", line 342, in create
  conn.add_s(self._id_to_dn(values['id']), attrs)
File "keystone/common/ldap/core.py", line 565, in add_s
  return self.conn.add_s(dn, ldap_attrs)
File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 194, in 
add_s
  return self.result(msgid,all=1,timeout=self.timeout)
File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 422, in 
result
  res_type,res_data,res_msgid = self.result2(msgid,all,timeout)
File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 426, in 
result2
  res_type, res_data, res_msgid, srv_ctrls = self.result3(msgid,all,timeout)
File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 432, in 
result3
  ldap_result = self._ldap_call(self._l.result3,msgid,all,timeout)
File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 96, in 
_ldap_call
  result = func(*args,**kwargs)

  There are four tests in total which work with arbitrary attributes,
  but three of them are skipped in test_backend_ldap:

  def test_arbitrary_attributes_are_returned_from_get_user(self):
  self.skipTest("Using arbitrary attributes doesn't work under LDAP")

  def test_new_arbitrary_attributes_are_returned_from_update_user(self):
  self.skipTest("Using arbitrary attributes doesn't work under LDAP")

  def test_updated_arbitrary_attributes_are_returned_from_update_user(self):
  self.skipTest("Using arbitrary attributes doesn't work under LDAP") 

  So I find it strange that
  test_arbitrary_attributes_are_returned_from_create_user is not skipped
  like these three.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1247142/+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 1253681] Re: Newly-created VPNaaS objects remain in PENDING_CREATE because neutron vpn agent is unauthorized to run openswan's ipsec command

2013-11-29 Thread Rami Vaknin
Ohh, thanks for the pointer, now I see the
${neutron_git}/etc/neutron/rootwrap.d/vpnaas.filters and it solves this
issue, closing this bug.

** Changed in: neutron
   Status: New => Invalid

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

Title:
  Newly-created VPNaaS objects remain in PENDING_CREATE because neutron
  vpn agent is unauthorized to run openswan's ipsec command

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  Version
  ===
  Havana on rhel

  Description
  ===
  I've created ike and ipsec policies, vpn service and ipsec site connections 
with almost all params set as default, it seems like the neutron vpn agent 
fails to run the openswan's ipsec command, the vpn service and the ipsec site 
connections remain in PENDING_CREATE status:

  
  2013-11-21 17:15:15.526 6112 WARNING neutron.context [-] Arguments dropped 
when creating context: {'project_id': u'1532b0139c4f49298dee924500761e6d'}
  2013-11-21 17:15:16.635 6112 ERROR neutron.services.vpn.device_drivers.ipsec 
[-] Failed to enable vpn process on router e8b2c574-0b11-4c96-bed4-731ae6cf0a90
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec 
Traceback (most recent call last):
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec  
 File 
"/usr/lib/python2.6/site-packages/neutron/services/vpn/device_drivers/ipsec.py",
 line 241, in enable
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec  
   self.start()
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec  
 File 
"/usr/lib/python2.6/site-packages/neutron/services/vpn/device_drivers/ipsec.py",
 line 382, in start
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec  
   '--virtual_private', virtual_private
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec  
 File 
"/usr/lib/python2.6/site-packages/neutron/services/vpn/device_drivers/ipsec.py",
 line 311, in _execute
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec  
   check_exit_code=check_exit_code)
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec  
 File "/usr/lib/python2.6/site-packages/neutron/agent/linux/ip_lib.py", line 
458, in execute
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec  
   check_exit_code=check_exit_code)
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec  
 File "/usr/lib/python2.6/site-packages/neutron/agent/linux/utils.py", line 62, 
in execute
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec  
   raise RuntimeError(m)
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec 
RuntimeError: 
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec 
Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 
'netns', 'exec', 'qrouter-e8b2c574-0b11-4c96-bed4-731ae6cf0a90', 'ipsec', 
'pluto', '--ctlbase', 
'/var/lib/neutron/ipsec/e8b2c574-0b11-4c96-bed4-731ae6cf0a90/var/run/pluto', 
'--ipsecdir', 
'/var/lib/neutron/ipsec/e8b2c574-0b11-4c96-bed4-731ae6cf0a90/etc', 
'--use-netkey', '--uniqueids', '--nat_traversal', '--secretsfile', 
'/var/lib/neutron/ipsec/e8b2c574-0b11-4c96-bed4-731ae6cf0a90/etc/ipsec.secrets',
 '--virtual_private', '%v4:10.35.214.0/24,%v4:10.35.214.0/24']
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec 
Exit code: 99
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec 
Stdout: ''
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec 
Stderr: '/usr/bin/neutron-rootwrap: Unauthorized command: ip netns exec 
qrouter-e8b2c574-0b11-4c96-bed4-731ae6cf0a90 ipsec pluto --ctlbase 
/var/lib/neutron/ipsec/e8b2c574-0b11-4c96-bed4-731ae6cf0a90/var/run/pluto 
--ipsecdir /var/lib/neutron/ipsec/e8b2c574-0b11-4c96-bed4-731ae6cf0a90/etc 
--use-netkey --uniqueids --nat_traversal --secretsfile 
/var/lib/neutron/ipsec/e8b2c574-0b11-4c96-bed4-731ae6cf0a90/etc/ipsec.secrets 
--virtual_private %v4:10.35.214.0/24,%v4:10.35.214.0/24 (no filter matched)\n'
  2013-11-21 17:15:16.635 6112 TRACE neutron.services.vpn.device_drivers.ipsec

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