[Yahoo-eng-team] [Bug 1673076] Re: SNAT enable/disable for router gateway

2017-03-15 Thread Victor Morales 
Hey Alam,

Apparently horizon doesn't implement this function[1] because from
neutron's perspective this is supported thru its client[2].  I don't
know the reasons behind that decision.

[1] 
https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/neutron.py#L1063-L1065
[2] 
https://github.com/openstack/python-neutronclient/blob/master/neutronclient/neutron/v2_0/router.py#L276

** Project changed: neutron => 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/1673076

Title:
  SNAT enable/disable for router gateway

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Hello,

  I installed OpenStack via Devstack from Master, but the option for
  SNAT enable/disable for router gateway is not available via dashboard.

  Am I missing a patch here?

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1673076/+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 1668125] Re: Add ability to change default quota

2017-02-27 Thread Victor Morales 
The way to change those values is thru the OSC,:

$ openstack project list
+--++
| ID   | Name   |
+--++
| 49f3e83f85354ee3a0abadcf1e35c9f4 | demo   |
| 5a46e724e04d41beaf365d7148f8f465 | invisible_to_admin |
| 6ebf8c5aadea49fdb6222eae1e1639c0 | admin  |
| 82533c3679a747189c401d42345f75b2 | service|
| a0c776bc0aa645a6845cd7919512ed01 | alt_demo   |
+--++

$ openstack quota set --secgroups 15 49f3e83f85354ee3a0abadcf1e35c9f4

$ openstack quota show 49f3e83f85354ee3a0abadcf1e35c9f4
+---+--+
| Field | Value|
+---+--+
| backup-gigabytes  | 1000 |
| backups   | 10   |
| cores | 20   |
| fixed-ips | -1   |
| floating-ips  | 50   |
| gigabytes | 1000 |
| gigabytes_lvmdriver-1 | -1   |
| health_monitors   | None |
| injected-file-size| 10240|
| injected-files| 5|
| injected-path-size| 255  |
| instances | 10   |
| key-pairs | 100  |
| l7_policies   | None |
| listeners | None |
| load_balancers| None |
| location  | None |
| name  | None |
| networks  | 10   |
| per-volume-gigabytes  | -1   |
| pools | None |
| ports | 50   |
| project   | 49f3e83f85354ee3a0abadcf1e35c9f4 |
| project_id| None |
| properties| 128  |
| ram   | 51200|
| rbac_policies | 10   |
| routers   | 10   |
| secgroup-rules| 100  |
| secgroups | 15   |
| server-group-members  | 10   |
| server-groups | 10   |
| snapshots | 10   |
| snapshots_lvmdriver-1 | -1   |
| subnet_pools  | -1   |
| subnets   | 10   |
| volumes   | 10   |
| volumes_lvmdriver-1   | -1   |
+---+--+

By other hand, python-neutronclient is under a process to be deprecated.
Therefore,  I'm gonna invalidate 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/1668125

Title:
  Add ability to change default quota

Status in neutron:
  Invalid

Bug description:
  Problem:
  Currently, the default quota is defined in configure file of neutron server: 
neutron.conf.
  admin isnot able to change it via API.

  other service nova, cinder can do it by, for example 'nova quota-
  class-update --instances -1 --cores -1 default'

  expectation:
  implement an API to let admin change the default quota. By client, it maybe:
  neutron quota-class-update --ports xx --networks yy --security-groups --zz 
default

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1668125/+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 1666864] Re: function does not return correct create router timestamp

2017-02-22 Thread Victor Morales 
The other thing that I noticed is that the revision_number differs from
the initial version(3) to the latest version(8), isn't another process
doing something in parallel that modifies this object?

** Changed in: neutron
   Status: Incomplete => 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/1666864

Title:
  function does not return correct create router timestamp

Status in neutron:
  Invalid

Bug description:
  Version: OSP-10 Newton
  Test failed : 
neutron.tests.tempest.api.test_timestamp.TestTimeStampWithL3.test_show_router_attribute_with_timestamp

  At creation the timestamp is correct: u'created_at':
  u'2017-02-22T10:47:24Z', u'updated_at': u'2017-02-22T10:47:24Z'

  when "show" function display the timestamp it display it with ~3 sec 
difference:
  u'created_at': u'2017-02-22T10:47:24Z', u'updated_at': u'2017-02-22T10:47:26Z'

  show function display incorrect timestamp

  218 def test_show_router_attribute_with_timestamp(self):
  219 router = self.create_router(router_name='test')
  220 import ipdb;ipdb.set_trace()
  --> 221 body = self.client.show_router(router['id'])
  222 show_router = body['router']
  223 # verify the timestamp from creation and showed is same
  224 import ipdb;ipdb.set_trace()
  225 self.assertEqual(router['created_at'],
  226  show_router['created_at'])

  ipdb> router
  {u'status': u'ACTIVE', u'external_gateway_info': None, 
u'availability_zone_hints': [], u'availability_zones': [], u'description': u'', 
u'admin_state_up': False, u'tenant_id': u'8b9cd1ebd13f4172a0c63789ee9c0de2', 
u'created_at': u'2017-02-22T10:47:24Z', u'updated_at': u'2017-02-22T10:47:24Z', 
u'flavor_id': None, u'revision_number': 3, u'routes': [], u'project_id': 
u'8b9cd1ebd13f4172a0c63789ee9c0de2', u'id': 
u'545e74b0-2f3d-43b8-8678-93bbb3f1f6f3', u'name': u'test'}
  ipdb> n
  2017-02-22 10:47:55.084 6919 INFO tempest.lib.common.rest_client 
[req-eef7ded4-bb01-4401-96cd-325c01b2230b ] Request 
(TestTimeStampWithL3:test_show_router_attribute_with_timestamp): 200 GET 
http://10.0.0.104:9696/v2.0/routers/545e74b0-2f3d-43b8-8678-93bbb3f1f6f3 0.224s
  2017-02-22 10:47:55.086 6919 DEBUG tempest.lib.common.rest_client 
[req-eef7ded4-bb01-4401-96cd-325c01b2230b ] Request - Headers: {'Content-Type': 
'application/json', 'Accept': 'application/json', 'X-Auth-Token': ''}
  Body: None
  Response - Headers: {'status': '200', u'content-length': '462', 
'content-location': 
'http://10.0.0.104:9696/v2.0/routers/545e74b0-2f3d-43b8-8678-93bbb3f1f6f3', 
u'date': 'Wed, 22 Feb 2017 10:47:56 GMT', u'content-type': 'application/json', 
u'connection': 'close', u'x-openstack-request-id': 
'req-eef7ded4-bb01-4401-96cd-325c01b2230b'}
  Body: {"router": {"status": "ACTIVE", "external_gateway_info": null, 
"availability_zone_hints": [], "availability_zones": ["nova"], "description": 
"", "admin_state_up": false, "tenant_id": "8b9cd1ebd13f4172a0c63789ee9c0de2", 
"created_at": "2017-02-22T10:47:24Z", "updated_at": "2017-02-22T10:47:26Z", 
"flavor_id": null, "revision_number": 8, "routes": [], "project_id": 
"8b9cd1ebd13f4172a0c63789ee9c0de2", "id": 
"545e74b0-2f3d-43b8-8678-93bbb3f1f6f3", "name": "test"}} _log_request_full 
tempest/lib/common/rest_client.py:431
  > 
/home/centos/tempest-upstream/neutron/neutron/tests/tempest/api/test_timestamp.py(222)test_show_router_attribute_with_timestamp()

  
  ipdb> router
  {u'status': u'ACTIVE', u'external_gateway_info': None, 
u'availability_zone_hints': [], u'availability_zones': [], u'description': u'', 
u'admin_state_up': False, u'tenant_id': u'8b9cd1ebd13f4172a0c63789ee9c0de2', 
u'created_at': u'2017-02-22T10:47:24Z', u'updated_at': u'2017-02-22T10:47:24Z', 
u'flavor_id': None, u'revision_number': 3, u'routes': [], u'project_id': 
u'8b9cd1ebd13f4172a0c63789ee9c0de2', u'id': 
u'545e74b0-2f3d-43b8-8678-93bbb3f1f6f3', u'name': u'test'}
  ipdb> show_router
  {u'status': u'ACTIVE', u'external_gateway_info': None, 
u'availability_zone_hints': [], u'availability_zones': [u'nova'], 
u'description': u'', u'admin_state_up': False, u'tenant_id': 
u'8b9cd1ebd13f4172a0c63789ee9c0de2', u'created_at': u'2017-02-22T10:47:24Z', 
u'updated_at': u'2017-02-22T10:47:26Z', u'flavor_id': None, u'revision_number': 
8, u'routes': [], u'project_id': u'8b9cd1ebd13f4172a0c63789ee9c0de2', u'id': 
u'545e74b0-2f3d-43b8-8678-93bbb3f1f6f3', u'name': u'test'}
  ipdb>

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1666864/+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 1659321] Re: Failed to start 2 RPC workers

2017-01-25 Thread Victor Morales 
*** This bug is a duplicate of bug 1659146 ***
https://bugs.launchpad.net/bugs/1659146

This bug is duplicated, there is a patch submitted for this: 
https://bugs.launchpad.net/neutron/+bug/1659146

** 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/1659321

Title:
  Failed to start 2 RPC workers

Status in neutron:
  Invalid

Bug description:
  There are some failures during the execution of functional tests that
  with the following stack trace:

  t1.1: 
neutron.tests.functional.test_server.TestRPCServer.test_restart_rpc_on_sighup_multiple_workers_StringException:
 Empty attachments:
stderr
stdout

  pythonlogging:'': {{{
  DEBUG [stevedore.extension] found extension EntryPoint.parse('fake = 
oslo_messaging._drivers.impl_fake:FakeDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('pika = 
oslo_messaging._drivers.impl_pika:PikaDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('zmq = 
oslo_messaging._drivers.impl_zmq:ZmqDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('kombu = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('amqp = 
oslo_messaging._drivers.impl_amqp1:ProtonDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('rabbit = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('kafka = 
oslo_messaging._drivers.impl_kafka:KafkaDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('fake = 
oslo_messaging._drivers.impl_fake:FakeDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('pika = 
oslo_messaging._drivers.impl_pika:PikaDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('zmq = 
oslo_messaging._drivers.impl_zmq:ZmqDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('kombu = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('amqp = 
oslo_messaging._drivers.impl_amqp1:ProtonDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('rabbit = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('kafka = 
oslo_messaging._drivers.impl_kafka:KafkaDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('fake = 
oslo_messaging._drivers.impl_fake:FakeDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('pika = 
oslo_messaging._drivers.impl_pika:PikaDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('zmq = 
oslo_messaging._drivers.impl_zmq:ZmqDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('kombu = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('amqp = 
oslo_messaging._drivers.impl_amqp1:ProtonDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('rabbit = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('kafka = 
oslo_messaging._drivers.impl_kafka:KafkaDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('fake = 
oslo_messaging._drivers.impl_fake:FakeDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('pika = 
oslo_messaging._drivers.impl_pika:PikaDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('zmq = 
oslo_messaging._drivers.impl_zmq:ZmqDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('kombu = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('amqp = 
oslo_messaging._drivers.impl_amqp1:ProtonDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('rabbit = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
 DEBUG [stevedore.extension] found extension EntryPoint.parse('kafka = 
oslo_messaging._drivers.impl_kafka:KafkaDriver')
 DEBUG [oslo_policy._cache_handler] Reloading cached file 
/opt/stack/new/neutron/neutron/tests/etc/policy.json
 DEBUG [oslo_policy.policy] Reloaded policy file: 
/opt/stack/new/neutron/neutron/tests/etc/policy.json
 DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
 DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
 DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
 DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
 DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
 DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
 DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
 DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd

[Yahoo-eng-team] [Bug 1659321] [NEW] Failed to start 2 RPC workers

2017-01-25 Thread Victor Morales 
*** This bug is a duplicate of bug 1659146 ***
https://bugs.launchpad.net/bugs/1659146

Public bug reported:

There are some failures during the execution of functional tests that
with the following stack trace:

t1.1: 
neutron.tests.functional.test_server.TestRPCServer.test_restart_rpc_on_sighup_multiple_workers_StringException:
 Empty attachments:
  stderr
  stdout

pythonlogging:'': {{{
DEBUG [stevedore.extension] found extension EntryPoint.parse('fake = 
oslo_messaging._drivers.impl_fake:FakeDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('pika = 
oslo_messaging._drivers.impl_pika:PikaDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('zmq = 
oslo_messaging._drivers.impl_zmq:ZmqDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('kombu = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('amqp = 
oslo_messaging._drivers.impl_amqp1:ProtonDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('rabbit = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('kafka = 
oslo_messaging._drivers.impl_kafka:KafkaDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('fake = 
oslo_messaging._drivers.impl_fake:FakeDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('pika = 
oslo_messaging._drivers.impl_pika:PikaDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('zmq = 
oslo_messaging._drivers.impl_zmq:ZmqDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('kombu = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('amqp = 
oslo_messaging._drivers.impl_amqp1:ProtonDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('rabbit = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('kafka = 
oslo_messaging._drivers.impl_kafka:KafkaDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('fake = 
oslo_messaging._drivers.impl_fake:FakeDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('pika = 
oslo_messaging._drivers.impl_pika:PikaDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('zmq = 
oslo_messaging._drivers.impl_zmq:ZmqDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('kombu = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('amqp = 
oslo_messaging._drivers.impl_amqp1:ProtonDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('rabbit = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('kafka = 
oslo_messaging._drivers.impl_kafka:KafkaDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('fake = 
oslo_messaging._drivers.impl_fake:FakeDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('pika = 
oslo_messaging._drivers.impl_pika:PikaDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('zmq = 
oslo_messaging._drivers.impl_zmq:ZmqDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('kombu = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('amqp = 
oslo_messaging._drivers.impl_amqp1:ProtonDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('rabbit = 
oslo_messaging._drivers.impl_rabbit:RabbitDriver')
   DEBUG [stevedore.extension] found extension EntryPoint.parse('kafka = 
oslo_messaging._drivers.impl_kafka:KafkaDriver')
   DEBUG [oslo_policy._cache_handler] Reloading cached file 
/opt/stack/new/neutron/neutron/tests/etc/policy.json
   DEBUG [oslo_policy.policy] Reloaded policy file: 
/opt/stack/new/neutron/neutron/tests/etc/policy.json
   DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
   DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
   DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
   DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
   DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
   DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
   DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
   DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
   DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
   DEBUG [neutron.agent.ovsdb.native.vlog] [POLLIN] on fd 14
}}}

Traceback (most recent call last):
  File "neutron/tests/base.py", line 115, in func
return f(self, *args, **kwargs)
  File "neutron/tests/functional/test_server.py", line 253, in 
test_restart_rpc_on_sighup_multiple_workers
workers=2)
  File "neutron/tests/functional/test_server.py", line 141, in 
_test_restart_service_on_sighup

[Yahoo-eng-team] [Bug 1622672] [NEW] Unknown filters aren't validated by the API

2016-09-12 Thread Victor Morales 
Public bug reported:

During the integration of Subnet Olso-Versioned Object, Artur
discovered[1] that there are some cases where the API receives filters
which are not defined in the model. It's necessary to modify the current
implementation of OVO to support cases like:

* Using 'admin_state_up' in Subnet model class.
* Using 'network_id' and 'router:external' as filters for Network model class.

[1] http://lists.openstack.org/pipermail/openstack-
dev/2016-July/100286.html

** Affects: neutron
 Importance: Wishlist
 Assignee: Victor Morales (electrocucaracha)
 Status: In Progress

** Changed in: neutron
 Assignee: (unassigned) => Victor Morales (electrocucaracha)

** Changed in: neutron
   Status: New => In Progress

** Changed in: neutron
   Importance: Undecided => Wishlist

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

Title:
  Unknown filters aren't validated by the API

Status in neutron:
  In Progress

Bug description:
  During the integration of Subnet Olso-Versioned Object, Artur
  discovered[1] that there are some cases where the API receives filters
  which are not defined in the model. It's necessary to modify the
  current implementation of OVO to support cases like:

  * Using 'admin_state_up' in Subnet model class.
  * Using 'network_id' and 'router:external' as filters for Network model class.

  [1] http://lists.openstack.org/pipermail/openstack-
  dev/2016-July/100286.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1622672/+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 1611546] [NEW] db_models.rst isn't included in any toctree

2016-08-09 Thread Victor Morales 
Public bug reported:

Neutron documentation warnings are treated them as errors.

$ sphinx-build -W -b html doc/source doc/build/html 

   18:00:59
Running Sphinx v1.2.3
fatal: unknown date format local -
loading pickled environment... not yet created
Using openstack theme from 
/Users/vjmorale/src/vagrant-intel-devstack/stack/neutron/.venv/lib/python2.7/site-packages/oslosphinx/theme
building [html]: targets for 57 source files that are out of date
updating environment: 57 added, 0 changed, 0 removed
reading sources... [100%] stadium/sub_projects  


 
looking for now-outdated files... none found
pickling environment... done
checking consistency... 
Warning, treated as error:
/Users/vjmorale/src/vagrant-intel-devstack/stack/neutron/doc/source/devref/db_models.rst::
 WARNING: document isn't included in any toctree

** Affects: neutron
 Importance: Undecided
 Assignee: Victor Morales (electrocucaracha)
 Status: In Progress


** Tags: doc

** Changed in: neutron
 Assignee: (unassigned) => Victor Morales (electrocucaracha)

** Changed in: neutron
   Status: New => 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/1611546

Title:
  db_models.rst isn't included in any toctree

Status in neutron:
  In Progress

Bug description:
  Neutron documentation warnings are treated them as errors.

  $ sphinx-build -W -b html doc/source doc/build/html   

 18:00:59
  Running Sphinx v1.2.3
  fatal: unknown date format local -
  loading pickled environment... not yet created
  Using openstack theme from 
/Users/vjmorale/src/vagrant-intel-devstack/stack/neutron/.venv/lib/python2.7/site-packages/oslosphinx/theme
  building [html]: targets for 57 source files that are out of date
  updating environment: 57 added, 0 changed, 0 removed
  reading sources... [100%] stadium/sub_projects


   
  looking for now-outdated files... none found
  pickling environment... done
  checking consistency... 
  Warning, treated as error:
  
/Users/vjmorale/src/vagrant-intel-devstack/stack/neutron/doc/source/devref/db_models.rst::
 WARNING: document isn't included in any toctree

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1611546/+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 1610041] Re: If a user has no admin role, how to get all share network ip availabilities

2016-08-05 Thread Victor Morales 
IMHO this is an expected behavior, according to the policy.json file
whatever user can get shared networks[1][2] but only admins can IP
availabilites[1].  You can change that behavior changing policy rules.

[1] https://github.com/openstack/neutron/blob/master/etc/policy.json#L41
[2] https://github.com/openstack/neutron/blob/master/etc/policy.json#L10
[3] https://github.com/openstack/neutron/blob/master/etc/policy.json#L48

** Changed in: neutron
   Status: Incomplete => 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/1610041

Title:
  If a user has no admin role,how to get all share network ip
  availabilities

Status in neutron:
  Invalid

Bug description:
  For user who doesn't have admin role, he / she can get other projects
  shared networks, but can not to get ip availabilities

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1610041/+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 1609932] Re: Added API extensions to detect sorting/pagination features

2016-08-04 Thread Victor Morales 
** Also affects: openstack-api-site
   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/1609932

Title:
  Added API extensions to detect sorting/pagination features

Status in neutron:
  New
Status in openstack-api-site:
  New

Bug description:
  https://review.openstack.org/329474
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit 5e0878f476d7116bc4e0c29c7929718f379b36c2
  Author: Ihar Hrachyshka 
  Date:   Tue Jun 14 16:16:06 2016 +0200

  Added API extensions to detect sorting/pagination features
  
  Those features are available only when allow_sorting and
  allow_pagination options are enabled (the current default is False).
  
  They don't depend on plugin support, because when plugins don't
  implement them natively, emulated mode is applied by API router itself.
  So to make it plugin agnostic, we introduce a way to register custom
  per-extension checks to override support detection for cases like that
  one.
  
  Now that we have a way to detect support for those features via API,
  there is little reason to keep tempest configuration options to enable
  those features. Instead, just inspect [network-feature-enabled]
  api_extensions option in tempest.conf.
  
  Now that DEFAULT_ALLOW_SORTING/DEFAULT_ALLOW_PAGINATION constants are
  used in a single place only (in allow_sorting/allow_pagination
  definitions), removed them and replaced with a literal.
  
  Added first in-tree API tests for /extensions entry point.
  
  DocImpact Update API documentation to cover new extensions.
  APIImpact Document the new extensions.
  Related-Bug: #1566514
  Change-Id: I0037a8ad52060a68dd75c0a1accc6add238e

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1609932/+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 1609934] Re: Enable sorting and pagination by default

2016-08-04 Thread Victor Morales 
** Also affects: openstack-api-site
   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/1609934

Title:
  Enable sorting and pagination by default

Status in neutron:
  New
Status in openstack-api-site:
  New

Bug description:
  https://review.openstack.org/329481
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit 9733cc25522b1cef83d090617a425efc5364d35b
  Author: Ihar Hrachyshka 
  Date:   Tue Jun 14 16:27:51 2016 +0200

  Enable sorting and pagination by default
  
  Now that we have a decent api test coverage for those features, as well
  as a way to detect the features via REST API, we should be safe and
  thrilled to enable them by default in all installations.
  
  Depends-On: I0037a8ad52060a68dd75c0a1accc6add238e
  Depends-On: I5e68f471a641a34100aba31cb2c4a815c7220014
  Depends-On: I648851b48d0481c97054e1280b60a119b42dfd38
  Depends-On: Ic04cd125dd715ae0694fbf24d8193abe3151ffd1
  Depends-On: Ib3709d15fd87b93285dadf78cce73ee37e8898e2
  Depends-On: Ie3a66d2a7c05143df3da1c56c8e8a5308d4bae91
  
  DocImpact Update configuration documentation to cover new defaults.
  UpgradeImpact To retain the original default behaviour, set
allow_sorting and allow_pagination to False.
  
  Closes-Bug: #1566514
  Change-Id: I3820bec029b3895913b034b718116c95b4942ed0

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1609934/+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 1609090] Re: [ovs firewall] VM can't be reached regardless of security group with icmp allowed

2016-08-03 Thread Victor Morales 
I tried to reproduce the issue with the script that you provide.  I have
some comments on that.  The first one is to add the --poll argument in
nova boot command, this is useful for waiting until the VM is ready.

nova boot "$VM" --flavor m1.tiny --image "$IMG" --nic net-name=$INT
--security-groups $SECGROUP --poll

The other one, is regarding the validation that you have for reusing
Floating IPs, it seems to fail when there is more than one available.

Regarding accessing that VMs thru ssh and doing ping, I didn't have
troubles to do it.  I changed the configuration option and restarted the
agent service, so maybe it's your environment.

** 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/1609090

Title:
  [ovs firewall] VM can't be reached regardless of security group with
  icmp allowed

Status in neutron:
  Invalid

Bug description:
  Reproduced on upstream devstack.

  /etc/neutron/plugins/ml2/ml2_conf.ini has

  [securitygroup]
  firewall_driver = openvswitch

  The issue was triggered by the following script
  http://paste.openstack.org/show/545720/ (output from reproduction
  http://paste.openstack.org/show/545724/)

  Steps to reproduce:
  1. create internal network and router connected to this network; set devstack 
public network as gateway.
  2. create security group with ping/ssh allowed.
  3. boot vm with security group from step 2
  4. try to ping created vm

  Will result in Destination Host Unreachable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1609090/+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 1608332] Re: create pool api parameter issue

2016-08-01 Thread Victor Morales 
** Also affects: openstack-api-site
   Importance: Undecided
   Status: New

** No longer affects: openstack-api-site

** Project changed: neutron => openstack-api-site

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

Title:
  create pool api parameter issue

Status in openstack-api-site:
  New

Bug description:
  There is a bug in the documentation[1] for lbaas v2 pool create
  parameters.  The request parameter mentioned are

  {
  "pool": {
  "admin_state_up": true,
  "description": "simple pool",
  "lb_algorithm": "ROUND_ROBIN",
  "name": "my-pool",
  "protocol": "HTTP",
  "subnet_id": "e301aed0-d9e7-498a-977c-1bbfaf14ed5d"
  }
  }

  The creation of pool requires a listener ID instead of Subnet Id.

  [1] http://developer.openstack.org/api-
  ref/networking/v2-ext/index.html?expanded=create-a-load-balancer-pool-
  detail#id355

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-api-site/+bug/1608332/+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 1571839] [NEW] NoSuchOptError: no such option in group neutron: auth_plugin

2016-04-18 Thread Victor Morales 
Public bug reported:

After this  change[1], auth_type configuration value is used instead of
auth_plugin, resulting in a deprecated value in the code[2]

[1] 
https://github.com/openstack/keystoneauth/commit/a56ed4218aef5a2e528aa682cea967e767dca923
[2] 
https://github.com/openstack/nova/blob/2bda625935f04f03622ac24eb5ad67e81bc748a1/nova/network/neutronv2/api.py#L107

** Affects: nova
 Importance: Undecided
 Assignee: Victor Morales (electrocucaracha)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Victor Morales (electrocucaracha)

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

Title:
  NoSuchOptError: no such option in group neutron: auth_plugin

Status in OpenStack Compute (nova):
  New

Bug description:
  After this  change[1], auth_type configuration value is used instead
  of auth_plugin, resulting in a deprecated value in the code[2]

  [1] 
https://github.com/openstack/keystoneauth/commit/a56ed4218aef5a2e528aa682cea967e767dca923
  [2] 
https://github.com/openstack/nova/blob/2bda625935f04f03622ac24eb5ad67e81bc748a1/nova/network/neutronv2/api.py#L107

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1571839/+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 1563149] [NEW] NeutronSyntheticFieldMultipleForeignKeys message is producing an error

2016-03-28 Thread Victor Morales 
Public bug reported:

There is a business logic that validates the number of foreign keys[1]
on the computer object.  It message contains a parsing format error [2],
the variable must be field instead of fields.

[1] 
https://github.com/openstack/neutron/blob/d27b27c183828b17aabfd736d5251e3f408a199d/neutron/objects/base.py#L301
[2] 
https://github.com/openstack/neutron/blob/d27b27c183828b17aabfd736d5251e3f408a199d/neutron/objects/base.py#L58-L59

** Affects: neutron
 Importance: Undecided
 Assignee: Victor Morales (electrocucaracha)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) => Victor Morales (electrocucaracha)

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

Title:
  NeutronSyntheticFieldMultipleForeignKeys message is producing an error

Status in neutron:
  New

Bug description:
  There is a business logic that validates the number of foreign keys[1]
  on the computer object.  It message contains a parsing format error
  [2], the variable must be field instead of fields.

  [1] 
https://github.com/openstack/neutron/blob/d27b27c183828b17aabfd736d5251e3f408a199d/neutron/objects/base.py#L301
  [2] 
https://github.com/openstack/neutron/blob/d27b27c183828b17aabfd736d5251e3f408a199d/neutron/objects/base.py#L58-L59

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1563149/+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 1559191] [NEW] TestParseOneVlanRange fails in python3.5

2016-03-19 Thread Victor Morales 
Public bug reported:

I know that python 3.5 is out of the scope but I noticed that this is
the only unit test that fails in that version.  In order to setup my
env, I had to change the values of python3.4 for python3.5 in tox.ini
file.

(py35)$ testr run TestParseOneVlanRange
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit} --list 
Guru mediation now registers SIGUSR1 and SIGUSR2 by default for backward 
compatibility. SIGUSR1 will no longer be registered in a future release, so 
please use SIGUSR2 to generate reports.
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit}  --load-list 
/var/folders/53/4xjcqmt56fb8bswzn3v4q5h8gp/T/tmpyr72wx3d
Guru mediation now registers SIGUSR1 and SIGUSR2 by default for backward 
compatibility. SIGUSR1 will no longer be registered in a future release, so 
please use SIGUSR2 to generate reports.
==
FAIL: 
neutron.tests.unit.common.test_utils.TestParseOneVlanRange.test_parse_one_net_incomplete_range
tags: worker-0
--
Empty attachments:
  pythonlogging:''
  stderr
  stdout

Traceback (most recent call last):
  File "/opt/stack/neutron/neutron/tests/unit/common/test_utils.py", line 271, 
in test_parse_one_net_incomplete_range
self.assertEqual(str(err), expected_msg)
  File 
"/opt/stack/neutron/.tox/py35/lib/python3.5/site-packages/testtools/testcase.py",
 line 362, in assertEqual
self.assertThat(observed, matcher, message)
  File 
"/opt/stack/neutron/.tox/py35/lib/python3.5/site-packages/testtools/testcase.py",
 line 447, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: !=:
reference = "Invalid network VLAN range: 'net1:100' - 'not enough values to 
unpack (expected 3, got 2)'."
actual= "Invalid network VLAN range: 'net1:100' - 'need more than 2 values 
to unpack'."
sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=1 
encoding='UTF-8'>
Ran 9 tests in 0.246s (-0.097s)
FAILED (id=72, failures=1)

** Affects: neutron
 Importance: Undecided
 Assignee: Victor Morales (electrocucaracha)
 Status: In Progress

** Changed in: neutron
 Assignee: (unassigned) => Victor Morales (electrocucaracha)

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

Title:
  TestParseOneVlanRange fails in python3.5

Status in neutron:
  In Progress

Bug description:
  I know that python 3.5 is out of the scope but I noticed that this is
  the only unit test that fails in that version.  In order to setup my
  env, I had to change the values of python3.4 for python3.5 in tox.ini
  file.

  (py35)$ testr run TestParseOneVlanRange
  running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit} --list 
  Guru mediation now registers SIGUSR1 and SIGUSR2 by default for backward 
compatibility. SIGUSR1 will no longer be registered in a future release, so 
please use SIGUSR2 to generate reports.
  running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit}  --load-list 
/var/folders/53/4xjcqmt56fb8bswzn3v4q5h8gp/T/tmpyr72wx3d
  Guru mediation now registers SIGUSR1 and SIGUSR2 by default for backward 
compatibility. SIGUSR1 will no longer be registered in a future release, so 
please use SIGUSR2 to generate reports.
  ==
  FAIL: 
neutron.tests.unit.common.test_utils.TestParseOneVlanRange.test_parse_one_net_incomplete_range
  tags: worker-0
  --
  Empty attachments:
pythonlogging:''
stderr
stdout

  Traceback (most recent call last):
File "/opt/stack/neutron/neutron/tests/unit/common/test_utils.py", line 
271, in test_parse_one_net_incomplete_range
  self.assertEqual(str(err), expected_msg)
File 
"/opt/stack/neutron/.tox/py35/lib/python3.5/site-packages/testtools/testcase.py",
 line 362, in assertEqual
  self.assertThat(observed, matcher, message)
File 
"/opt/stack/neutron/.tox/py35/lib/python3.5/site-packages/testtools/testcase.py",
 line 447, in assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: !=:
  reference = "Invalid network VLAN range: 'net1:100' - 'not enough values to 
unpack (expected 3, got 2)'."
  actual= "Invalid network VLAN range: 'net1:100' - 'need more than 2 
values to unpack'."
  sys:1:

[Yahoo-eng-team] [Bug 1547164] [NEW] Documentation warning on openvswitch_firewall.rst

2016-02-18 Thread Victor Morales 
Public bug reported:

After executing :

$ tox -e doc

I'm  getting the following warning:

reading sources... [100%] stadium/sub_projects


Warning, treated as error:
/opt/stack/neutron/doc/source/devref/openvswitch_firewall.rst:25: WARNING: 
Title underline too short.

Open vSwitch Firewall Driver
===

** Affects: neutron
 Importance: Undecided
 Assignee: Victor Morales (electrocucaracha)
 Status: In Progress

** Changed in: neutron
 Assignee: (unassigned) => Victor Morales (electrocucaracha)

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

Title:
  Documentation warning on openvswitch_firewall.rst

Status in neutron:
  In Progress

Bug description:
  After executing :

  $ tox -e doc

  I'm  getting the following warning:

  reading sources... [100%] stadium/sub_projects

  
  Warning, treated as error:
  /opt/stack/neutron/doc/source/devref/openvswitch_firewall.rst:25: WARNING: 
Title underline too short.

  Open vSwitch Firewall Driver
  ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1547164/+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 1540525] [NEW] DB diagram is not displayed in the documentation

2016-02-01 Thread Victor Morales 
Public bug reported:

Having  the current database diagram in the documentation is something
necessary for developers, operators and testers.  Given the nature of
the project and the constantly changes it's difficult to track changes
and keep them in the repository, therefore the process to created this
schema must be automated.

Neutron is not the only project that lacks of this documentation but
it's a good candidate to start this initiative.

** Affects: neutron
 Importance: Undecided
 Assignee: Victor Morales (electrocucaracha)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) => Victor Morales (electrocucaracha)

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

Title:
  DB diagram is not displayed in the documentation

Status in neutron:
  New

Bug description:
  Having  the current database diagram in the documentation is something
  necessary for developers, operators and testers.  Given the nature of
  the project and the constantly changes it's difficult to track changes
  and keep them in the repository, therefore the process to created this
  schema must be automated.

  Neutron is not the only project that lacks of this documentation but
  it's a good candidate to start this initiative.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1540525/+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 1487728] [NEW] ldap and ldappool modules are no listed in requirements file

2015-08-22 Thread Victor Morales 
Public bug reported:

Configuring LDAP as assignment backend driver is causing some import
modules errors.  After reviewing the requirements.txt file, those
dependencies are not listed there, but those dependencies are listed in
requirements repo.

** Affects: keystone
 Importance: Undecided
 Assignee: Victor Morales (electrocucaracha)
 Status: New

** Changed in: keystone
 Assignee: (unassigned) = Victor Morales (electrocucaracha)

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

Title:
  ldap and ldappool modules are no listed in requirements file

Status in Keystone:
  New

Bug description:
  Configuring LDAP as assignment backend driver is causing some import
  modules errors.  After reviewing the requirements.txt file, those
  dependencies are not listed there, but those dependencies are listed
  in requirements repo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1487728/+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 1369390] [NEW] Fails to start a server providing the configuration file

2014-09-14 Thread Victor Morales 
Public bug reported:

Using glance-control api start etc/glance-api.conf or glance-control
registry start etc/glance-registry.conf, it's resulting in the
following error:

Traceback (most recent call last):
  File /home/vagrant/glance/.venv/bin/glance-control, line 10, in module
sys.exit(main())
  File /home/vagrant/glance/glance/cmd/control.py, line 354, in main
pid = do_start('Start', *args)
  File /home/vagrant/glance/glance/cmd/control.py, line 199, in do_start
return launch(pid_file, conf_file, CONF.capture_output, CONF.await_child)
  File /home/vagrant/glance/glance/cmd/control.py, line 163, in launch
msg += 'with %s' % conf_file
  File 
/home/vagrant/glance/.venv/local/lib/python2.7/site-packages/oslo/i18n/_message.py,
 line 154, in __add__
raise TypeError(msg)
TypeError

This is because the variable msg is an instance of
oslo.i18n._message.Message which not support concatenation.


https://github.com/openstack/glance/blob/master/glance/cmd/control.py#L163
https://github.com/openstack/oslo.i18n/blob/master/oslo/i18n/_message.py#L151-154

** Affects: glance
 Importance: Undecided
 Status: New

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

Title:
  Fails to start a server providing the configuration file

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  Using glance-control api start etc/glance-api.conf or glance-
  control registry start etc/glance-registry.conf, it's resulting in
  the following error:

  Traceback (most recent call last):
File /home/vagrant/glance/.venv/bin/glance-control, line 10, in module
  sys.exit(main())
File /home/vagrant/glance/glance/cmd/control.py, line 354, in main
  pid = do_start('Start', *args)
File /home/vagrant/glance/glance/cmd/control.py, line 199, in do_start
  return launch(pid_file, conf_file, CONF.capture_output, CONF.await_child)
File /home/vagrant/glance/glance/cmd/control.py, line 163, in launch
  msg += 'with %s' % conf_file
File 
/home/vagrant/glance/.venv/local/lib/python2.7/site-packages/oslo/i18n/_message.py,
 line 154, in __add__
  raise TypeError(msg)
  TypeError

  This is because the variable msg is an instance of
  oslo.i18n._message.Message which not support concatenation.

  
  https://github.com/openstack/glance/blob/master/glance/cmd/control.py#L163
  
https://github.com/openstack/oslo.i18n/blob/master/oslo/i18n/_message.py#L151-154

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1369390/+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 1366361] [NEW] sqlite database should be used by default during development

2014-09-06 Thread Victor Morales 
Public bug reported:

Some other OpenStack components, for example Keystone, have configured a
sqlite file as default option.  But, this default option is not present
in glance.  Having this default option will reduce steps to configure a
development environment

** Affects: glance
 Importance: Undecided
 Assignee: Victor Morales (electrocucaracha)
 Status: New

** Changed in: glance
 Assignee: (unassigned) = Victor Morales (electrocucaracha)

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

Title:
  sqlite database should be used by default during development

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  Some other OpenStack components, for example Keystone, have configured
  a sqlite file as default option.  But, this default option is not
  present in glance.  Having this default option will reduce steps to
  configure a development environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1366361/+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 1347976] [NEW] sqlite files should be excluded from the scope of the repo

2014-07-23 Thread Victor Morales 
Public bug reported:

By default, the sql engine used by all the openstack components is
sqlite. Its simplicity helps during development/coding phases to avoid
additional dependencies like MySQL or others.  In order to store the
data this engine uses text files, but currently it's not part of the
excluded files of the repo within .gitignore file. Adding this file
could avoid the submission of keystone.db file and others by mistake.

** Affects: keystone
 Importance: Undecided
 Assignee: Victor Morales (electrocucaracha)
 Status: New

** Changed in: keystone
 Assignee: (unassigned) = Victor Morales (electrocucaracha)

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

Title:
  sqlite files should be excluded from the scope of the repo

Status in OpenStack Identity (Keystone):
  New

Bug description:
  By default, the sql engine used by all the openstack components is
  sqlite. Its simplicity helps during development/coding phases to avoid
  additional dependencies like MySQL or others.  In order to store the
  data this engine uses text files, but currently it's not part of the
  excluded files of the repo within .gitignore file. Adding this file
  could avoid the submission of keystone.db file and others by mistake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1347976/+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 1261893] Re: glance image-create --location doesn't fail with bad URLs

2013-12-27 Thread Victor Morales 
** Also 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/1261893

Title:
  glance image-create --location doesn't fail with bad URLs

Status in OpenStack Dashboard (Horizon):
  New
Status in Python client library for Glance:
  New

Bug description:
  I ran the command below, then realized that the URL is bad, there's no
  server there. Instead of throwing an error, it blindly created another
  image of size ''. Didn't see anything in the recent commits for it,
  this is on Ubuntu 12.04.

   python-glanceclient  1:0.11.0-0ubuntu1~cloud0
  Client library for Openstack glance server.

  
  root@larry:~# glance image-create --name cirros --is-public true 
--container-format bare --disk-format qcow2 --location 
http://10.0.0.1:9630/isos/cirros-0.3.0-x86_64-disk.img
  +--+--+
  | Property | Value|
  +--+--+
  | checksum | None |
  | container_format | bare |
  | created_at   | 2013-12-17T19:20:57  |
  | deleted  | False|
  | deleted_at   | None |
  | disk_format  | qcow2|
  | id   | 93ca9d12-f9c9-4ef1-a12a-192cc2251da3 |
  | is_public| True |
  | min_disk | 0|
  | min_ram  | 0|
  | name | cirros   |
  | owner| 9db5a2b06743410eb506384f19ae7db7 |
  | protected| False|
  | size | 0|
  | status   | active   |
  | updated_at   | 2013-12-17T19:20:57  |
  +--+--+
  root@larry:~# glance image-list
  
+--++-+--+--++
  | ID   | Name   | Disk Format | Container 
Format | Size | Status |
  
+--++-+--+--++
  | 93ca9d12-f9c9-4ef1-a12a-192cc2251da3 | cirros | qcow2   | bare  
   |  | active |
  
+--++-+--+--++

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