from:"Doug Hellmann"

[Yahoo-eng-team] [Bug 1696866] Re: Cinder LVM driver and ipv6 broken

2018-01-22 Thread Doug Hellmann

** Changed in: oslo.config
   Status: New => Incomplete

** Changed in: oslo.config
   Status: Incomplete => Invalid

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

Title:
  Cinder LVM driver and ipv6 broken

Status in Cinder:
  Incomplete
Status in OpenStack Compute (nova):
  Invalid
Status in oslo.config:
  Invalid
Status in tripleo:
  Fix Released

Bug description:
  The following traceback is seen in the cinder volume logs if you
  deploy with the default LVM driver and ipv6:

  2017-06-08 21:50:40.665 38554 CRITICAL cinder 
[req-a7aff57e-2042-48f2-b1eb-962f79ccda01 - - - - -] ConfigFileValueError: 
Value for option iscsi_ip_address is not valid: [fd00:fd00:fd00:3000::12] is 
not a valid host address
  2017-06-08 21:50:40.665 38554 ERROR cinder Traceback (most recent call last):
  2017-06-08 21:50:40.665 38554 ERROR cinder   File "/usr/bin/cinder-volume", 
line 10, in 
  2017-06-08 21:50:40.665 38554 ERROR cinder sys.exit(main())
  2017-06-08 21:50:40.665 38554 ERROR cinder   File 
"/usr/lib/python2.7/site-packages/cinder/cmd/volume.py", line 120, in main
  2017-06-08 21:50:40.665 38554 ERROR cinder launcher.wait()
  2017-06-08 21:50:40.665 38554 ERROR cinder   File 
"/usr/lib/python2.7/site-packages/oslo_service/service.py", line 581, in wait
  2017-06-08 21:50:40.665 38554 ERROR cinder self.conf.log_opt_values(LOG, 
logging.DEBUG)
  2017-06-08 21:50:40.665 38554 ERROR cinder   File 
"/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2799, in 
log_opt_values
  2017-06-08 21:50:40.665 38554 ERROR cinder _sanitize(opt, 
getattr(group_attr, opt_name)))
  2017-06-08 21:50:40.665 38554 ERROR cinder   File 
"/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 3277, in __getattr__
  2017-06-08 21:50:40.665 38554 ERROR cinder return self._conf._get(name, 
self._group)
  2017-06-08 21:50:40.665 38554 ERROR cinder   File 
"/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2841, in _get
  2017-06-08 21:50:40.665 38554 ERROR cinder value = self._do_get(name, 
group, namespace)
  2017-06-08 21:50:40.665 38554 ERROR cinder   File 
"/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2884, in _do_get
  2017-06-08 21:50:40.665 38554 ERROR cinder % (opt.name, str(ve)))
  2017-06-08 21:50:40.665 38554 ERROR cinder ConfigFileValueError: Value for 
option iscsi_ip_address is not valid: [fd00:fd00:fd00:3000::12] is not a valid 
host address

  The problem appears to be that we bracket the value.  If I remove the
  brackets then cinder volume works correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1696866/+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 1427665] Re: AttributeError: 'RequestContext' object has no attribute 'user_id'

2018-01-22 Thread Doug Hellmann

** Changed in: oslo.log
   Status: New => Invalid

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

Title:
  AttributeError: 'RequestContext' object has no attribute 'user_id'

Status in OpenStack Compute (nova):
  Invalid
Status in oslo.log:
  Invalid

Bug description:
  Example from:
  
http://logs.openstack.org/47/122347/16/check/check-tempest-dsvm-full/e958fa0/logs/screen-n-cpu.txt.gz

  Traceback (most recent call last):
File "/usr/lib/python2.7/logging/__init__.py", line 851, in emit
  msg = self.format(record)
File "/usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py", line 
69, in format
  return logging.StreamHandler.format(self, record)
File "/usr/lib/python2.7/logging/__init__.py", line 724, in format
  return fmt.format(record)
File "/usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py", line 
178, in format
  context = _update_record_with_context(record)
File "/usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py", line 
56, in _update_record_with_context
  d = _dictify_context(context)
File "/usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py", line 
31, in _dictify_context
  context = context.to_dict()
File "/opt/stack/new/nova/nova/context.py", line 157, in to_dict
  values.update({'user_id': self.user_id,
  AttributeError: 'RequestContext' object has no attribute 'user_id'
  Logged from file context.py, line 97

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1427665/+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 1230360] Re: keystone-all --log-file logs to stdout

2018-01-22 Thread Doug Hellmann

The default for use_stderr was changed to False.

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

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

Title:
  keystone-all --log-file logs to stdout

Status in OpenStack Identity (keystone):
  Invalid
Status in oslo.log:
  Fix Released

Bug description:
  The help text for keystone-all says if I set --log-file then logging
  goes to the output file, otherwise it goes to stdout. But logging goes
  to stdout whether I set --log-file or not.

  Here's the output without --log-file:

  $ tools/with_venv.sh bin/keystone-all
  2013-09-25 10:35:40.229 3406 INFO keystone.common.environment [-] Environment 
configured as: eventlet
  2013-09-25 10:35:40.652 3406 WARNING keystone.token.provider [-] 
keystone.conf [signing] token_format is deprecated in favor of keystone.conf 
[token] provider
  2013-09-25 10:35:40.747 3406 INFO keystone.common.environment.eventlet_server 
[-] Starting bin/keystone-all on 0.0.0.0:35357
  2013-09-25 10:35:40.751 3406 INFO keystone.common.environment.eventlet_server 
[-] Starting bin/keystone-all on 0.0.0.0:5000

  Here's the output with --log-file:

  $ tools/with_venv.sh bin/keystone-all --log-file /tmp/keystone-log1.txt
  2013-09-25 10:35:54.747 3425 INFO keystone.common.environment [-] Environment 
configured as: eventlet
  2013-09-25 10:35:55.168 3425 WARNING keystone.token.provider [-] 
keystone.conf [signing] token_format is deprecated in favor of keystone.conf 
[token] provider
  2013-09-25 10:35:55.262 3425 INFO keystone.common.environment.eventlet_server 
[-] Starting bin/keystone-all on 0.0.0.0:35357
  2013-09-25 10:35:55.266 3425 INFO keystone.common.environment.eventlet_server 
[-] Starting bin/keystone-all on 0.0.0.0:5000

  I expected that when I used --log-file that there would be no ouput to
  stdout.

  Note that it wrote the same thing to the log file so maybe this is
  expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1230360/+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 1720354] Re: Glance doesn't send correctly authorization request to Oslo policy

2017-10-09 Thread Doug Hellmann

It sounds like the policy library is not clear enough that it expects
the thing passed to it to be a dictionary, or at least to fully act like
one.

@Cyril, I think your pastebin from comment #1 is going in the right
direction. Would it fill out the API of ImageTarget so that it is fully
compliant with the Mapping abstract base class?
https://docs.python.org/2/library/collections.html#collections.Mapping

** Also affects: oslo.policy
   Importance: Undecided
   Status: New

** Changed in: oslo.policy
   Status: New => Triaged

** Changed in: oslo.policy
   Importance: Undecided => Low

** Changed in: oslo.policy
 Assignee: (unassigned) => Doug Hellmann (doug-hellmann)

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

Title:
  Glance doesn't send correctly authorization request to Oslo policy

Status in Glance:
  New
Status in oslo.policy:
  In Progress

Bug description:
  We have an OpenStack/Mitaka installed with Keystone, Nova and Glance.
  In /etc/glance/policy.json, we have modified the following lines to test the 
http_check function of Oslo policy:

  ...
  "add_image": "http://moon:8081/authz/wrapper;,
  "delete_image": "http://moon:8081/authz/wrapper;,
  "get_image": "http://moon:8081/authz/wrapper;,
  "get_images": "http://moon:8081/authz/wrapper;,
  "modify_image": "http://moon:8081/authz/wrapper;,
  ...
  Then, when we run:
  $ openstack image list
  +--+++
  | ID   | Name   | Status |
  +--+++
  | 6e31cdd2-4968-4a80-aebc-fcdd6f213091 | cirros | active |
  +--+++
  with no problem, but if we run:
  $ openstack image create --disk-format qcow2 --file 
/vagrant/cirros-0.3.5-x86_64-disk.img --container-format bare cirros4

  400 Bad Request
  cannot deepcopy this pattern object
  (HTTP 400)

  The Oslo_Policy code doesn't raise an error but stop when trying to 
deepcopying the target variable in 
oslo.policy/oslo.policy/oslo_policy/_checks.py (line ~241) and we have the 
following event in Glance API logs:
  2017-09-25 12:48:16.044 16600 DEBUG oslo_policy._cache_handler 
[req-e98eef44-d01b-401f-8e69-c78adf5310d3 - - - - -] Reloading cached file 
/etc/glance/policy.json read_cached_file 
/usr/local/lib/python2.7/dist-packages/oslo_policy/_cache_handler.py:40
  2017-09-25 12:48:16.047 16600 DEBUG oslo_policy.policy 
[req-e98eef44-d01b-401f-8e69-c78adf5310d3 - - - - -] Reloaded policy file: 
/etc/glance/policy.json _load_policy_file 
/usr/local/lib/python2.7/dist-packages/oslo_policy/policy.py:682
  2017-09-25 12:48:16.075 16600 DEBUG glance.api.v2.images 
[req-e98eef44-d01b-401f-8e69-c78adf5310d3 - - - - -] cannot deepcopy this 
pattern object create 
/usr/lib/python2.7/dist-packages/glance/api/v2/images.py:85
  2017-09-25 12:48:16.084 16600 INFO eventlet.wsgi.server 
[req-e98eef44-d01b-401f-8e69-c78adf5310d3 - - - - -] 127.0.0.1 - - [25/Sep/2017 
12:48:16] "POST /v2/images HTTP/1.1" 400 273 0.053245

  An other problem is that we have not enough information in the target
  variable (in oslo.policy/oslo.policy/oslo_policy/_checks.py). Because
  most of the information have the 'object' type, they are deleted from
  the temp_target variable (line ~244).

  We believe that this is due to the Glance part since it doesn't well
  prepare the authorization request (body) to Oslo policy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1720354/+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 1706179] Re: keystone has no admin or configuration guide

2017-07-25 Thread Doug Hellmann

Yes, the problem was the missing index.html pages.

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

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

Title:
  keystone has no admin or configuration guide

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  The doc-migration spec calls for a configuration guide to be published
  by placing the content doc/source/configuration and the admin guide to
  be published by placing the content under doc/source/admin. No such
  content exists for keystone.

  The project can not be included in the list of services on
  https://docs.openstack.org/pike/configuration/ and
  https://docs.openstack.org/pike/admin/ until the content is created.

  http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-
  migration.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1706179/+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 1706179] [NEW] keystone has no admin or configuration guide

2017-07-24 Thread Doug Hellmann

Public bug reported:

The doc-migration spec calls for a configuration guide to be published
by placing the content doc/source/configuration and the admin guide to
be published by placing the content under doc/source/admin. No such
content exists for keystone.

The project can not be included in the list of services on
https://docs.openstack.org/pike/configuration/ and
https://docs.openstack.org/pike/admin/ until the content is created.

http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-
migration.html

** Affects: keystone
 Importance: Undecided
 Status: New

** Description changed:

  The doc-migration spec calls for a configuration guide to be published
  by placing the content doc/source/configuration and the admin guide to
  be published by placing the content under doc/source/admin. No such
- content exists for heat.
+ content exists for keystone.
  
  The project can not be included in the list of services on
  https://docs.openstack.org/pike/configuration/ and
  https://docs.openstack.org/pike/admin/ until the content is created.
  
  http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-
  migration.html

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

Title:
  keystone has no admin or configuration guide

Status in OpenStack Identity (keystone):
  New

Bug description:
  The doc-migration spec calls for a configuration guide to be published
  by placing the content doc/source/configuration and the admin guide to
  be published by placing the content under doc/source/admin. No such
  content exists for keystone.

  The project can not be included in the list of services on
  https://docs.openstack.org/pike/configuration/ and
  https://docs.openstack.org/pike/admin/ until the content is created.

  http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-
  migration.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1706179/+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 1662911] [NEW] v3 API create_user does not use default_project_id

2017-02-08 Thread Doug Hellmann

Public bug reported:

The v3 call to create a user doesn't use the default_project_id argument
except to validate it.

https://github.com/openstack/keystone/blob/master/keystone/identity/core.py#L918-L919

This caused problems when updating grenade to allow the ocata->pike
tests to run, because the user was not set up with a default role as it
had been under V2.

https://review.openstack.org/#/c/427916/1

http://logs.openstack.org/16/427916/1/check/gate-grenade-dsvm-neutron-ubuntu-xenial/56b7a7d/logs/apache/keystone.txt.gz?level=WARNING#_2017-02-08_13_48_57_247
http://logs.openstack.org/16/427916/1/check/gate-grenade-dsvm-neutron-ubuntu-xenial/56b7a7d/logs/grenade.sh.txt.gz#_2017-02-08_13_48_54_600

** Affects: keystone
 Importance: Undecided
 Status: New

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

Title:
  v3 API create_user does not use default_project_id

Status in OpenStack Identity (keystone):
  New

Bug description:
  The v3 call to create a user doesn't use the default_project_id
  argument except to validate it.

  
https://github.com/openstack/keystone/blob/master/keystone/identity/core.py#L918-L919

  This caused problems when updating grenade to allow the ocata->pike
  tests to run, because the user was not set up with a default role as
  it had been under V2.

  https://review.openstack.org/#/c/427916/1

  
http://logs.openstack.org/16/427916/1/check/gate-grenade-dsvm-neutron-ubuntu-xenial/56b7a7d/logs/apache/keystone.txt.gz?level=WARNING#_2017-02-08_13_48_57_247
  
http://logs.openstack.org/16/427916/1/check/gate-grenade-dsvm-neutron-ubuntu-xenial/56b7a7d/logs/grenade.sh.txt.gz#_2017-02-08_13_48_54_600

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1662911/+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 1662699] [NEW] API documentation and behavior do not match for booting with attached volumes

2017-02-07 Thread Doug Hellmann

Public bug reported:

Description
===

The documentation for block device mapping in
http://docs.openstack.org/developer/nova/block_device_mapping.html
#block-device-mapping-v2 indicates that to attach a volume to a new
instance without booting from that volume a boot_index value of None can
be passed. Shade was doing this, and it works against some clouds (at
least DreamHosts's iad2 cloud, "dreamcompute", which is running either
mitaka or newton). It does not work against nova at least as of
9ae5b2306b7a7cc9e77c77292256b13926920ead launched with devstack.

Steps to reproduce
==

1. Run devstack.
2. Download the downpour git repo from https://github.com/dhellmann/downpour
3. Use the tiny.yml playbook in the demo directory to launch an instance (see 
the README for some setup instructions).

Expected Result
===

One new instance named downpour-demo-tiny booted ephemeral with a new
volume named downpour-demo-tiny attached to it.

Actual Result
=

Error message: Invalid input for field/attribute boot_index. Value:
None. None is not of type 'integer'

Additional Info
===

IRC logs from 7 Feb 2017 in #openstack-nova

[Tue 05:29:35 PM]  mriedem: so - I've got this question about boot 
from volume
[Tue 05:30:51 PM]  mriedem: 
http://developer.openstack.org/api-ref/compute/?expanded=create-server-detail#create-server
 says that block_device_mapping_v2.boot_index takes a string and also that None 
should be used for volumes not used as boot volumes
[Tue 05:32:00 PM]  was just packing up...
[Tue 05:32:20 PM]  mriedem: but we just got an error "Invalid 
input for field/attribute boot_index. Value: None. None is not of type 'integer"
[Tue 05:32:24 PM]  mordred: 
http://docs.openstack.org/developer/nova/block_device_mapping.html might be 
helpful
[Tue 05:32:33 PM]  mriedem: yup. it also says None is valid
[Tue 05:34:01 PM]  i feel like something was just recently changed 
in the json schema there, is this master?
[Tue 05:34:17 PM]  dhellmann: you were doing master devstack?
[Tue 05:34:30 PM]  mriedem: I think so yeah?
[Tue 05:34:43 PM]mordred : yes, master devstack (from a few 
hours ago)
[Tue 05:34:45 PM] mordred   goes to look at json schema
[Tue 05:34:51 PM]   
https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/schemas/block_device_mapping.py#L56
[Tue 05:35:28 PM]  fantastic
[Tue 05:36:06 PM]  what's the image and dest type?
[Tue 05:36:19 PM]  source_type and destination_type i mean
[Tue 05:37:01 PM]  because 
https://github.com/openstack/nova/blob/master/nova/block_device.py#L198
[Tue 05:37:02 PM]it's a qcow2 ubuntu image
[Tue 05:37:16 PM]  destination_type would be 'volume'
[Tue 05:37:22 PM]  and source_type is?
[Tue 05:37:23 PM]  image?
[Tue 05:37:24 PM]I want to boot it ephemeral  and attach a volume
[Tue 05:37:47 PM]  yah- source_type also volume
[Tue 05:38:01 PM]  have you tried omitting boot_index
[Tue 05:38:02 PM]  ?
[Tue 05:38:05 PM]  yes. that works
[Tue 05:38:12 PM]  as does providing -1 or '-1'
[Tue 05:38:46 PM]  however, None worked in the past and is still 
referneced in the docs ... so maybe there's a bug somewhere, I'm just not sure 
what to file/write up
[Tue 05:38:59 PM]  (we can make shade dtrt by omitting or using -1
[Tue 05:39:14 PM]  oomichi: Kevin_Zheng: gmann: alex_xu: do you 
remember anything recently related to this? ^
[Tue 05:39:40 PM]  https://review.openstack.org/#/c/410006/
[Tue 05:40:50 PM]  mordred: i wouldn't put a ton of faith in the 
api-ref docs on this one
[Tue 05:40:57 PM]  mriedem: ok
[Tue 05:41:03 PM]  i'd be interested in knowing if it's different 
on like a liberty install
[Tue 05:41:29 PM]  mriedem: None worked against dreamhost - 
whatever version is running there
[Tue 05:41:43 PM]  mordred: because my guess is the wording in the 
api-ref was pulled from 
http://docs.openstack.org/developer/nova/block_device_mapping.html and that's 
more about the actual object code in nova rather than the API
[Tue 05:42:05 PM]  ah - k. so it's likely just a docs bug
[Tue 05:42:06 PM]dreamhost is either mitaka or newton
[Tue 05:42:15 PM]  i'd file a bug either way so we can investigate
[Tue 05:42:27 PM]I can do that
[Tue 05:42:37 PM]  plus, if the api is ok but the docs are wrong, 
we can use the bug to fix the docs
[Tue 05:42:50 PM]  cool.
[Tue 05:42:52 PM]  thanks dhellmann !
[Tue 05:43:10 PM]thanks, mordred & mriedem 
[Tue 05:45:00 PM]  also,
[Tue 05:45:07 PM]  i wonder if you were hitting a nova v2 vs v2.1 
endpoint before...
[Tue 05:45:11 PM]  v2 didn't have schema validation
[Tue 05:45:22 PM]  mordred: dhellmann: ^
[Tue 05:45:39 PM]  oh - it's entirely possible
[Tue 05:46:06 PM]  shade is (currently) just piggybacking 
novaclient which grabs latest microversion aiui
[Tue 05:46:12 PM]  I haven't gotten to

[Yahoo-eng-team] [Bug 1600281] Re: ImportError: No module named api

2016-07-13 Thread Doug Hellmann

I've added neutron back to this bug report, because we need to sort out
which version of neutron-lib is correct for mitaka. 0.0.2 was marked as
part of the mitaka release, but its contents do not appear on the stable
branch. Should we change the constraints list to only allow 0.0.1, or do
we need 0.0.2 and therefore need to back port its contents into the
correct branch?


** Also affects: neutron
   Importance: Undecided
   Status: New

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

** Also affects: neutron/mitaka
   Importance: Undecided
   Status: New

** Changed in: neutron/mitaka
   Importance: Undecided => Medium

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

Title:
  ImportError: No module named api

Status in neutron:
  New
Status in neutron mitaka series:
  New
Status in tripleo:
  Fix Released

Bug description:
  The mitaka ci job is currently failing during the undercloud install
  with the following error

  
Stage[main]/Ceilometer::Keystone::Auth/Keystone::Resource::Service_identity[ceilometer]/Keystone_endpoint[regionOne/ceilometer::metering]/ensure:
 created^[[0m
  
Stage[main]/Neutron::Keystone::Auth/Keystone::Resource::Service_identity[neutron]/Keystone_endpoint[regionOne/neutron::network]/ensure:
 created^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: No handlers 
could be found for logger "oslo_config.cfg"^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: Traceback (most 
recent call last):^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns:   File 
"/usr/bin/neutron-db-manage", line 10, in ^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: 
sys.exit(main())^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns:   File 
"/usr/lib/python2.7/site-packages/neutron/db/migration/cli.py", line 749, in 
main^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: return_val 
|= bool(CONF.command.func(config, CONF.command.name))^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns:   File 
"/usr/lib/python2.7/site-packages/neutron/db/migration/cli.py", line 223, in 
do_upgrade^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: 
run_sanity_checks(config, revision)^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns:   File 
"/usr/lib/python2.7/site-packages/neutron/db/migration/cli.py", line 731, in 
run_sanity_checks^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: 
script_dir.run_env()^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns:   File 
"/usr/lib/python2.7/site-packages/alembic/script/base.py", line 397, in 
run_env^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: 
util.load_python_file(self.dir, 'env.py')^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns:   File 
"/usr/lib/python2.7/site-packages/alembic/util/pyfiles.py", line 81, in 
load_python_file^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: module = 
load_module_py(module_id, path)^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns:   File 
"/usr/lib/python2.7/site-packages/alembic/util/compat.py", line 79, in 
load_module_py^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: mod = 
imp.load_source(module_id, path, fp)^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns:   File 
"/usr/lib/python2.7/site-packages/neutron/db/migration/alembic_migrations/env.py",
 line 25, in ^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: from 
neutron.db.migration.models import head  # noqa^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns:   File 
"/usr/lib/python2.7/site-packages/neutron/db/migration/models/head.py", line 
28, in ^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: from 
neutron.db import bgp_db  # noqa^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns:   File 
"/usr/lib/python2.7/site-packages/neutron/db/bgp_db.py", line 26, in 
^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: from 
neutron_lib.api import validators^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: ImportError: No 
module named api^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]: Failed to call refresh: 
neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file 
/etc/neutron/plugin.ini upgrade head returned 1 instead of one of [0]^[[0m
  Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]: neutron-db-manage 
--config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini 
upgrade head returned 1 instead of one of [0]^[[0m
  
Stage[main]/Swift::Keystone::Auth/Keystone::Resource::Service_identity[swift]/Keystone_user[swift]/ensure:
 created^[[0m

To manage

[Yahoo-eng-team] [Bug 1548433] [NEW] neutron returns objects other than oslo_config.cfg.Opt instances from list_opts

2016-02-22 Thread Doug Hellmann

Public bug reported:

The neutron function for listing options for use with the configuration
generator returns things that are not compliant with the
oslo_config.cfg.Opt class API. At the very least this includes the
options from keystoneauth1, but I haven't looked to find if there are
others.

We'll work around this for now in the configuration generator code, but
in the future we will more strictly enforce the API compliance by
refusing to generate a configuration file or by leaving options out of
the output.

The change blocked by this issue is:
https://review.openstack.org/#/c/282435/5

One failure log showing the issue is:
http://logs.openstack.org/35/282435/5/check/gate-tempest-dsvm-neutron-
src-oslo.config/77044c6/logs/devstacklog.txt.gz

The neutron code triggering the issue is in:
http://git.openstack.org/cgit/openstack/neutron/tree/neutron/opts.py#n279

The best solution would be to fix keystoneauth to support option
discovery natively using proper oslo.config Opts.

** Affects: keystoneauth
 Importance: Undecided
 Status: New

** Affects: neutron
 Importance: Undecided
 Status: New

** Also affects: keystoneauth
   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/1548433

Title:
  neutron returns objects other than oslo_config.cfg.Opt instances from
  list_opts

Status in keystoneauth:
  New
Status in neutron:
  New

Bug description:
  The neutron function for listing options for use with the
  configuration generator returns things that are not compliant with the
  oslo_config.cfg.Opt class API. At the very least this includes the
  options from keystoneauth1, but I haven't looked to find if there are
  others.

  We'll work around this for now in the configuration generator code,
  but in the future we will more strictly enforce the API compliance by
  refusing to generate a configuration file or by leaving options out of
  the output.

  The change blocked by this issue is:
  https://review.openstack.org/#/c/282435/5

  One failure log showing the issue is:
  http://logs.openstack.org/35/282435/5/check/gate-tempest-dsvm-neutron-
  src-oslo.config/77044c6/logs/devstacklog.txt.gz

  The neutron code triggering the issue is in:
  http://git.openstack.org/cgit/openstack/neutron/tree/neutron/opts.py#n279

  The best solution would be to fix keystoneauth to support option
  discovery natively using proper oslo.config Opts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystoneauth/+bug/1548433/+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 1534613] Re: warnings in stable/liberty release notes are breaking releasenotes job in master

2016-01-22 Thread Doug Hellmann

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

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

Title:
  warnings in stable/liberty release notes are breaking releasenotes job
  in master

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

Bug description:
  Seeing this here:

  http://logs.openstack.org/69/268069/3/check/gate-nova-
  releasenotes/aaa7da2/console.html#_2016-01-15_11_27_02_287

  fatal: Path 'releasenotes/notes/new-oslo-reports-option-
  619c3dbf3ae320fb.yaml' does not exist in
  '8b65185c14447d30dc323f1a43de8d9b253fae04'

  That release note was deleted when we did this revert:

  https://review.openstack.org/#/c/253821/

  And it appears reno isn't handling it (or the sphinx extension).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1534613/+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 1534613] Re: warnings in stable/liberty release notes are breaking releasenotes job in master

2016-01-15 Thread Doug Hellmann

See https://review.openstack.org/268225 manage stderr output from
external commands in reno.

** Changed in: reno
   Status: Invalid => In Progress

** Changed in: reno
 Assignee: (unassigned) => Doug Hellmann (doug-hellmann)

** Changed in: reno
   Importance: Undecided => Low

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

Title:
  warnings in stable/liberty release notes are breaking releasenotes job
  in master

Status in OpenStack Compute (nova):
  In Progress
Status in reno:
  In Progress

Bug description:
  Seeing this here:

  http://logs.openstack.org/69/268069/3/check/gate-nova-
  releasenotes/aaa7da2/console.html#_2016-01-15_11_27_02_287

  fatal: Path 'releasenotes/notes/new-oslo-reports-option-
  619c3dbf3ae320fb.yaml' does not exist in
  '8b65185c14447d30dc323f1a43de8d9b253fae04'

  That release note was deleted when we did this revert:

  https://review.openstack.org/#/c/253821/

  And it appears reno isn't handling it (or the sphinx extension).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1534613/+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 1520722] Re: Automatically generate neutron core configuration files

2015-12-07 Thread Doug Hellmann

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

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

Title:
  Automatically generate neutron core configuration files

Status in neutron:
  Fix Released
Status in openstack-manuals:
  Triaged

Bug description:
  https://review.openstack.org/204206
  \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 71190773e14260fab96e78e65a290356cdc08581
  Author: Martin Hickey 
  Date:   Mon Nov 9 23:37:37 2015 +

  Automatically generate neutron core configuration files
  
  This adds a new tox environment, genconfig, which generates sample
  neutron core configuration file using oslo-config-generator.
  
  Updates to some configuration option help messages to reflect useful
  details that were missing in the code but were present in config files.
  
  It also adds details to devref on how to update config files.
  
  Partially-Implements: blueprint autogen-neutron-conf-file
  
  DocImpact
  
  Change-Id: I1c6dc4e7d479f1b7c755597caded24a0f018c712
  Closes-bug: #1199963
  Co-Authored-By: Louis Taylor 

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1520722/+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 1520041] Re: doc/source/man/neutron-server.rst is out-of-date. is it necessary?

2015-12-07 Thread Doug Hellmann

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

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

Title:
  doc/source/man/neutron-server.rst is out-of-date. is it necessary?

Status in neutron:
  Fix Released

Bug description:
  doc/source/man/neutron-server.rst is not maintained and out-of-date.
  Options mainly depend on oslo and it is not easy to maintain it.

  One option is to delete it.
  There is another opinion that it is worth having the man page even though it 
is a skeleton. I don't have a good idea on how to keep it up-to-date.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1520041/+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 1522731] Re: test_migrations filter_metadata_diff has py3 issue

2015-12-07 Thread Doug Hellmann

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

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

Title:
  test_migrations filter_metadata_diff has py3 issue

Status in neutron:
  Fix Released

Bug description:
  filter_metadata_diff returns a filter object in python3.
  it confuses oslo.db and causes test failures in relevant tests.
  eg. https://review.openstack.org/#/c/214765/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1522731/+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 1521766] Re: pylint breakage in neutron and neutron-vpnaas

2015-12-07 Thread Doug Hellmann

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

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

Title:
  pylint breakage in neutron and neutron-vpnaas

Status in neutron:
  Fix Released

Bug description:
  The astroid package, used by pylint, was recently updated to version
  1.4.1. Both 1.4.0 and 1.4.1 do not work with pylint 1.4.4, which is
  being used by LB, VPN, and neutron. astroid 1.3.8 works with pylint
  1.4.4.

  For neutron:
  master and liberty gate uses pep8-constraints, which has a pin for astroid
  kilo needs pinning (proposal is to add to requriements)
  juno doesn't use pylint, so works

  Note: Can modify pep8 target to do same as pep8-constraints, so that
  developers can use same command they are used to.

  To add users
  For LB:
  master - Temp workaround was to remove pylint, can pin, if desired.
  liberty, kilo? - will need to pin
  juno?

  
  For VPN:
  master, liberty, and kilo need to pin pylint and astroid
  juno does not use pylint

  NOTE: Can migrate to using pep8-constraints job and target.

  
  For FW:
  does not do pylint for pep8, so no problem seen (but no coverage).

  Because this broke gate, there are several patches already in play for
  this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1521766/+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 1521820] Re: Some DVR functional tests leak the FIP namespace

2015-12-07 Thread Doug Hellmann

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

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

Title:
  Some DVR functional tests leak the FIP namespace

Status in neutron:
  Fix Released

Bug description:
  The FIP namespace is deleted when the agent receives an RPC message
  'fipnamespace_delete_on_ext_net'
  (https://review.openstack.org/#/c/230079/). This is simulated in some
  DVR tests (Thus cleaning up the namespace), but not all. All of the
  DVR 'lifecycle' tests execute _dvr_router_lifecycle, which in turn
  executes _assert_fip_namespace_deleted, that calls
  agent.fipnamespace_delete_on_ext_net and asserts it succeeded. Any
  test that creates a distributed router that is not a 'lifecycle' test
  does not clean up the FIP namespace, this includes:

  * test_dvr_router_fips_for_multiple_ext_networks
  * test_dvr_router_rem_fips_on_restarted_agent
  * test_dvr_router_add_fips_on_restarted_agent
  * test_dvr_router_add_internal_network_set_arp_cache
  * test_dvr_router_fip_agent_mismatch
  * test_dvr_router_fip_late_binding
  * test_dvr_router_snat_namespace_with_interface_remove
  * test_dvr_ha_router_failover

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1521820/+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 1522224] Fix included in openstack/neutron 7.0.1

2015-12-07 Thread Doug Hellmann

This issue was fixed in the openstack/neutron 7.0.1 release.

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

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

Title:
  default quotas are broken for rbac

Status in neutron:
  Fix Released

Bug description:
  The default quotas option for rbac is registered as 'rbac_entry' when
  the API name is 'rbac_policy' so it ends up being ignored and the
  entries default to -1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/154/+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 1522706] Re: lbass migration vs model mismatch

2015-12-07 Thread Doug Hellmann

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

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

Title:
  lbass migration vs model mismatch

Status in neutron:
  Fix Released

Bug description:
  tls_container_id and default_tls_container_id has different length
  between migration and model.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1522706/+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 1522710] Re: Functional Test does not clean up ports when in default network namespace

2015-12-07 Thread Doug Hellmann

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

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

Title:
  Functional Test does not clean up ports when in default network
  namespace

Status in neutron:
  Fix Released

Bug description:
  The VethFixture in net_helpers.py does not clean up ports that were
  created in the deafult network namespace. One exploiter is the
  neutron/tests/functional/agent/linux/test_bridge_lib.py test. After
  one test run, you have about 10 vethpairs, saying 20 new devices in
  your default network namespace

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1522710/+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 1520054] Re: HyperV third-party code still present in neutron tree

2015-12-07 Thread Doug Hellmann

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

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

Title:
  HyperV third-party code still present in neutron tree

Status in networking-hyperv:
  Fix Committed
Status in neutron:
  Fix Released

Bug description:
  The HyperV ML2 mechanism driver and agent should be completely removed
  from the neutron tree. All HyperV code and artifacts should be
  contained in the networking-hyperv sub-project.

  See http://docs.openstack.org/developer/neutron/devref/contribute.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-hyperv/+bug/1520054/+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 1521620] Re: Neutron-lbaas gate broken due to pep8

2015-12-07 Thread Doug Hellmann

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

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

Title:
  Neutron-lbaas gate broken due to pep8

Status in neutron:
  Fix Released

Bug description:
  2015-12-01 11:39:24.491 | pep8 runtests: PYTHONHASHSEED='3236704285'
  2015-12-01 11:39:24.491 | pep8 runtests: commands[0] | flake8
  2015-12-01 11:39:24.492 |   /home/jenkins/workspace/gate-neutron-lbaas-pep8$ 
/home/jenkins/workspace/gate-neutron-lbaas-pep8/.tox/pep8/bin/flake8 
  2015-12-01 11:39:27.194 | pep8 runtests: commands[1] | pylint 
--rcfile=.pylintrc --output-format=colorized neutron_lbaas
  2015-12-01 11:39:27.194 |   /home/jenkins/workspace/gate-neutron-lbaas-pep8$ 
/home/jenkins/workspace/gate-neutron-lbaas-pep8/.tox/pep8/bin/pylint 
--rcfile=.pylintrc --output-format=colorized neutron_lbaas 
  2015-12-01 11:39:27.513 | Warning: option ignore-iface-methods is obsolete 
and it is slated for removal in Pylint 1.6.
  2015-12-01 11:39:46.623 | [7;33m* Module 
neutron_lbaas.agent_scheduler[0m
  2015-12-01 11:39:46.623 | [1mC[0m: 22, 0: [1mexternal import "from 
oslo_log import log as logging" comes before "from neutron.db import 
agents_db"[0m ([1mwrong-import-order[0m)
  2015-12-01 11:39:46.623 | [1mC[0m: 23, 0: [1mexternal import "import six" 
comes before "from neutron.db import agents_db"[0m ([1mwrong-import-order[0m)
  2015-12-01 11:39:46.624 | [1mC[0m: 24, 0: [1mexternal import "import 
sqlalchemy as sa" comes before "from neutron.db import agents_db"[0m 
([1mwrong-import-order[0m)
  2015-12-01 11:39:46.624 | [1mC[0m: 25, 0: [1mexternal import "from 
sqlalchemy import orm" comes before "from neutron.db import agents_db"[0m 
([1mwrong-import-order[0m)
  2015-12-01 11:39:46.624 | [1mC[0m: 26, 0: [1mexternal import "from 
sqlalchemy.orm import joinedload" comes before "from neutron.db import 
agents_db"[0m ([1mwrong-import-order[0m)
  2015-12-01 11:39:46.624 | [7;33m* Module 
neutron_lbaas.db.loadbalancer.loadbalancer_dbv2[0m
  2015-12-01 11:39:46.624 | [1mC[0m: 25, 0: [1mexternal import "from oslo_db 
import exception" comes before "from neutron.api.v2 import attributes"[0m 
([1mwrong-import-order[0m)
  2015-12-01 11:39:46.624 | [1mC[0m: 26, 0: [1mexternal import "from 
oslo_log import log as logging" comes before "from neutron.api.v2 import 
attributes"[0m ([1mwrong-import-order[0m)
  2015-12-01 11:39:46.624 | [1mC[0m: 27, 0: [1mexternal import "from 
oslo_utils import excutils" comes before "from neutron.api.v2 import 
attributes"[0m ([1mwrong-import-order[0m)
  2015-12-01 11:39:46.624 | [1mC[0m: 28, 0: [1mexternal import "from 
oslo_utils import uuidutils" comes before "from neutron.api.v2 import 
attributes"[0m ([1mwrong-import-order[0m)
  2015-12-01 11:39:46.624 | [1mC[0m: 29, 0: [1mexternal import "from 
sqlalchemy import orm" comes before "from neutron.api.v2 import attributes"[0m 
([1mwrong-import-order[0m)
  2015-12-01 11:39:46.624 | [1mC[0m: 30, 0: [1mexternal import "from 
sqlalchemy.orm import exc" comes before "from neutron.api.v2 import 
attributes"[0m ([1mwrong-import-order[0m)
  2015-12-01 11:39:46.624 | [7;33m* Module 
neutron_lbaas.db.loadbalancer.models[0m
  2015-12-01 11:39:46.625 | [1mC[0m: 20, 0: [1mexternal import "import 
sqlalchemy as sa" comes before "from neutron.db import model_base"[0m 
([1mwrong-import-order[0m)
  2015-12-01 11:39:46.625 | [1mC[0m: 21, 0: [1mexternal import "from 
sqlalchemy.ext import orderinglist" comes before "from neutron.db import 
model_base"[0m ([1mwrong-import-order[0m)
  2015-12-01 11:39:46.625 | [1mC[0m: 22, 0: [1mexternal import "from 
sqlalchemy import orm" comes before "from neutron.db import model_base"[0m 
([1mwrong-import-order[0m)
  2015-12-01 11:39:46.625 | [7;33m* Module 
neutron_lbaas.db.loadbalancer.loadbalancer_db[0m
  2015-12-01 11:39:46.625 | [1mC[0m: 29, 0: [1mexternal import "from oslo_db 
import exception" comes before "from neutron.api.v2 import attributes"[0m 
([1mwrong-import-order[0m)
  2015-12-01 11:39:46.625 | [1mC[0m: 30, 0: [1mexternal import "from 
oslo_log import log as logging" comes before "from neutron.api.v2 import 
attributes"[0m ([1mwrong-import-order[0m)
  2015-12-01 11:39:46.625 | [1mC[0m: 31, 0: [1mexternal import "from 
oslo_utils import excutils" comes before "from neutron.api.v2 import 
attributes"[0m ([1mwrong-import-order[0m)
  2015-12-01 11:39:46.625 | [1mC[0m: 32, 0: [1mexternal import "from 
oslo_utils import uuidutils" comes before "from neutron.api.v2 import 
attributes"[0m ([1mwrong-import-order[0m)
  2015-12-01 11:39:46.625 | [1mC[0m: 33, 0: [1mexternal import "import 
sqlalchemy as sa" comes before "from neutron.api.v2 import attributes"[0m 
([1mwrong-import-order[0m)
  2015-12-01

[Yahoo-eng-team] [Bug 1520138] Re: lbaas: vip connection limit can be set to value less than -1 in openstack cli

2015-12-07 Thread Doug Hellmann

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

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

Title:
  lbaas: vip connection limit can be set to value less than -1 in
  openstack cli

Status in neutron:
  Fix Released

Bug description:
  In openstack kilo setup with ubuntu 14.04,  in openstack neutron cli,
  lb vip connection limit can be set to a value less than -1, this is
  forbidden via dashboard.

  1. create a lb pool in admin tenant.
  2. create vip for this pool and set connection limit to -2.

  
  [root@nsj1 ~]# neutron lb-vip-create --connection-limit -2 --description vip  
--name lb_vip --protocol-port 80 --protocol TCP --subnet-id 
0f27a0a7-5a43-48f6-bcd3-e03dd7b39254 uat-lb-alan
  Created a new vip:
  +-+--+
  | Field   | Value|
  +-+--+
  | address | 10.90.2.19   |
  | admin_state_up  | True |
  | connection_limit| -2   |
>>>on dashboard, if the value is less than -1, it will rejected.
  | description | vip  |
  | id  | 344a0679-21ec-4ec5-87f9-87441b246fd8 |
  | name| lb_vip   |
  | pool_id | eb912b41-42e5-462c-8391-608f919a528b |
  | port_id | 7d4a41bf-f655-4721-8914-b24c54176b04 |
  | protocol| TCP  |
  | protocol_port   | 80   |
  | session_persistence |  |
  | status  | PENDING_CREATE   |
  | status_description  |  |
  | subnet_id   | 0f27a0a7-5a43-48f6-bcd3-e03dd7b39254 |
  | tenant_id   | b901c52cb2984ad0bc9914140e3ba54d |
  +-+--+

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1520138/+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 1505575] Re: Fatal memory consumption by neutron-server with DVR at scale

2015-12-07 Thread Doug Hellmann

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

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

Title:
  Fatal memory consumption by neutron-server with DVR at scale

Status in neutron:
  Fix Released

Bug description:
  Steps to reproduce:
  0. The issue is noticeable at scale (100+ nodes), DVR should be turned on
  1. Run rally scenario NeutronNetworks.create_and_list_routers

  Initially neutron-server processes consume 100-150M, but at some point
  the size rapidly increases in several times. (At 200 nodes the raise
  was from 150M to 2G, and upto 14G in the end).

  The issue may lead to OOM situation causing kernel to kill the process
  with highest consumption. Usually candidates are rabbit or mysql. This
  makes cluster completely inoperable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1505575/+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 1518643] Re: Nuage vendor code still present in neutron tree

2015-12-07 Thread Doug Hellmann

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

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

Title:
  Nuage vendor code still present in neutron tree

Status in neutron:
  Fix Released
Status in python-neutronclient:
  New

Bug description:
  The Nuage plugins and ML2 mechanism drivers should be completely
  removed from the neutron tree.

  See http://docs.openstack.org/developer/neutron/devref/contribute.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1518643/+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 1522436] Re: No need to autoreschedule routers if l3 agent is back online

2015-12-07 Thread Doug Hellmann

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

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

Title:
  No need to autoreschedule routers if l3 agent is back online

Status in neutron:
  Fix Released

Bug description:
   - in case l3 agent goes offline the auto-rescheduling task is triggered and 
starts to reschedule each router from dead agent one by one
   - If there are a lot of routers scheduled to the agent, rescheduling all of 
them might take some time
   - during that time the agent might get back online
   - currently autorescheduling will be continued until all routers are 
rescheduled from the (already alive!) agent

  The proposal is to skip rescheduling if agent is back online.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1522436/+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 1521846] Re: Metering not configured for all-in-one DVR job, failing tests

2015-12-07 Thread Doug Hellmann

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

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

Title:
  Metering not configured for all-in-one DVR job, failing tests

Status in neutron:
  Fix Released

Bug description:
  Here's an example:
  
http://logs.openstack.org/74/247874/6/check/gate-tempest-dsvm-neutron-dvr/62fdece/console.html#_2015-12-02_02_15_59_182

  It looks like the metering setUpClass is trying to register metering
  resources before checking if the extension is actually loaded (Which
  is a separate bug in the tests). Another test fails showing that
  metering is not configured:

  http://logs.openstack.org/74/247874/6/check/gate-tempest-dsvm-neutron-
  dvr/62fdece/console.html#_2015-12-02_02_15_59_167

  Metering seems to be configured fine both in the non-DVR job, as well
  as the multinode DVR job.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1521846/+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 1522734] Re: neutron cannot build on HyperV

2015-12-07 Thread Doug Hellmann

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

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

Title:
  neutron cannot build on HyperV

Status in neutron:
  Fix Released

Bug description:
  We are receiving the following error when installing neutron on HyperV

  error: can't copy 'etc\neutron\plugins\ml2\linuxbridge_agent.ini': doesn't 
exist or not a regular file
  ExecRetry : System.Management.Automation.RuntimeException: Failed to install 
  neutron from repo

  It is related to this commit:

  
https://github.com/openstack/neutron/commit/a8a0c619de69dd0d84a692c85fe6d23b765550e7

  that is incomplete.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1522734/+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 1451621] Re: creating resources with an empty tenant_id succeeds when using noop driver

2015-12-07 Thread Doug Hellmann

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

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

Title:
  creating resources with an empty tenant_id succeeds when using noop
  driver

Status in neutron:
  Fix Released

Bug description:
  Please take a look at "test_create_listener_empty_tenant_id" method in
  test_listeners_admin.py in the patch
  https://review.openstack.org/#/c/173423 to reproduce the error.

  
  Ongoing discussion:
  
  In case of  noop driver when we try to create a 
resource(loadbalancer/listener/member/pool) with empty tenant id, it gets 
created (as there is no validation). But in case of backend driver with 
validation for empty/invalid tenant-id, it raises BadRequest which is 
translated as "driver-internal error" at plugin layer.
  -Santosh Sharma

  I think the question would be whether the api should treat an empty string 
tenant id the same as a tenant id which is None.
  -Franklin Naval

  I think this falls under the same discussion about tenant_id being validated 
for all admin requests. All of neutron currently does not do this, and since we 
are an extension to neutron and don't control the wsgi layer, we usually just 
go with what they do. However, we can specifically validate the string is 
non-empty in our plugin, but that would be a temporary hack until the larger 
neutron discussion completes.
  -Brandon Logan

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1451621/+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 1518637] Re: Brocade vendor code still present in neutron tree

2015-12-07 Thread Doug Hellmann

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

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

Title:
  Brocade vendor code still present in neutron tree

Status in networking-brocade:
  New
Status in neutron:
  Fix Released

Bug description:
  The Brocade plugins and ML2 mechanism drivers should be completely
  removed from the neutron tree. All Brocade code and artifacts should
  be contained in the networking-brocade sub-project.

  See http://docs.openstack.org/developer/neutron/devref/contribute.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-brocade/+bug/1518637/+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 1494574] Re: Logging missing value types

2015-12-04 Thread Doug Hellmann

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

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

Title:
  Logging missing value types

Status in Cinder:
  Fix Released
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Released
Status in networking-midonet:
  Fix Released
Status in neutron:
  Fix Released
Status in os-brick:
  Fix Released
Status in oslo.versionedobjects:
  Fix Committed
Status in tempest:
  Fix Released
Status in Trove:
  In Progress

Bug description:
  There are a few locations in the code where the log string is missing
  the formatting type, causing log messages to fail.

  
  FILE: ../OpenStack/cinder/cinder/volume/drivers/emc/emc_vnx_cli.py
  
  LOG.debug('EMC: Command Exception: %(rc) %(result)s. 
'  
  FILE: ../OpenStack/cinder/cinder/consistencygroup/api.py  
  
  LOG.error(_LE("CG snapshot %(cgsnap) not found 
when "
  LOG.error(_LE("Source CG %(source_cg) not found 
when "
  FILE: ../OpenStack/cinder/cinder/volume/drivers/emc/emc_vmax_masking.py   
  
  "Storage group %(sgGroupName) "   
  
  FILE: ../OpenStack/cinder/cinder/volume/manager.py
  
  '%(image_id) will not create cache 
entry.'),

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1494574/+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 1503501] Re: oslo.db no longer requires testresources and testscenarios packages

2015-12-04 Thread Doug Hellmann

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

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

Title:
  oslo.db no longer requires testresources and testscenarios packages

Status in Cinder:
  Fix Released
Status in Glance:
  Fix Released
Status in heat:
  Fix Released
Status in heat liberty series:
  Fix Committed
Status in Ironic:
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in Sahara:
  Fix Released
Status in Sahara liberty series:
  Fix Committed
Status in Sahara mitaka series:
  Fix Released

Bug description:
  As of https://review.openstack.org/#/c/217347/ oslo.db no longer has
  testresources or testscenarios in its requirements, So next release of
  oslo.db will break several projects. These project that use fixtures
  from oslo.db should add these to their requirements if they need it.

  Example from Nova:
  ${PYTHON:-python} -m subunit.run discover -t ./ ${OS_TEST_PATH:-./nova/tests} 
--list 
  ---Non-zero exit code (2) from test listing.
  error: testr failed (3) 
  import errors ---
  Failed to import test module: nova.tests.unit.db.test_db_api
  Traceback (most recent call last):
File 
"/home/travis/build/dims/nova/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py",
 line 456, in _find_test_path
  module = self._get_module_from_name(name)
File 
"/home/travis/build/dims/nova/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py",
 line 395, in _get_module_from_name
  __import__(name)
File "nova/tests/unit/db/test_db_api.py", line 31, in 
  from oslo_db.sqlalchemy import test_base
File 
"/home/travis/build/dims/nova/.tox/py27/src/oslo.db/oslo_db/sqlalchemy/test_base.py",
 line 17, in 
  import testresources
  ImportError: No module named testresources

  https://travis-ci.org/dims/nova/jobs/83992423

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1503501/+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 1323975] Re: do not use default=None for config options

2015-12-03 Thread Doug Hellmann

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

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

Title:
  do not use default=None for config options

Status in Aodh:
  Fix Released
Status in Barbican:
  Fix Released
Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in congress:
  Fix Committed
Status in Designate:
  Fix Committed
Status in Glance:
  Fix Released
Status in glance_store:
  Fix Released
Status in Gnocchi:
  Fix Committed
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Committed
Status in Mistral:
  Fix Released
Status in Murano:
  Fix Committed
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo-incubator:
  Fix Released
Status in oslo.messaging:
  Fix Released
Status in Rally:
  Fix Committed
Status in Sahara:
  Fix Released
Status in tempest:
  In Progress
Status in Trove:
  In Progress
Status in zaqar:
  Fix Released

Bug description:
  In the cfg module default=None is set as the default value. It's not
  necessary to set it again when defining config options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1323975/+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 1512207] Fix included in openstack/manila 2.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/manila 2.0.0.0b1 development
milestone.

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

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

Title:
  Fix usage of assertions

Status in OpenStack Identity (keystone):
  Fix Committed
Status in Manila:
  Fix Released
Status in Sahara:
  Fix Released

Bug description:
  Manila  should use the specific assertion:

self.assertIsTrue/False(observed)

  instead of the generic assertion:

self.assertEqual(True/False, observed)

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1512207/+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 1516634] Re: Openstack typo

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Openstack typo

Status in Glance:
  Fix Released
Status in Manila:
  Fix Released

Bug description:
  According to the word choice convention in 
http://docs.openstack.org/contributor-guide/writing-style/word-choice.html
  We should use OpenStack instead of Openstack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1516634/+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 1503501] Fix included in openstack/sahara 4.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/sahara 4.0.0.0b1 development
milestone.

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

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

Title:
  oslo.db no longer requires testresources and testscenarios packages

Status in Cinder:
  Fix Released
Status in Glance:
  Fix Released
Status in heat:
  Fix Committed
Status in heat liberty series:
  Fix Committed
Status in Ironic:
  Fix Committed
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in Sahara:
  Fix Released
Status in Sahara liberty series:
  Fix Committed
Status in Sahara mitaka series:
  Fix Released

Bug description:
  As of https://review.openstack.org/#/c/217347/ oslo.db no longer has
  testresources or testscenarios in its requirements, So next release of
  oslo.db will break several projects. These project that use fixtures
  from oslo.db should add these to their requirements if they need it.

  Example from Nova:
  ${PYTHON:-python} -m subunit.run discover -t ./ ${OS_TEST_PATH:-./nova/tests} 
--list 
  ---Non-zero exit code (2) from test listing.
  error: testr failed (3) 
  import errors ---
  Failed to import test module: nova.tests.unit.db.test_db_api
  Traceback (most recent call last):
File 
"/home/travis/build/dims/nova/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py",
 line 456, in _find_test_path
  module = self._get_module_from_name(name)
File 
"/home/travis/build/dims/nova/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py",
 line 395, in _get_module_from_name
  __import__(name)
File "nova/tests/unit/db/test_db_api.py", line 31, in 
  from oslo_db.sqlalchemy import test_base
File 
"/home/travis/build/dims/nova/.tox/py27/src/oslo.db/oslo_db/sqlalchemy/test_base.py",
 line 17, in 
  import testresources
  ImportError: No module named testresources

  https://travis-ci.org/dims/nova/jobs/83992423

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1503501/+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 1489059] Fix included in openstack/sahara 4.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/sahara 4.0.0.0b1 development
milestone.

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

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

Title:
  "db type could not be determined" running py34

Status in Aodh:
  Fix Committed
Status in cloudkitty:
  Fix Committed
Status in Glance:
  In Progress
Status in glance_store:
  Fix Committed
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-lib:
  In Progress
Status in OpenStack Identity (keystone):
  In Progress
Status in keystoneauth:
  In Progress
Status in keystonemiddleware:
  In Progress
Status in Manila:
  Fix Committed
Status in networking-midonet:
  New
Status in networking-ofagent:
  New
Status in neutron:
  Fix Committed
Status in python-glanceclient:
  In Progress
Status in python-keystoneclient:
  In Progress
Status in Sahara:
  Fix Released
Status in senlin:
  Fix Committed
Status in tap-as-a-service:
  New
Status in tempest:
  In Progress

Bug description:
  When running tox for the first time, the py34 execution fails with an
  error saying "db type could not be determined".

  This issue is know to be caused when the run of py27 preceeds py34 and
  can be solved erasing the .testrepository and running "tox -e py34"
  first of all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1489059/+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 1361360] Re: Eventlet green threads not released back to the pool leading to choking of new requests

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Eventlet green threads not released back to the pool leading to
  choking of new requests

Status in Cinder:
  Fix Released
Status in Cinder icehouse series:
  Fix Released
Status in Cinder juno series:
  Fix Released
Status in Glance:
  Fix Released
Status in Glance icehouse series:
  Fix Committed
Status in Glance juno series:
  Fix Released
Status in heat:
  Fix Released
Status in heat kilo series:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in OpenStack Identity (keystone) juno series:
  Fix Released
Status in OpenStack Identity (keystone) kilo series:
  Fix Released
Status in Manila:
  Fix Released
Status in neutron:
  Fix Released
Status in neutron icehouse series:
  Fix Released
Status in neutron juno series:
  Fix Committed
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) icehouse series:
  Fix Released
Status in OpenStack Security Advisory:
  Won't Fix
Status in OpenStack Security Notes:
  Won't Fix
Status in Sahara:
  Fix Released

Bug description:
  Currently reproduced  on Juno milestone 2. but this issue should be
  reproducible in all releases since its inception.

  It is possible to choke OpenStack API controller services using
  wsgi+eventlet library by simply not closing the client socket
  connection. Whenever a request is received by any OpenStack API
  service for example nova api service, eventlet library creates a green
  thread from the pool and starts processing the request. Even after the
  response is sent to the caller, the green thread is not returned back
  to the pool until the client socket connection is closed. This way,
  any malicious user can send many API requests to the API controller
  node and determine the wsgi pool size configured for the given service
  and then send those many requests to the service and after receiving
  the response, wait there infinitely doing nothing leading to
  disrupting services for other tenants. Even when service providers
  have enabled rate limiting feature, it is possible to choke the API
  services with a group (many tenants) attack.

  Following program illustrates choking of nova-api services (but this
  problem is omnipresent in all other OpenStack API Services using
  wsgi+eventlet)

  Note: I have explicitly set the wsi_default_pool_size default value to 10 in 
order to reproduce this problem in nova/wsgi.py.
  After you run the below program, you should try to invoke API
  

  import time
  import requests
  from multiprocessing import Process

  def request(number):
 #Port is important here
 path = 'http://127.0.0.1:8774/servers'
  try:
  response = requests.get(path)
  print "RESPONSE %s-%d" % (response.status_code, number)
  #during this sleep time, check if the client socket connection is 
released or not on the API controller node.
  time.sleep(1000)
  print “Thread %d complete" % number
  except requests.exceptions.RequestException as ex:
  print “Exception occurred %d-%s" % (number, str(ex))

  if __name__ == '__main__':
  processes = []
  for number in range(40):
  p = Process(target=request, args=(number,))
  p.start()
  processes.append(p)
  for p in processes:
  p.join()

  


  Presently, the wsgi server allows persist connections if you configure 
keepalive to True which is default.
  In order to close the client socket connection explicitly after the response 
is sent and read successfully by the client, you simply have to set keepalive 
to False when you create a wsgi server.

  Additional information: By default eventlet passes “Connection: keepalive” if 
keepalive is set to True when a response is sent to the client. But it doesn’t 
have capability to set the timeout and max parameter.
  For example.
  Keep-Alive: timeout=10, max=5

  Note: After we have disabled keepalive in all the OpenStack API
  service using wsgi library, then it might impact all existing
  applications built with the assumptions that OpenStack API services
  uses persistent connections. They might need to modify their
  applications if reconnection logic is not in place and also they might
  experience the performance has slowed down as it will need to
  reestablish the http connection for every request.

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

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

[Yahoo-eng-team] [Bug 1489059] Re: "db type could not be determined" running py34

2015-12-03 Thread Doug Hellmann

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

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

Title:
  "db type could not be determined" running py34

Status in Aodh:
  Fix Released
Status in cloudkitty:
  Fix Committed
Status in Glance:
  In Progress
Status in glance_store:
  Fix Committed
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-lib:
  In Progress
Status in OpenStack Identity (keystone):
  In Progress
Status in keystoneauth:
  In Progress
Status in keystonemiddleware:
  In Progress
Status in Manila:
  Fix Committed
Status in networking-midonet:
  New
Status in networking-ofagent:
  New
Status in neutron:
  Fix Committed
Status in python-glanceclient:
  In Progress
Status in python-keystoneclient:
  In Progress
Status in Sahara:
  Fix Released
Status in senlin:
  Fix Committed
Status in tap-as-a-service:
  New
Status in tempest:
  In Progress

Bug description:
  When running tox for the first time, the py34 execution fails with an
  error saying "db type could not be determined".

  This issue is know to be caused when the run of py27 preceeds py34 and
  can be solved erasing the .testrepository and running "tox -e py34"
  first of all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1489059/+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 1323975] Re: do not use default=None for config options

2015-12-03 Thread Doug Hellmann

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

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

Title:
  do not use default=None for config options

Status in Aodh:
  Fix Released
Status in Barbican:
  Fix Released
Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in congress:
  Fix Committed
Status in Designate:
  Fix Committed
Status in Glance:
  Fix Released
Status in glance_store:
  Fix Released
Status in Gnocchi:
  Fix Committed
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Released
Status in Mistral:
  Fix Released
Status in Murano:
  Fix Committed
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo-incubator:
  Fix Released
Status in oslo.messaging:
  Fix Released
Status in Rally:
  Fix Committed
Status in Sahara:
  Fix Released
Status in tempest:
  In Progress
Status in Trove:
  In Progress
Status in zaqar:
  Fix Released

Bug description:
  In the cfg module default=None is set as the default value. It's not
  necessary to set it again when defining config options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1323975/+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 1489059] Re: "db type could not be determined" running py34

2015-12-03 Thread Doug Hellmann

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

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

Title:
  "db type could not be determined" running py34

Status in Aodh:
  Fix Released
Status in cloudkitty:
  Fix Committed
Status in Glance:
  In Progress
Status in glance_store:
  Fix Committed
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-lib:
  In Progress
Status in OpenStack Identity (keystone):
  In Progress
Status in keystoneauth:
  In Progress
Status in keystonemiddleware:
  In Progress
Status in Manila:
  Fix Released
Status in networking-midonet:
  New
Status in networking-ofagent:
  New
Status in neutron:
  Fix Committed
Status in python-glanceclient:
  In Progress
Status in python-keystoneclient:
  In Progress
Status in Sahara:
  Fix Released
Status in senlin:
  Fix Committed
Status in tap-as-a-service:
  New
Status in tempest:
  In Progress

Bug description:
  When running tox for the first time, the py34 execution fails with an
  error saying "db type could not be determined".

  This issue is know to be caused when the run of py27 preceeds py34 and
  can be solved erasing the .testrepository and running "tox -e py34"
  first of all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1489059/+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 1179007] Re: Migrate build system to pbr

2015-12-03 Thread Doug Hellmann

** Changed in: python-openstackclient
   Status: Fix Committed => Fix Released

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

Title:
  Migrate build system to pbr

Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in Gear:
  New
Status in git-review:
  Fix Committed
Status in heat:
  Fix Released
Status in heat-cfntools:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in neutron:
  Fix Released
Status in oslo-incubator:
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-heatclient:
  Fix Released
Status in python-keystoneclient:
  Fix Released
Status in python-neutronclient:
  Fix Committed
Status in python-novaclient:
  Fix Released
Status in python-openstackclient:
  Fix Released
Status in python-swiftclient:
  Fix Released
Status in Python client library for Zaqar:
  Fix Released
Status in OpenStack Object Storage (swift):
  Fix Released
Status in Trove:
  Fix Released
Status in Zuul:
  New

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1

  openstack.common.setup and openstack.common.version are now in the
  standalone library pbr. Migrating involves moving build config to
  setup.cfg, copying in a stub setup.py file, adding pbr and d2to1 to the
  build depends, removing openstack.common.(setup|version) from the
  filesystem and from openstack-common.conf and making sure *.egg is in
  .gitignore.

   affects ceilometer
   affects cinder
   affects git-review
   affects heat-cfntools
   affects heat
   affects keystone
   affects openstack-ci
   affects oslo
   affects python-ceilometerclient
   affects python-cinderclient
   affects python-gear
   affects python-glanceclient
   affects python-heatclient
   affects python-keystoneclient
   affects python-novaclient
   affects python-openstackclient
   affects python-quantumclient
   affects python-swiftclient
   affects reddwarf
   affects swift
   affects zuul
  -BEGIN PGP SIGNATURE-
  Version: GnuPG v1.4.12 (GNU/Linux)
  Comment: Using GnuPG with undefined - http://www.enigmail.net/

  iEYEARECAAYFAlGObdUACgkQ2Jv7/VK1RgFlkACgzycOW0/rPvnLaXXX9/oqYA7q
  kGEAoMaEzGbFEAnsQA6+cEsKIUSMWAPD
  =W8F0
  -END PGP SIGNATURE-

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1179007/+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 1512207] Fix included in openstack/sahara 4.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/sahara 4.0.0.0b1 development
milestone.

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

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

Title:
  Fix usage of assertions

Status in OpenStack Identity (keystone):
  Fix Committed
Status in Manila:
  Fix Committed
Status in Sahara:
  Fix Released

Bug description:
  Manila  should use the specific assertion:

self.assertIsTrue/False(observed)

  instead of the generic assertion:

self.assertEqual(True/False, observed)

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1512207/+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 1475831] Fix included in openstack/python-openstackclient 2.0.0

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/python-openstackclient 2.0.0
release.

** Changed in: python-openstackclient
   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/1475831

Title:
  Some compute quotas are not being set

Status in OpenStack Compute (nova):
  Invalid
Status in python-openstackclient:
  Fix Released

Bug description:
  The following quotas are not being set correctly:

--injected-file-size
--injected-path-size
--properties
--secgroup-rules
--secgroups

  
  Because novaclient expects (novaclient/v2/shell.py):
  3877 _quota_resources = ['instances', 'cores', 'ram',
  3878 'floating_ips', 'fixed_ips', 'metadata_items',
  3879 'injected_files', 'injected_file_content_bytes',
  3880 'injected_file_path_bytes', 'key_pairs',
  3881 'security_groups', 'security_group_rules',
  3882 'server_groups', 'server_group_members']

  But we send (python-openstackclient/openstackclient/common/quota.py):

   30 COMPUTE_QUOTAS = {
   34 'injected_file_content_bytes': 'injected-file-size',
   35 'injected_file_path_bytes': 'injected-path-size',
   39 'metadata_items': 'properties',
   41 'security_group_rules': 'secgroup-rules',
   42 'security_groups': 'secgroups',
   43 }

  Current behavior
  # openstack quota set --injected-file-size 11 testproject_dx
  No quotas updated

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1475831/+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 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong

2015-12-03 Thread Doug Hellmann

** Changed in: manila
   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/1259292

Title:
  Some tests use assertEqual(observed, expected) , the argument order is
  wrong

Status in Barbican:
  In Progress
Status in Ceilometer:
  Invalid
Status in Cinder:
  Fix Released
Status in congress:
  In Progress
Status in Designate:
  Fix Committed
Status in Glance:
  Fix Released
Status in heat:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  Fix Committed
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Released
Status in Mistral:
  Fix Released
Status in Murano:
  Fix Committed
Status in OpenStack Compute (nova):
  Won't Fix
Status in python-ceilometerclient:
  Invalid
Status in python-cinderclient:
  Fix Released
Status in python-designateclient:
  Fix Committed
Status in python-mistralclient:
  Fix Released
Status in Python client library for Zaqar:
  Fix Released
Status in Sahara:
  Fix Released
Status in zaqar:
  Fix Committed

Bug description:
  The test cases will produce a confusing error message if the tests
  ever fail, so this is worth fixing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1259292/+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 1252649] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Images table isn't enable pagination on Project Panel

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  On Project dashboard, Images table displays all items on one page, we
  should enable pagination here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1252649/+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 1520598] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  several launch instance hits cause several requests

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Release: Kilo

  I have the 'new' launch instance dialog. After I clicked the launch
  instance button it takes a while to get the response, during this time
  it is possible to click the button again and another request will be
  triggered (resulting in multiple instances being created).

  Maybe https://bugs.launchpad.net/horizon/+bug/1461641 would be enough
  to acknowledge that the request was sent, but I would rather have the
  button disabled after the first submission to prevent the users from
  accidental creation of multiple instances.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1520598/+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 1520997] Re: Inconsistence in text of filter options

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Inconsistence in text of filter options

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  In some select filters (I found three pages, see screenshots) several
  texts of this filters, lack the equals symbol "=" like the rest of
  options of the same filter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1520997/+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 1513179] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  create volume workflow does not compute quota usage correctly

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The cinder quota on gigabytes is the sum of both volumes and
  snapshots. This is not correctly reflected in the create volume
  dialog, which allows the user to attempt to create volumes when there
  is not enough quota available, which results in a useless error
  message.

  To recreate the problem:
  1) on Project->Compute->Volumes create a 1G empty volume
  2) on the same panel create a snapshot of the new volume
  3) on Identity->Projects->[your project] choose Modify Quota and set the 
quota for "Total Size of Volumes and Snapshots (GB) " to 3G.
  4) Note that the quota usage (2 of 3) is correctly reflected on 
Project->Compute-Overview
  5) on Project->Compute->Volumes click Create Volume
  *Note the the quota is not accurately reflected
  6) Attempt to create a new volume of size 2G.
  *Note the obscure failure message "Error: Unable to create volume."

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1513179/+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 1508692] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Material Design Theme Needs to Pad the Content Correctly

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  A recent change fixed the sidebar height of the default theme but
  introduced a bug in the Large screen of the Material Design theme.

  
https://www.dropbox.com/s/w1t5gz1xoeskpch/Screenshot%202015-10-21%2014.40.11.png?dl=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1508692/+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 1506891] Re: JS Unit Test Branch Coverage is Low

2015-12-03 Thread Doug Hellmann

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

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

Title:
  JS Unit Test Branch Coverage is Low

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The JS unit test branch coverage is within 0.25% of its threshold,
  meaning slight variations may cause patches to trigger coverage
  failures.

  There are a few places where coverage is particularly bad that should
  be given more tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1506891/+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 1507703] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Karma for OSD doesn't load templates

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The openstack_dashboard Karma configuration is not looking in the
  right place for templates and other resources.  For example, you
  cannot use the 'templates' module to load templates for use in
  directive testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1507703/+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 1511109] Re: Python Tests are failing on Horizon because of incomplete mocking

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Python Tests are failing on Horizon because of incomplete mocking

Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in OpenStack Dashboard (Horizon) liberty series:
  Fix Committed

Bug description:
  openstack_dashboard.dashboards.project.instances.tests.InstanceTests
  are failing as the calls to flavor_list are not mocked on Nova.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1511109/+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 1511532] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Spelling Errors

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  While browsing around the Horizon repository, I found a few spelling
  errors that need correction.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1511532/+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 1516589] Re: Horizon still has legacy models.py files

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Horizon still has legacy models.py files

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  There a number of models.py files still in the source due to
  https://code.djangoproject.com/ticket/7198, which was closed a very
  long time ago.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1516589/+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 1511790] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Quickstart guide says to update environment_version which does not
  exist

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The horizon quickstart guide has an important note that tells the
  developer to update the environment_version variable in the
  run_tests.sh file whenever they change something in the environment
  [1].  The problem is this variable no longer exists [2].

  [1] 
http://docs.openstack.org/developer/horizon/quickstart.html#horizon-s-structure
  [2] https://review.openstack.org/119842

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1511790/+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 1513601] Re: add Italian localization

2015-12-03 Thread Doug Hellmann

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

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

Title:
  add Italian localization

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Our Horizon Italian localization is at approximately 100%.

  
https://translate.openstack.org/webtrans/translate?project=horizon=master=it=en%20#doc:horizon/locale/django

  The criteria is 90% complete. We should include in the list of
  languages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1513601/+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 1508526] Re: Karma test coverage reports are hidden by default

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Karma test coverage reports are hidden by default

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Karma test coverage reports are hidden files (.) by default.
  There's no reason for them to be hidden, and they are more accessible
  as regular files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1508526/+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 1517653] Re: subnet tests generating Http302 error in tests

2015-12-03 Thread Doug Hellmann

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

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

Title:
  subnet tests generating Http302 error in tests

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  .Error while checking action permissions.
  Traceback (most recent call last):
    File "/Documents/workspace/horizon/horizon/tables/base.py", line 1270, in 
_filter_action
  return action._allowed(request, datum) and row_matched
    File "/Documents/workspace/horizon/horizon/tables/actions.py", line 136, in 
_allowed
  return self.allowed(request, datum)
    File 
"/Documents/workspace/horizon/openstack_dashboard/dashboards/project/networks/subnets/tables.py",
 line 40, in allowed
  network = self.table._get_network()
    File "/Documents/workspace/horizon/horizon/utils/memoized.py", line 90, in 
wrapped
  value = cache[key] = func(*args, **kwargs)
    File 
"/Documents/workspace/horizon/openstack_dashboard/dashboards/project/networks/subnets/tables.py",
 line 145, in _get_network
  exceptions.handle(self.request, msg, redirect=self.failure_url)
    File "/Documents/workspace/horizon/horizon/exceptions.py", line 368, in 
handle
  log_method, log_entry, log_level)
    File "/Documents/workspace/horizon/horizon/exceptions.py", line 277, in 
handle_recoverable
  raise Http302(redirect)
  Http302

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1517653/+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 1517670] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  update rule name failing in the test

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Failed to update rule new name: Unexpected method call.  unexpected:-  
expected:+
  - function.__call__(, 
'h0881d38-c3eb-4fee-9763-12de3338041d', action=u'ALLOW', description=u'new 
desc', destination_ip_address=None, destination_port=u'1:65535', enabled=True, 
ip_version=u'', name=u'new name', protocol=u'ICMP', shared=False, 
source_ip_address='1.2.3.0/24', source_port=None) -> None
  + function.__call__(mox.IsA() , 
'h0881d38-c3eb-4fee-9763-12de3338041d', action='ALLOW', description='new desc', 
destination_ip_address=None, destination_port='1:65535', enabled=True, 
name='new name', protocol='ICMP', shared=False, source_ip_address='1.2.3.0/24', 
source_port=None) -> 
  ..Failed to update rule new name: Unexpected method call.  unexpected:-  
expected:+
  - function.__call__(, 
'f0881d38-c3eb-4fee-9763-12de3338041d', action=u'ALLOW', description=u'new 
desc', destination_ip_address=None, destination_port=u'1:65535', enabled=True, 
ip_version=u'', name=u'new name', protocol=u'ICMP', shared=False, 
source_ip_address='1.2.3.0/24', source_port=None) -> None
  + function.__call__(mox.IsA() , 
'f0881d38-c3eb-4fee-9763-12de3338041d', action='ALLOW', description='new desc', 
destination_ip_address=None, destination_port='1:65535', enabled=True, 
name='new name', protocol='ICMP', shared=False, source_ip_address='1.2.3.0/24', 
source_port=None) -> , , 'tenant_id': 
'1', 'enabled': True, 'source_ip_address': '1.2.3.0/24', 
'destination_ip_address': '4.5.6.7/32', 'firewall_policy_id': 
'abcdef-c3eb-4fee-9763-12de3338041e', 'action': 'deny', 'position': 2, 
'source_port': '80', 'shared': True, 'destination_port': '1:65535', 'id': 
'c6298a93-850f-4f64-b78a-959fd4f1e5df', 'name': ''}>], 'tenant_id': '1', 
 'id': 'abcdef-c3eb-4fee-9763-12de3338041e', 'shared': True, 'audited': True, 
'name': 'policy1'}>, 'tenant_id': '1', 'enabled': True, 'rule_id': 
'f0881d38-c3eb-4fee-9763-12de3338041d', 'source_ip_address': '1.2.3.0/24', 
'destination_ip_address': '4.5.6.7/32', 'firewall_policy_id': 
'abcdef-c3eb-4fee-9763-12de3338041e', 'action': 'ALLOW', 'position': 1, 
'source_port': '80', 'shared': True, 'destination_port': '1:65535', 'id': 
'f0881d38-c3eb-4fee-9763-12de3338041d', 'name': 'rule1'}>
  .Failed to update rule new name: Unexpected method call.  unexpected:-  
expected:+
  - function.__call__(, 
'f0881d38-c3eb-4fee-9763-12de3338041d', action=u'ALLOW', description=u'new 
desc', destination_ip_address=None, destination_port=u'1:65535', enabled=True, 
ip_version=u'', name=u'new name', protocol=None, shared=False, 
source_ip_address='1.2.3.0/24', source_port=None) -> None
  + function.__call__(mox.IsA() , 
'f0881d38-c3eb-4fee-9763-12de3338041d', action='ALLOW', description='new desc', 
destination_ip_address=None, destination_port='1:65535', enabled=True, 
name='new name', protocol=None, shared=False, source_ip_address='1.2.3.0/24', 
source_port=None) -> , , 'tenant_id': 
'1', 'enabled': True, 'source_ip_address': '1.2.3.0/24', 
'destination_ip_address': '4.5.6.7/32', 'firewall_policy_id': 
'abcdef-c3eb-4fee-9763-12de3338041e', 'action': 'deny', 'position': 2, 
'source_port': '80', 'shared': True, 'destination_port': '1:65535', 'id': 
'c6298a93-850f-4f64-b78a-959fd4f1e5df', 'name': ''}>], 'tenant_id': '1', 'i
 d': 'abcdef-c3eb-4fee-9763-12de3338041e', 'shared': True, 'audited': True, 
'name': 'policy1'}>, 'tenant_id': '1', 'enabled': True, 'rule_id': 
'f0881d38-c3eb-4fee-9763-12de3338041d', 'source_ip_address': '1.2.3.0/24', 
'destination_ip_address': '4.5.6.7/32', 'firewall_policy_id': 
'abcdef-c3eb-4fee-9763-12de3338041e', 'action': 'ALLOW', 'position': 1, 
'source_port': '80', 'shared': True, 'destination_port': '1:65535', 'id': 
'f0881d38-c3eb-4fee-9763-12de3338041d', 'name': 'rule1'}>

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1517670/+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 1506942] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  JS unit test statement coverage is low

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The JS unit test statement coverage in the ./horizon project has a
  threshold of 68%...way too low.

  There are a few places where coverage is particularly bad that should
  be given more tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1506942/+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 1507563] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  WEBROOT not set correctly in 500 error page

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Template for 500 error uses CONF.WEBROOT to set Home link, where CONF
  is loaded by templatetag from horizon.conf. But in
  horizon/conf/__init__.py, only HORIZON_CONF is set and nothing else.
  As a result, 500.html is rendered with empty url for Home link.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1507563/+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 1505863] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  caret button shouldn't be disabled

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Currently, in action dropdown menu with split-button, when the action
  disabled, the caret button is disabled as well, this cause it's
  impossible to interact with other actions in the dropdown. Caret
  button should be always enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1505863/+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 1506565] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Add correct license for simple modal

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Somewhere along the way, the license for simple modal was mishandled.
  This should be corrected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1506565/+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 1506177] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  vm_state 'soft-delete' should be 'soft_deleted'

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  In

  
https://github.com/openstack/nova/blob/4cf6ef68199183697a0209751575f88fe5b2a733/nova/compute/vm_states.py#L40

  the vm_state SOFT_DELETED is mapped to the value 'soft-delete.  All
  the other vm_states are mapped to values that match their state in
  lower case, so to be consistent SOFT_DELETED should map to
  'soft_deleted'.

  I searched through the Nova code and did not find any references to
  soft-delete, so a change should not cause any breakage.

  In Horizon's instance table here:

  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/tables.py#L1001

  the value expected is 'soft_deleted', so changing the value in nova to
  be consistent should help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1506177/+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 1507515] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  wrong url in preview stack detail

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  In preview stack detail page, URL for the cancel button redirecting to
  the 'access and security' table.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1507515/+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 1493433] Re: "No volume type" in volume create screen is not a great default

2015-12-03 Thread Doug Hellmann

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

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

Title:
  "No volume type" in volume create screen is not a great default

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  If a deployment has defined volume types, having "No volume type" show
  up as the first item in the list is not a great experience.

  There is also this api call which could be used to determine which
  item should be selected:

  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/cinder.py#L488

  (def volume_type_default(request):)

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1493433/+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 1494166] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Error message is not specific and distinct when the  Qos Spec name
  already exist

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  When input a "QoS Spec" name that already exist in create "QoS Spec" modal 
form, we will see the error message: "Unable to create QoS Spec" in the top 
right corner of the page, this error message is not specific and clear.
  If we provide specific and clear error message: 'QoS Spec name "%s" already 
exists.' beside the name field,  it will be more better.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1494166/+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 1491180] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Adding ifAllowed method to policy

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Policy current returns a response object containing the allowed field,
  which either is true or false. To simplify this a bit, we need a
  wrapper method ifAllowed that would return a promise that either
  resolves or rejects. If it resolves, the success handler is called,
  and if it rejects, the error handler is called. This is more useful in
  practice and negates the need to check the response object.
  Furthermore, this is useful for creating a hz-if-policies directive in
  the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1491180/+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 1495976] Re: Image location help text only reference http

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Image location help text only reference http

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Glance supports http/https url to upload, but Image location field
  help text only reference http, should add https as well to keep
  consistent with the backend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1495976/+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 1490559] Re: admin not able to set 'maintenance' state for volumes

2015-12-03 Thread Doug Hellmann

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

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

Title:
  admin not able to set 'maintenance' state for volumes

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  admin not able to set the status as 'maintenance' from horizon since
  the the options doesn't contain.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1490559/+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 1494149] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Image form "format" field is not being auto-completed (again)

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Selenium is again detecting (correctly) that the Create Image form
  "format" field isn't being auto-filled when a file is selected (eg. a
  .iso).

  It appears that the angular ImageFormController isn't even active in
  the page, though the reason hasn't been determined yet. I suspect a
  recent commit has broken it because it was working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1494149/+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 1492182] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  word spelling mistake in django.po

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  In */LC_MESSAGES/django.po file, original description is as following:

  
  #: dashboards/project/networks/ports/tables.py:62
  msgctxt "status of a neteork port"
  msgid "Error"
  msgstr ""
  

   I think " neteork " should be "network " .

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1492182/+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 1490031] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Refactor status and admin state translation code to improve
  readability

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  In some of the dashboard 'views.py' files, there is code that enables
  the detail status and, when applicable, admin state labels to be
  translated.  The current coding style of these sections is hard to
  read.  Any and all sections of code that use this style should be
  refactored to enhance the code readability.

  Example:

  Current hard to read code: 
  
https://github.com/openstack/horizon/blob/943a57b536a40f44053c0161f708a78e22469ed0/openstack_dashboard/dashboards/project/images/images/views.py#L112

  Possible refactor:
  status_label_dict = {value.lower(): label for (value, label) in 
project_tables.ImagesTable.STATUS_DISPLAY_CHOICES}
  image.status_label = status_label_dict.get(image.status.lower(), image.status)

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1490031/+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 1493216] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Stacks event tab wouldn't display data

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  I deploy new devstack environment and launch new stacks.
  Enter the stack page then go to event tab.
  It will not display event and only show loading, attach file is screen 
snapshot.
  Console will have one 500 response at following link
  
http://ip/dashboard/project/stacks/stack/92f0c65a-6dd3-43c8-964f-6e45c94d3b3e/?tab=stack_details__events
  Following link is django log.
  http://paste.openstack.org/show/449776/

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1493216/+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 1496953] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Instance status values in CSV summary are not translated

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  I prepared my environment using the pseudo translation tool to use
  German.

  When I navigate to the Admin->System->Overview and click on the
  "Download CSV Summary" button, the instance status/state values
  ("Active", "Stopped") in the generated csv file are not translated
  into the locale I'm using.  However when I navigate to the instance
  the Status values are translated.

  You can see in the attached screen shot the translated values from the
  instance page and the non-translated values from the csv file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1496953/+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 1497295] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Incorrect actions on Admin -> Subnet Details

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The table actions generated on the Subnet Details page under Admin/
  Networks incorrectly use the project URLS and views, rather than the
  admin ones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1497295/+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 1472281] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  router:external networks are not visible

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Since Icehouse, the common Neutron policy is to have external networks
  with router:external = True and shared=False (used to be shared=True
  before)

  The issue is that we can not see the external network to obtain its ID
  (and its ID is necessary e.g. in the orchestration panel when
  launching a heat template)

  Currently, a user needs to use the CLI to obtain the public network
  ID.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1472281/+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 1484068] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Confusing confirmation message for disassociating floating IP from VIP

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Since there's no separate VIPs tab for load balancers dashboard,
  pool's id is used for generating confirmation messages even if VIP
  action is chosen.  Thus while disassociating floating IP from VIP, the
  following message is shown: 'You have selected . Please confirm your selection.' It would be nice to add a
  few words to this message to make it clearer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1484068/+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 1482094] Re: Processing Bar is Shown even after the action is complete

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Processing Bar is Shown even after the action is complete

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Glance service:-

  - Deactivate an image using curl command from the api.
  - The same image is shown as the status as deactivated in the curl command 
status.
  - Go to Horizon Dashboard, The same image is shown as deactivated but there 
is one processing bar in front of the Deactivated column which shows the action 
is in progress and is not completed.
  - As for informational purpose this is wrong once deactivated tag is there it 
should not show the processing bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1482094/+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 1487251] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Creating new user does not require project

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  When creating a new user, adding the user to a project is optional.
  The REST api needs to respect this.

  Reference:
  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/rest/keystone.py#L91

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1487251/+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 1496164] Re: Building on Horizon tutorial startdash command broken

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Building on Horizon tutorial startdash command  broken

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  http://docs.openstack.org/developer/horizon/topics/tutorial.html

  Run the following commands:

  

  mkdir openstack_dashboard/dashboards/mydashboard

  ./run_tests.sh -m startdash mydashboard \
--target openstack_dashboard/dashboards/mydashboard

  

  startdash command is broken.  Gives "KeyError: extensions" on this
  line:

  
https://github.com/openstack/horizon/blob/master/horizon/management/commands/startdash.py#L50

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1496164/+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 1501513] Fix included in openstack/horizon 9.0.0.0b1

2015-12-03 Thread Doug Hellmann

This issue was fixed in the openstack/horizon 9.0.0.0b1 development
milestone.

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

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

Title:
  Controllers in app/tech-debt are not being tested

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  app/tech-debt/image-form.controller.js and app/tech-debt/hz-namespace-
  resource-type-form.controller.js are not being covered at all by tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1501513/+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 1507558] Re: Ironic gate breakage: deployed VM's do not get DHCP

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Ironic gate breakage: deployed VM's do not get DHCP

Status in Ironic:
  Invalid
Status in neutron:
  Fix Released

Bug description:
  See e.g. https://review.openstack.org/#/c/234186/. It started around
  midnight UTC, Mon Oct 19.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ironic/+bug/1507558/+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 1505295] Re: Tox tests failing with AttributeError

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Tox tests failing with AttributeError

Status in Cinder:
  Fix Released
Status in Designate:
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  In Progress
Status in openstack-ansible:
  Fix Released

Bug description:
  Currently all tests run in Jenkins python27 and python34 are failing
  with an AttributeError, saying that "'str' has no attribute 'DEALER'",
  as well as an AssertionError on assert TRANSPORT is not None in
  cinder/rpc.py.

  An example of the full traceback of the failure can be found here:

   http://paste.openstack.org/show/476040/

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1505295/+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 1504892] Re: create a keystone.version package

2015-12-03 Thread Doug Hellmann

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

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

Title:
  create a keystone.version package

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  the logic for handling the way keystone builds a WSGI app per API
  interface + version (v2 vs v3) should be isolated to it's own package
  in keystone (such as keystone.version).

  there are entry points for these files in keystone-paste.ini (pre-
  Liberty) and setup.cfg (as of Liberty), so we need to make sure this
  work is tracked and documented.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1504892/+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 1505374] Re: Unit tests failing with oslo.policy 0.12.0

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Unit tests failing with oslo.policy 0.12.0

Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  Fix Released

Bug description:
  
  oslo.policy 0.12.0 was released recently, and this caused a couple keystone 
unit tests to fail. The new release has a change to use requests rather than 
urllib, and keystone's unit tests were assuming that oslo.policy was 
implemented using urllib (by mocking the response).

  failing tests:

   keystone.tests.unit.test_policy.PolicyTestCase.test_enforce_http_true
   keystone.tests.unit.test_policy.PolicyTestCase.test_enforce_http_false

  Keystone doesn't need to test these internal implementation details of
  oslo.policy, let's just assume it works as designed and they have
  their own tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1505374/+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 1505259] Re: Functional gate broken due to configure_for_func_testing.sh inability to configure DB backends

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Functional gate broken due to configure_for_func_testing.sh inability
  to configure DB backends

Status in neutron:
  Fix Released

Bug description:
  After https://review.openstack.org/#/c/233106/ was merged to Devstack, the 
configure_for_func_testing.sh script is unable to configure both DB backends, 
and test setup eventually fails as such:
  
http://logs.openstack.org/68/233068/5/check/gate-neutron-dsvm-functional/6c27c46/console.html#_2015-10-12_13_29_18_446

  This happens because the Postgres disable is successful, but the Postgres 
enable is ignored by Devstack. The issue is here:
  
https://github.com/openstack/neutron/blob/master/tools/configure_for_func_testing.sh#L127

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1505259/+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 1504891] Re: keystone-paste.ini docs for deployers are out of date

2015-12-03 Thread Doug Hellmann

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

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

Title:
  keystone-paste.ini docs for deployers are out of date

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  The docs in this section: http://docs.openstack.org/developer/keystone
  /http-api.html#i-am-a-deployer

  reference an editable section in keystone-paste.ini
  ([app:service_v3]).

  this section is now managed by entry points in setup.cfg

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1504891/+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 1507944] Re: Incorrect example in federated rules documentation

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Incorrect example in federated rules documentation

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  There is a major error in one of the examples in the mapping rules
  documentation [0]

  When mapping groups by names along with blacklist/whitelist keywords
  the correct structure is:

  "local": [
  {
  "groups": "{0}",
  "domain": {
  "id": DEVELOPER_GROUP_DOMAIN_ID
  }
  },
  ]

  
  whereas one can find following in the documentation:

  "local": [
  {
  "groups": {
  "name": "{1}",
  "domain": {
  "id": "0cd5e9"
  }
  }
  }
  ],
   

  This should be fixed as soon as possible as uses following guidance
  will fail with their setup.

  
  [0] http://docs.openstack.org/developer/keystone/mapping_combinations.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1507944/+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 1507752] Re: Rally change breaks Keystone rally job

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Rally change breaks Keystone rally job

Status in OpenStack Identity (keystone):
  Fix Released
Status in Rally:
  Fix Committed

Bug description:
  This change:
  
http://git.openstack.org/cgit/openstack/rally/diff/rally/plugins/openstack/scenarios/keystone/basic.py?id=f871de842214f103b4841160e90c73cd98c4f5ad

  Breaks this job:
  
http://logs.openstack.org/74/231574/6/check/gate-rally-dsvm-keystone/57d4dfc/rally-plot/results.html.gz#/KeystoneBasic.create_user/failures

  Traceback:
  Traceback (most recent call last):
File "/opt/stack/new/rally/rally/task/runner.py", line 64, in 
_run_scenario_once
  method_name)(**kwargs) or scenario_output
File 
"/opt/stack/new/rally/rally/plugins/openstack/scenarios/keystone/basic.py", 
line 33, in create_user
  self._user_create(**kwargs)
File "/opt/stack/new/rally/rally/task/atomic.py", line 83, in 
func_atomic_actions
  f = func(self, *args, **kwargs)
File 
"/opt/stack/new/rally/rally/plugins/openstack/scenarios/keystone/utils.py", 
line 45, in _user_create
  name, password=password, email=email, **kwargs)
  TypeError: create() got an unexpected keyword argument 'name_length'

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1507752/+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 1506986] Re: documentation needs to be clarified about differences between subtree_as_ids and subtree_as_list

2015-12-03 Thread Doug Hellmann

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

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

Title:
  documentation needs to be clarified about differences between
  subtree_as_ids and subtree_as_list

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  The current documentation in the idendity API V3 just explain what is the API 
returns about subtree_as_ids and subtree_as_list.
  The same documentation needs to be add for parents_as_ids and parents_as_list
  We need to explain what is the difference in the API response between this 
two operations and what is the excepted use for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1506986/+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 1503501] Re: oslo.db no longer requires testresources and testscenarios packages

2015-12-03 Thread Doug Hellmann

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

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

Title:
  oslo.db no longer requires testresources and testscenarios packages

Status in Cinder:
  Fix Released
Status in Glance:
  Fix Released
Status in heat:
  Fix Released
Status in heat liberty series:
  Fix Committed
Status in Ironic:
  Fix Committed
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in Sahara:
  Fix Released
Status in Sahara liberty series:
  Fix Committed
Status in Sahara mitaka series:
  Fix Released

Bug description:
  As of https://review.openstack.org/#/c/217347/ oslo.db no longer has
  testresources or testscenarios in its requirements, So next release of
  oslo.db will break several projects. These project that use fixtures
  from oslo.db should add these to their requirements if they need it.

  Example from Nova:
  ${PYTHON:-python} -m subunit.run discover -t ./ ${OS_TEST_PATH:-./nova/tests} 
--list 
  ---Non-zero exit code (2) from test listing.
  error: testr failed (3) 
  import errors ---
  Failed to import test module: nova.tests.unit.db.test_db_api
  Traceback (most recent call last):
File 
"/home/travis/build/dims/nova/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py",
 line 456, in _find_test_path
  module = self._get_module_from_name(name)
File 
"/home/travis/build/dims/nova/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py",
 line 395, in _get_module_from_name
  __import__(name)
File "nova/tests/unit/db/test_db_api.py", line 31, in 
  from oslo_db.sqlalchemy import test_base
File 
"/home/travis/build/dims/nova/.tox/py27/src/oslo.db/oslo_db/sqlalchemy/test_base.py",
 line 17, in 
  import testresources
  ImportError: No module named testresources

  https://travis-ci.org/dims/nova/jobs/83992423

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1503501/+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 1519078] Re: Freescale vendor code complete decomposition

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Freescale vendor code complete decomposition

Status in neutron:
  Fix Released

Bug description:
  The Freescale service plugin and ML2 mechanism driver should be
  completely removed from the neutron tree. All Freescale code and
  artifacts should be contained in an external freescale repository.

  See http://docs.openstack.org/developer/neutron/devref/contribute.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1519078/+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 1507602] Re: _get_router() sometimes raises RouterNotFound when called from under create_floatingip

2015-12-03 Thread Doug Hellmann

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

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

Title:
  _get_router() sometimes raises RouterNotFound when called from under
  create_floatingip

Status in neutron:
  Fix Released

Bug description:
  https://review.openstack.org/#/c/215136/ was merged in the gate and
  broke Ironic. It seems we have a weird issue in neutron db code that
  makes fetch on router_id raise NotFound when updating a floating IP.

  The patch was reverted in master, but we should understand what went
  wrong, and maybe introduce additional testing that would not allow the
  issue to sneak in.

  We also should look into another patch that made similar change for
  Create on FIP: https://review.openstack.org/#/c/231031/ It may also
  break something.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1507602/+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 1507522] Re: fwaas lacks scenario tests

2015-12-03 Thread Doug Hellmann

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

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

Title:
  fwaas lacks scenario tests

Status in neutron:
  Fix Released

Bug description:
  fwaas lacks tempest scenario tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1507522/+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 1506818] Re: RetryRequest need a arg in _lock_subnetpool method

2015-12-03 Thread Doug Hellmann

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

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

Title:
  RetryRequest need a arg in _lock_subnetpool method

Status in neutron:
  Fix Released

Bug description:
  as defined in oslo db, RetryRequest need a arg

  https://github.com/openstack/oslo.db/blob/master/oslo_db/exception.py#L206

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1506818/+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 1507314] Re: device_driver default in LBaaS needs adjustment

2015-12-03 Thread Doug Hellmann

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

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

Title:
  device_driver default in LBaaS needs adjustment

Status in neutron:
  Fix Released

Bug description:
  The default lbaas_agent.ini of neutron-lbaas lists this:

   # Default is:
  # device_driver = 
neutron.services.loadbalancer.drivers.haproxy.namespace_driver.HaproxyNSDriver

  However, the actual default, as seen in
  neutron_lbaas/services/loadbalancer/agent/agent_manager.py is:

  
  OPTS = [
  cfg.MultiStrOpt(
  'device_driver',
  default=['neutron_lbaas.services.loadbalancer.drivers'
   '.haproxy.namespace_driver.HaproxyNSDriver'],

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1507314/+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 1506794] Re: VPNaaS: Active VPN connection goes down after controller shutdown/start

2015-12-03 Thread Doug Hellmann

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

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

Title:
VPNaaS: Active VPN connection goes down after controller
shutdown/start

Status in neutron:
Fix Released

Bug description:
Ubuntu 14.04 + OpenSwan 1:2.6.38-1

Environment with 3 controllers and 2 computes

Steps to reproduce:
1. Create VPN connection between tenant1 and tenant2 and check that it's
active
2. Find a controller where one of the routers-participants of VPN connection
is scheduled (tenant1's router, for example)
3. Shutdown this controller, wait some time and check that tenant1's router
is rescheduled successfully, and VPN connection is restored
4. Start the controller which was shut downed and wait some time while it's
completely booted
5. Reschedule tenant1's router back to its origin controller, which was under
shutdown/start, wait some time and check that tenant1's router is rescheduled
successfully, and VPN connection is restored

Actual result: tenant1's router is rescheduled, VMs can ping external
hosts, but VPN connection goes to DOWN state on tenant1's side with
the following error in vpn-agent.log on a controller where tenant1's
router was rescheduled back in p.5:
http://paste.openstack.org/show/476459/

Analysis:
Pluto processes are running in qrouter namespace (or snat in case of DVR).
When a controller is being shut down all namespaces get deleted (as they are
stored in tmpfs), but pluto .pid and .ctl files remain as they are stored in
/opt/stack/data/neutron/ipsec//var/run/.

Then, when router is rescheduled back to the origin controller, vpn
agent attempts to start pluto process and pluto fails when it finds
that a .pid file already exists. Such behavior of pluto is determined
by the flags that are used to open this file [1],[2] and it is most
probably a defense against accidental rewriting of .pid file .

As it is not a pluto bug, the solution might be to add a workaround to VPNaaS
that will clean-up .ctl and .pid files on start-up.
Essentially, the same approach was used for LibreSwan driver [3] so we just
need to do some refactoring to make this approach shared for OpenSwan and
LibreSwan .

[1]
https://github.com/xelerance/Openswan/blob/master/programs/pluto/plutomain.c#L258-L259
[2]
https://github.com/libreswan/libreswan/blob/master/programs/pluto/plutomain.c#L231-L232
[3]
https://github.com/openstack/neutron-vpnaas/commit/00b633d284f0f21aa380fa47a270c612ebef0795

P.S.
Another way to reproduce this failure is to replace steps 3-5 with:
3. Send kill -9 to the pluto process on that controller
4. Remove tenant1's router from agent running on that controller and then
schedule it back.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1506794/+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 1515100] Re: Unnecessary "ugettext_lazy" procedure against name

2015-12-03 Thread Doug Hellmann

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

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

Title:
  Unnecessary "ugettext_lazy" procedure against name

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Unnecessary "ugettext_lazy" procedure against database instance name
  and image name exist in detail view settings in views.py.

  
  openstack_dashboard/contrib/trove/content/databases/views.py

  class DetailView(tabs.TabView):
  tab_group_class = project_tabs.ImageDetailTabs
  template_name = 'horizon/common/_detail.html'
  page_title = _("{{ image.name }}")
  ~

  openstack_dashboard/dashboards/project/images/images/views.py

  class DetailView(horizon_tabs.TabbedTableView):
  tab_group_class = tabs.InstanceDetailTabs
  template_name = 'horizon/common/_detail.html'
  page_title = _("{{ instance.name }}")
  ~~~

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

1 2 3 4 5 6 7 8 9 10 >

1 - 100 of 1086 matches

Mail list logo