[Yahoo-eng-team] [Bug 1533518] [NEW] Remove 'validate' key in 'type:dict_or_nodata' type in resource attribute map

[Bo Chi]

Public bug reported:

In neutron/extensions/l3_ext_gw_mode.py, there's another 'validate' key in the 
'validate' section of type 'type:dict_or_nodata', this cause the validation is 
not performed.
Because in _validate_dict_item(), it checks key name that starts with 'type:', 
and perform the validation.

EXTENDED_ATTRIBUTES_2_0 = { 
'routers': {l3.EXTERNAL_GW_INFO:
{'allow_post': True,
 'allow_put': True,
 'is_visible': True,
 'default': None,
 'enforce_policy': True,
 'validate':
 {'type:dict_or_nodata':
  {'network_id': {'type:uuid': None, 'required': True},
   'enable_snat': {'type:boolean': None, 'required': False,
   'convert_to': attrs.convert_to_boolean},
   'external_fixed_ips': {
   'convert_list_to': attrs.convert_kvp_list_to_dict,
   'validate': {'type:fixed_ips': None},
< error
   'default': None,
   'required': False}
   }   
  

The correct format is :

'external_fixed_ips': {
   'convert_list_to': attrs.convert_kvp_list_to_dict,
   'type:fixed_ips': None,  
  < should be
   'default': None,
   'required': False}
   }

** Affects: neutron
 Importance: Undecided
 Assignee: Bo Chi (bochi-michael)
 Status: In Progress

** Changed in: neutron
 Assignee: (unassigned) => Bo Chi (bochi-michael)

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

Title:
  Remove 'validate' key in 'type:dict_or_nodata' type in resource
  attribute map

Status in neutron:
  In Progress

Bug description:
  In neutron/extensions/l3_ext_gw_mode.py, there's another 'validate' key in 
the 'validate' section of type 'type:dict_or_nodata', this cause the validation 
is not performed.
  Because in _validate_dict_item(), it checks key name that starts with 
'type:', and perform the validation.

  EXTENDED_ATTRIBUTES_2_0 = { 
  'routers': {l3.EXTERNAL_GW_INFO:
  {'allow_post': True,
   'allow_put': True,
   'is_visible': True,
   'default': None,
   'enforce_policy': True,
   'validate':
   {'type:dict_or_nodata':
{'network_id': {'type:uuid': None, 'required': True},
 'enable_snat': {'type:boolean': None, 'required': False,
 'convert_to': attrs.convert_to_boolean},
 'external_fixed_ips': {
 'convert_list_to': attrs.convert_kvp_list_to_dict,
 'validate': {'type:fixed_ips': None},  
  < error
 'default': None,
 'required': False}
 }   


  The correct format is :

  'external_fixed_ips': {
 'convert_list_to': attrs.convert_kvp_list_to_dict,
 'type:fixed_ips': None,
< should be
 'default': None,
 'required': False}
 }

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1533518/+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 1533514] [NEW] FilterAction does not filter rows as specified fields

[Wang Bo]

Public bug reported:

In Identity/Projects panel page, input filter string into  Filter box.
The result rows are not expected.

Refer to:
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/identity/projects/tables.py#L171

It expected the rows which filed "tenant.name" containing the input
string. However, except "tenant.name" any other fileds containing the
string in the rows has been selected as result.

** Affects: horizon
 Importance: Undecided
 Assignee: Wang Bo (chestack)
 Status: New

** Attachment added: "filteraction.png"
   
https://bugs.launchpad.net/bugs/1533514/+attachment/4549042/+files/filteraction.png

** Changed in: horizon
 Assignee: (unassigned) => Wang Bo (chestack)

** Description changed:

  In Identity/Projects panel page, input filter string into  Filter box.
- The filtered rows are not expected.
+ The result rows are not expected.
  
  Refer to:
  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/identity/projects/tables.py#L171
  
- It want the rows in which only filed "tenant.name" containing the input
+ It expected the rows which filed "tenant.name" containing the input
  string. However, except "tenant.name" any other fileds containing the
  string in the rows has been selected as result.

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

Title:
  FilterAction does not filter rows as specified fields

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  In Identity/Projects panel page, input filter string into  Filter box.
  The result rows are not expected.

  Refer to:
  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/identity/projects/tables.py#L171

  It expected the rows which filed "tenant.name" containing the input
  string. However, except "tenant.name" any other fileds containing the
  string in the rows has been selected as result.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1533514/+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 1533487] Re: test_create_server_with_personality fails on the gate

[Matthew Treinish]

Well I was gonna suggest the dashboard because it will show this
information, but the job is non-voting check only when it would fail so
that doesn't help. As a cool aside it does show that the change:
https://review.openstack.org/#/c/257493/ makes it noticeably slower:

http://status.openstack.org/openstack-
health/#/test/tempest.api.compute.servers.test_server_personality.ServerPersonalityTestJSON.test_create_server_with_personality

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

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

Title:
  test_create_server_with_personality fails on the gate

Status in OpenStack Compute (nova):
  New
Status in tempest:
  New

Bug description:
  http://logs.openstack.org/54/264354/8/check/gate-tempest-dsvm-neutron-
  full-ssh/2e7adb0/logs/testr_results.html.gz

  Traceback (most recent call last):
File "tempest/api/compute/servers/test_server_personality.py", line 69, in 
test_create_server_with_personality
  'sudo cat %s' % file_path))
File "tempest/common/utils/linux/remote_client.py", line 56, in exec_command
  return self.ssh_client.exec_command(cmd)
File 
"/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py",
 line 167, in exec_command
  stderr=err_data, stdout=out_data)
  tempest_lib.exceptions.SSHExecCommandFailed: Command 'set -eu -o pipefail; 
PATH=$PATH:/sbin; sudo cat /test.txt', exit status: 1, stderr:
  cat: can't open '/test.txt': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1533487/+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 1277104] Re: wrong order of assertEquals args

[Yatin Kumbhare]

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

** Changed in: manila
 Assignee: (unassigned) => Yatin Kumbhare (yatinkumbhare-c)

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

Title:
  wrong order of assertEquals args

Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in Glance:
  Fix Released
Status in ironic-python-agent:
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  New
Status in oslo.messaging:
  Fix Released
Status in oslo.policy:
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-ironicclient:
  Fix Released
Status in python-novaclient:
  Fix Released
Status in python-openstackclient:
  Fix Released
Status in Python client library for Sahara:
  Fix Released
Status in python-solumclient:
  New
Status in python-swiftclient:
  Won't Fix
Status in python-troveclient:
  Fix Released
Status in Rally:
  Confirmed
Status in Trove:
  Fix Released

Bug description:
  Args of assertEquals method in ceilometer.tests are arranged in wrong order. 
In result when test fails it shows incorrect information about observed and 
actual data. It's found more than 2000 times.
  Right order of arguments is "expected, actual".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1277104/+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 1533487] [NEW] test_create_server_with_personality fails on the gate

[Ken'ichi Ohmichi]

Public bug reported:

http://logs.openstack.org/54/264354/8/check/gate-tempest-dsvm-neutron-
full-ssh/2e7adb0/logs/testr_results.html.gz

Traceback (most recent call last):
  File "tempest/api/compute/servers/test_server_personality.py", line 69, in 
test_create_server_with_personality
'sudo cat %s' % file_path))
  File "tempest/common/utils/linux/remote_client.py", line 56, in exec_command
return self.ssh_client.exec_command(cmd)
  File 
"/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py",
 line 167, in exec_command
stderr=err_data, stdout=out_data)
tempest_lib.exceptions.SSHExecCommandFailed: Command 'set -eu -o pipefail; 
PATH=$PATH:/sbin; sudo cat /test.txt', exit status: 1, stderr:
cat: can't open '/test.txt': No such file or directory

** Affects: nova
 Importance: Undecided
 Status: New

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

Title:
  test_create_server_with_personality fails on the gate

Status in OpenStack Compute (nova):
  New

Bug description:
  http://logs.openstack.org/54/264354/8/check/gate-tempest-dsvm-neutron-
  full-ssh/2e7adb0/logs/testr_results.html.gz

  Traceback (most recent call last):
File "tempest/api/compute/servers/test_server_personality.py", line 69, in 
test_create_server_with_personality
  'sudo cat %s' % file_path))
File "tempest/common/utils/linux/remote_client.py", line 56, in exec_command
  return self.ssh_client.exec_command(cmd)
File 
"/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py",
 line 167, in exec_command
  stderr=err_data, stdout=out_data)
  tempest_lib.exceptions.SSHExecCommandFailed: Command 'set -eu -o pipefail; 
PATH=$PATH:/sbin; sudo cat /test.txt', exit status: 1, stderr:
  cat: can't open '/test.txt': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1533487/+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 1334109] Re: Lock wait timeout updating router's gw_port_id

[Launchpad Bug Tracker]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
   Status: Incomplete => Expired

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

Title:
  Lock wait timeout updating router's gw_port_id

Status in neutron:
  Expired

Bug description:
  Traceback:

   TRACE neutron.api.v2.resource Traceback (most recent call last):
   TRACE neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/api/v2/resource.py", line 87, in resource
   TRACE neutron.api.v2.resource result = method(request=request, **args)
   TRACE neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/api/v2/base.py", line 419, in create
   TRACE neutron.api.v2.resource obj = obj_creator(request.context, 
**kwargs)
   TRACE neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/db/l3_db.py", line 132, in create_router
   TRACE neutron.api.v2.resource self._update_router_gw_info(context, 
router_db['id'], gw_info)
   TRACE neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/db/l3_gwmode_db.py", line 58, in 
_update_router_gw_info
   TRACE neutron.api.v2.resource context, router_id, info, router=router)
   TRACE neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/db/l3_db.py", line 214, in 
_update_router_gw_info
   TRACE neutron.api.v2.resource self._create_router_gw_port(context, 
router, network_id)
   TRACE neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/db/l3_db.py", line 175, in 
_create_router_gw_port
   TRACE neutron.api.v2.resource context.session.add(router)
   TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 463, 
in __exit__
   TRACE neutron.api.v2.resource self.rollback()
   TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/util/langhelpers.py", line 
57, in __exit__
   TRACE neutron.api.v2.resource compat.reraise(exc_type, exc_value, exc_tb)
   TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 460, 
in __exit__
   TRACE neutron.api.v2.resource self.commit()
   TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 370, 
in commit
   TRACE neutron.api.v2.resource self._prepare_impl()
   TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 350, 
in _prepare_impl
   TRACE neutron.api.v2.resource self.session.flush()
   TRACE neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/openstack/common/db/sqlalchemy/session.py", 
line 597, in _wrap
   TRACE neutron.api.v2.resource return f(*args, **kwargs)
   TRACE neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/openstack/common/db/sqlalchemy/session.py", 
line 836, in flush
   TRACE neutron.api.v2.resource return super(Session, self).flush(*args, 
**kwargs)
   TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1907, 
in flush
   TRACE neutron.api.v2.resource self._flush(objects)
   TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 2025, 
in _flush
   TRACE neutron.api.v2.resource 
transaction.rollback(_capture_exception=True)
   TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/util/langhelpers.py", line 
57, in __exit__
   TRACE neutron.api.v2.resource compat.reraise(exc_type, exc_value, exc_tb)
   TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1989, 
in _flush
   TRACE neutron.api.v2.resource flush_context.execute()
   TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line 
371, in execute
   TRACE neutron.api.v2.resource rec.execute(self)
   TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line 
524, in execute
   TRACE neutron.api.v2.resource uow
   TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line 
59, in save_obj
   TRACE neutron.api.v2.resource mapper, table, update)
   TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line 
516, in _emit_update_statements
   TRACE neutron.api.v2.resource execute(statement, params)
   TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 727, 
in execute
   TRACE neutron.api.v2.resource return meth(self, multiparams, params)
   TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/sql/elements.py", li

[Yahoo-eng-team] [Bug 1355360] Re: Cisco VPNaaS agent doesn't resync with config DB on restart

[Launchpad Bug Tracker]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
   Status: Incomplete => Expired

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

Title:
  Cisco VPNaaS agent doesn't resync with config DB on restart

Status in neutron:
  Expired

Bug description:
  When Cisco VPNaaS agent restarts - either due to software-error or
  operator action - the agent doesn't reconcile with the configuration
  changes that happened while it was down with the CSR Virtual-Router
  configs. This could lead to cases where,

  a) any VPN config (ipsec-connection, et. al) that gets deleted in DB but 
doesn't gets deleted in the CSR VM
  b) any VPN config that gets updated in DB will cause the agent to reapply the 
configs as 'new' but it already exists in CSR VM.  While many configurations in 
CSR software are idempotent the RESTapi used to re-apply will fail with 
'resource already exist' status.  This will cause the Cisco VPN agent to report 
a failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1355360/+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 1498529] Re: VPNaaS: VPN connection shown "pending create" status after it created successfully

[Launchpad Bug Tracker]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
   Status: Incomplete => Expired

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

Title:
  VPNaaS: VPN connection shown "pending create" status after it created
  successfully

Status in neutron:
  Expired

Bug description:
  It's a display issue.
  After create VPN connection on openstack dashboard, the vpn connection is 
shown as "pending create". No matter create done or not.

  walk around: manually refresh openstack dashboard webpage.

  Juno version

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1498529/+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 1498704] Re: Tenant junk entries found in the controller Even after deletion

[Launchpad Bug Tracker]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
   Status: Incomplete => Expired

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

Title:
  Tenant junk entries found in the controller Even after deletion

Status in neutron:
  Expired

Bug description:
  Steps to Reproduce:-

  1) Create a few tenants(may be 4 to 5)
  2) Create Networks,subnets, routers and connect them
  3) Create vpnaas(site-to-site connection) in between two tenants
  4) Boot up vms and docker containers behind the vpnaas
  5) Send PING traffic between the docker containers across tenants
  6) After the test, delete all the namespaces, networks tenants etc
  7) Check in the Openstack dashboard and cli, the networks related tio 
different tenants are
  still listed as "Active" with the tenant names which are ALREADY DELETED.

  This issue is found in Juno release:
  root@controller:~# nova-manage version
  2014.2.3
  root@controller:~#

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1498704/+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 1532688] Re: Testing volume encryption fails

[Nguyen Truong Son]

** Also affects: nova (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: nova (Ubuntu)

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

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

Title:
  Testing volume encryption fails

Status in OpenStack Compute (nova):
  New
Status in openstack-manuals:
  New

Bug description:
  Hi

  I deploy openstack liberty with nfs cinder and barbican key manager.
  When attaching encrypted volume to instance, in compute host run the
  command:

  sudo nova-rootwrap /etc/nova/rootwrap.conf cryptsetup --batch-mode
  luksFormat --key-file=- --cipher aes-xts-plain64 --key-size 512
  /home/openstack/deployment/lib/nova/mnt/014350d8bf61a4224293d8dd521b6438
  /volume-ac170625-e126-4f01-b123-55f864125821

  After that, it run the command:

  sudo nova-rootwrap /etc/nova/rootwrap.conf cryptsetup luksOpen --key-
  file=-
  /home/openstack/deployment/lib/nova/mnt/014350d8bf61a4224293d8dd521b6438
  /volume-ac170625-e126-4f01-b123-55f864125821 volume-
  ac170625-e126-4f01-b123-55f864125821

  The luksOpen does things: original cinder volume file is deleted, and it is a 
link pointed to the encrypted device.
  See: https://bugs.launchpad.net/nova/+bug/1511255

  compute host is where cryptsetup is run, so it can read data from
  volume.

  When run command to test: strings
  /home/openstack/deployment/lib/nova/mnt/014350d8bf61a4224293d8dd521b6438
  /volume-ac170625-e126-4f01-b123-55f864125821 | grep "Hello"

  Result is:

  Hello, world (unencrypted /dev/vdb)
  Hello, world (encrypted /dev/vdc)

  ---
  Built: 2016-01-10T11:13:36 00:00
  git SHA: 2e180b474baadea9df8d9ae5f73a0cf8e150a417
  URL: 
http://docs.openstack.org/liberty/config-reference/content/section_testing_encryption.html
  source File: 
file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/config-reference/block-storage/section_volume-encryption.xml
  xml:id: section_testing_encryption

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1532688/+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 1533139] Re: there is useless 'u' in the wrong info when execute a wrong nova command

[Mark]

Thank you for the suggestion, I updated the same.

** Project changed: nova => python-novaclient

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

Title:
  there is useless 'u' in the wrong info when execute a wrong nova
  command

Status in python-novaclient:
  Incomplete

Bug description:
  [Summary]
  there is useless 'u' in the wrong info when execute a wrong nova command

  [Topo]
  devstack all-in-one node

  [Description and expect result]
  no useless 'u' in the wrong info when execute a wrong nova command

  [Reproduceable or not]
  reproduceable

  [Recreate Steps]
  1) there is useless 'u' in the wrong info when execute a wrong nova command:

  [user@controller Desktop]$ nova dsjf
  usage: nova [--version] [--debug] [--os-cache] [--timings]
  [--os-auth-token OS_AUTH_TOKEN]
  [--os-tenant-name ]
  [--os-tenant-id ] [--os-region-name ]
  [--os-auth-system ] [--service-type ]
  [--service-name ]
  [--volume-service-name ]
  [--os-endpoint-type ]
  [--os-compute-api-version ]
  [--bypass-url ] [--insecure]
  [--os-cacert ] [--os-cert ]
  [--os-key ] [--timeout ] [--os-auth-url OS_AUTH_URL]
  [--os-domain-id OS_DOMAIN_ID] [--os-domain-name OS_DOMAIN_NAME]
  [--os-project-id OS_PROJECT_ID]
  [--os-project-name OS_PROJECT_NAME]
  [--os-project-domain-id OS_PROJECT_DOMAIN_ID]
  [--os-project-domain-name OS_PROJECT_DOMAIN_NAME]
  [--os-trust-id OS_TRUST_ID] [--os-user-id OS_USER_ID]
  [--os-user-name OS_USERNAME]
  [--os-user-domain-id OS_USER_DOMAIN_ID]
  [--os-user-domain-name OS_USER_DOMAIN_NAME]
  [--os-password OS_PASSWORD]
   ...
  error: argument : invalid choice: u'dsjf'
  Try 'nova help ' for more information.

  2)below is a correct example for reference:
  root@45-59:/opt/stack/devstack# keystone wrongcmd
  usage: keystone [--version] [--debug] [--os-username ]
  [--os-password ]
  [--os-tenant-name ]
  [--os-tenant-id ] [--os-auth-url ]
  [--os-region-name ]
  [--os-identity-api-version ]
  [--os-token ]
  [--os-endpoint ] [--os-cache]
  [--force-new-token] [--stale-duration ] [--insecure]
  [--os-cacert ] [--os-cert ]
  [--os-key ] [--timeout ]
   ...
  keystone: error: argument : invalid choice: 'wrongcmd'

  [Configration]
  reproduceable bug, no need

  [logs]
  reproduceable bug, no need

  [Root cause anlyze or debug inf]
  reproduceable bug

  [Attachment]
  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-novaclient/+bug/1533139/+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 1533473] [NEW] missing mm-ctl rootwrap entry for compute.filters

[YAMAMOTO Takashi]

Public bug reported:

mm-ctl is used to plug VIF_TYPE_MIDONET vifs.
it needs to be in compute.filters.

** Affects: nova
 Importance: Undecided
 Status: New

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

Title:
  missing mm-ctl rootwrap entry for compute.filters

Status in OpenStack Compute (nova):
  New

Bug description:
  mm-ctl is used to plug VIF_TYPE_MIDONET vifs.
  it needs to be in compute.filters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1533473/+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 1508188] Re: Remove deprecated options

[Armando Migliaccio]

Need new owner to finish off the external_network_bridge option removal.

** Summary changed:

- Remove deprecated use_namespaces option
+ Remove deprecated options

** Description changed:

- dhcp/l3 agent use_namespaces option has been deprecated in Liberty[1].
+ dhcp/l3 agent use_namespaces and external_network_bridge options has
+ been deprecated in Liberty[1,2].
  
  Now kernels property support namespaces, removing this option allow to
  simplify agent code and remove an option (use_namespaces == False) not
  functionally tested.
  
  [1] https://bugs.launchpad.net/neutron/+bug/1435382
+ [2] https://review.openstack.org/#/c/219928/

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

** Changed in: neutron
 Assignee: Cedric Brandily (cbrandily) => (unassigned)

** Summary changed:

- Remove deprecated options
+ Remove l3 deprecated options

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

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

Title:
  Remove l3 deprecated options

Status in neutron:
  Incomplete

Bug description:
  dhcp/l3 agent use_namespaces and external_network_bridge options has
  been deprecated in Liberty[1,2].

  Now kernels property support namespaces, removing this option allow to
  simplify agent code and remove an option (use_namespaces == False) not
  functionally tested.

  [1] https://bugs.launchpad.net/neutron/+bug/1435382
  [2] https://review.openstack.org/#/c/219928/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1508188/+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 1533460] [NEW] DBReferenceError rasied during race between HA router deleting and L3 agent sync router info

[LIU Yulong]

Public bug reported:

If auto_scheduler the router, during race between HA router creating and 
deleting, the neutron server may treat the HA router as 'no scheduled', then it 
will create a new HA port binding with the router(id) which is deleted 
concurrently, and
then foreign key constraint error(Integrity Error) raised.

Exception:
DBReferenceError: (IntegrityError) (1452, 'Cannot add or update a child row: a 
foreign key constraint fails (`neutron`.`ha_router_agent_port_bindings`, 
CONSTRAINT `ha_router_agent_port_bindings_ibfk_2` FOREIGN KEY (`router_id`) 
REFERENCES `routers` (`id`) ON DELETE CASCADE)') 'INSERT INTO 
ha_router_agent_port_bindings (port_id, router_id, l3_agent_id, state) VALUES 
(%s, %s, %s, %s)' ('xxx', 'xxx', None, 'standby')

For more information:
https://bugs.launchpad.net/neutron/+bug/1523780/comments/7

** Affects: neutron
 Importance: Undecided
 Status: New

** Summary changed:

- DBReferenceError rasied during race between HA router creating and deleting
+ DBReferenceError rasied during race between HA router deleting and L3 agent 
sync router info

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

Title:
  DBReferenceError rasied during race between HA router deleting and L3
  agent sync router info

Status in neutron:
  New

Bug description:
  If auto_scheduler the router, during race between HA router creating and 
deleting, the neutron server may treat the HA router as 'no scheduled', then it 
will create a new HA port binding with the router(id) which is deleted 
concurrently, and
  then foreign key constraint error(Integrity Error) raised.

  Exception:
  DBReferenceError: (IntegrityError) (1452, 'Cannot add or update a child row: 
a foreign key constraint fails (`neutron`.`ha_router_agent_port_bindings`, 
CONSTRAINT `ha_router_agent_port_bindings_ibfk_2` FOREIGN KEY (`router_id`) 
REFERENCES `routers` (`id`) ON DELETE CASCADE)') 'INSERT INTO 
ha_router_agent_port_bindings (port_id, router_id, l3_agent_id, state) VALUES 
(%s, %s, %s, %s)' ('xxx', 'xxx', None, 'standby')

  For more information:
  https://bugs.launchpad.net/neutron/+bug/1523780/comments/7

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1533460/+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 1533457] [NEW] Neutron server unable to sync HA info after race between HA router creating and deleting

[LIU Yulong]

Public bug reported:

Neutron server will not be able to sync ha router data after race
happened between get_ha_router_port_bindings and HA router deleting API
call.

Exception:
TypeError: 'NoneType' object is unsubscriptable (function 
get_ha_router_port_bindings and _process_sync_ha_data)

** Affects: neutron
 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/1533457

Title:
  Neutron server unable to sync HA info after race between HA router
  creating and deleting

Status in neutron:
  New

Bug description:
  Neutron server will not be able to sync ha router data after race
  happened between get_ha_router_port_bindings and HA router deleting
  API call.

  Exception:
  TypeError: 'NoneType' object is unsubscriptable (function 
get_ha_router_port_bindings and _process_sync_ha_data)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1533457/+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 1492683] Re: neutron lbaas should add the new appended timestamp field

[Armando Migliaccio]

Tracking this with a separate bug seems overkill.

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

** Changed in: neutron
 Assignee: zhaobo (zhaobo6) => (unassigned)

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

Title:
  neutron lbaas should add the new appended timestamp field

Status in neutron:
  Invalid

Bug description:
  According to bp:
  https://review.openstack.org/#/c/210955/

  this bp will add timestamp fields(such as created_at and updated_at)
  to neutron core resources.

  But when neutron lbaas use these resources with new fields will hit
  issues, so it should to add the new fields to lbaas's resources which
  is related with neutron core resources.

  So should add the new appended attributes to
  neutron_lbaas/services/loadbalancer/data_models.py which import
  models_v2 from neutron.db .

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1492683/+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 1533455] [NEW] Stale processes lives after a fanout deleting HA router RPC between L3 agents

[LIU Yulong]

Public bug reported:

Stale processes lives after a fanout deleting HA router RPC between L3
agents:

The race happened between l3 agents after a fanout deleting HA router RPC. Race 
Scenario:
1. HA router X was schedulered to L3 agent A and L3 agent B

2. X in L3 agent A is the master state

3. a delete X RPC fanout

4. agent A delete all X HA attributes and processes including keepalived

5. （race） agent B was not ready to process the deleting RPC, 
assume there are a lot of deleting RPC is in the router update 
queue, or anything cause the agent B delay processing the RPC.

6. (race) X in agent B is backup state, now it can not get the VRRP
advertisement from X in agent A because of the 4, so X set it's state to
master

8. (race) enqueue_state_change for X in agent B

9. (race) agent B could process the deleting RPC

10. (race) X is still in agent B router_info, so spawn the metadata-
proxy

11. (race) agent B do deleting process for HA router X gateway, floating
IP etc.

12. (race) agent B remove X from router info

13. 13. metadata-proxy for router X in agent B lives.

If you have tried to use rally to run create_and_delete_routers, you
will find the l3 agent side will have some stale metadata-proxy
processes after the rally test.

The only way to decide whether to spawn the metedata-proxy is to try get
router in agent router_info dict. But enqueue_state_change and
processing router deleting can be run concurrently.

** Affects: neutron
 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/1533455

Title:
  Stale processes lives after a fanout deleting HA router RPC between L3
  agents

Status in neutron:
  New

Bug description:
  Stale processes lives after a fanout deleting HA router RPC between L3
  agents:

  The race happened between l3 agents after a fanout deleting HA router RPC. 
Race Scenario:
  1. HA router X was schedulered to L3 agent A and L3 agent B

  2. X in L3 agent A is the master state

  3. a delete X RPC fanout

  4. agent A delete all X HA attributes and processes including
  keepalived

  5. （race） agent B was not ready to process the deleting RPC, 
  assume there are a lot of deleting RPC is in the router update 
  queue, or anything cause the agent B delay processing the RPC.

  6. (race) X in agent B is backup state, now it can not get the VRRP
  advertisement from X in agent A because of the 4, so X set it's state
  to master

  8. (race) enqueue_state_change for X in agent B

  9. (race) agent B could process the deleting RPC

  10. (race) X is still in agent B router_info, so spawn the metadata-
  proxy

  11. (race) agent B do deleting process for HA router X gateway,
  floating IP etc.

  12. (race) agent B remove X from router info

  13. 13. metadata-proxy for router X in agent B lives.

  If you have tried to use rally to run create_and_delete_routers, you
  will find the l3 agent side will have some stale metadata-proxy
  processes after the rally test.

  The only way to decide whether to spawn the metedata-proxy is to try
  get router in agent router_info dict. But enqueue_state_change and
  processing router deleting can be run concurrently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1533455/+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 1498656] Re: router's status is not in DOWN when setting its admin-state-up as false

[Armando Migliaccio]

For the reasons stated on the abandoned patch.

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

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

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

Title:
  router's status is not in DOWN when setting its admin-state-up as
  false

Status in neutron:
  Won't Fix

Bug description:
  when updating the status of router's admin-state-up as false, its
  status is not in DOWN state. However, its namespace cannot be seen
  under 'sudo ip netns', but the status of that router is misleading.

  steps to reproduce:

  devstack@ubuntu:/opt/stack/neutron-vpnaas$ neutron router-show routerB
  
+---++
  | Field | Value   


   |
  
+---++
  | admin_state_up| False   


   |
  | external_gateway_info | {"network_id": 
"d8996aff-7a44-452d-8e94-705d4983f3e0", "enable_snat": true, 
"external_fixed_ips": [{"subnet_id": "9d39b49a-539d-493e-89cc-8efd7fc6e640", 
"ip_address": "172.24.4.4"}, {"subnet_id": 
"c966139b-8fcb-4c5f-b6dc-c1e43545dabc", "ip_address": "2001:db8::4"}]} |
  | id| e27f3a24-c8c4-4db1-ac0f-e35d56ebdeff


   |
  | name  | routerB 


   |
  | routes| 


   |
  | status| ACTIVE  


   |
  | tenant_id | ac1ff23dbb2e41babc3a1d6f69c0de9c


   |
  
+---++
  devstack@ubuntu:/opt/stack/neutron-vpnaas$
  devstack@ubuntu:/opt/stack/neutron-vpnaas$
  devstack@ubuntu:/opt/stack/neutron-vpnaas$
  devstack@ubuntu:/opt/stack/neutron-vpnaas$
  devstack@ubuntu:/opt/stack/neutron-vpnaas$
  devstack@ubuntu:/opt/stack/neutron-vpnaas$
  devstack@ubuntu:/opt/stack/neutron-vpnaas$
  devstack@ubuntu:/opt/stack/neutron-vpnaas$
  devstack@ubuntu:/opt/stack/neutron-vpnaas$ neutron router-show routerA
  
+---++
  | Field | Value   

   

[Yahoo-eng-team] [Bug 1533454] [NEW] L3 agent unable to update HA router state race after between HA router creating and deleting

[LIU Yulong]

Public bug reported:

When neutron server deleted all the resources of a HA router, L3 agent can not 
aware that, so race happened in some procedure like this:
1. neutron server delete all res of a HA router
2. RPC to l3 agent 1 in which the HA router was master state
3. In l3 agent 2 'backup' router set itself to masert and notify server a HA 
router state change notify.
4. DB error rasied in updating HA router states

** Affects: neutron
 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/1533454

Title:
  L3 agent unable to update HA router state race after between HA router
  creating and deleting

Status in neutron:
  New

Bug description:
  When neutron server deleted all the resources of a HA router, L3 agent can 
not aware that, so race happened in some procedure like this:
  1. neutron server delete all res of a HA router
  2. RPC to l3 agent 1 in which the HA router was master state
  3. In l3 agent 2 'backup' router set itself to masert and notify server a HA 
router state change notify.
  4. DB error rasied in updating HA router states

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1533454/+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 1312499] Re: add alert-error in local_settings.py not work

[OpenStack Infra]

Reviewed:  https://review.openstack.org/266406
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=1b8783b47ab63838acfbfaada93c4bd6402ee8c5
Submitter: Jenkins
Branch:master

commit 1b8783b47ab63838acfbfaada93c4bd6402ee8c5
Author: Rob Cresswell 
Date:   Tue Jan 12 14:40:47 2016 +

Fix doc incorrectly specifying alert-error

The settings doc specifies 'alert-error', when horizon uses
'alert-danger'. This causes unexpected behaviour when altering
HORIZON_CONFIG, such as alerts that don't fade (see bug report)

Change-Id: I8e5f3e253db980700f6064264e985ea8cde759d4
Closes-Bug: 1312499


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

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

Title:
  add alert-error in local_settings.py not work

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  add alert-error in HORIZON_CONFIG in local_settings.py., but it does
  not work, the error message is still exist until refresh the page.

  'auto_fade_alerts': {
  'delay': 3000,
  'fade_duration': 1500,
  'types': ['alert-success', 'alert-info', 'alert-error']
  },

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1312499/+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 1531334] Re: [Launch Instance] New items are visible under both allocated and available in transfer tables

[OpenStack Infra]

Reviewed:  https://review.openstack.org/252205
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=52fc193d0cbf8d9208b1151b6a302001a44cb582
Submitter: Jenkins
Branch:master

commit 52fc193d0cbf8d9208b1151b6a302001a44cb582
Author: Rajat Vig 
Date:   Tue Dec 1 22:18:56 2015 -0800

Transfer table should update allocatedIds on allocated change

Transfer table does a one time allocation
for allocatedIds and does not watch changes to
allocated. As a result, when the allocated
list is fetched at a later point, the allocatedIds
are not updated resulting in a broken view.

Partially-Implements: blueprint ng-flavors
Closes-Bug: #1531334

Change-Id: I807c682b69081f90fc3d74675e8ca149bb855521


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

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

Title:
  [Launch Instance] New items are visible under both allocated and
  available in transfer tables

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Description:
  The transfer table is a component that is preloaded with data to identify 
what's available and what's allocated. This results in two disjoint sets. The 
bug appears when we programatically try to create and allocate an item to an 
already preloaded transfer table. Although the table adds the new item to the 
allocated set, it adds it to the available set as well.

  Steps to reproduce:
  * Navigate to Project-->Compute-->Instances
  * Click on the angular Launch Instance button to open up the Launch Instance 
Modal
  * Go to key pair section
  * Make sure there are no key pairs allocated in the transfer table.
  * Create a key pair by clicking on the create key pair button and completing 
the create key pair flow.

  When you return back to the transfer table that lists the key pairs,
  you can see that the newly created key pair is visible under both the
  available section as well as the allocated.

  Attached Screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1531334/+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 1463891] Re: Setting admin_state down on port produces no logs

[OpenStack Infra]

Reviewed:  https://review.openstack.org/266383
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=7ca04daa71910b578303845a363883fa036358f7
Submitter: Jenkins
Branch:master

commit 7ca04daa71910b578303845a363883fa036358f7
Author: Hynek Mlnarik 
Date:   Tue Jan 12 09:10:25 2016 +0100

Log INFO message when setting admin state up flag to False for OVS port

Disabling admin state can cause confusion in OVS agent logs as to why
VLAN 4095 is set to a particular port. This commit adds an extra INFO
log message when admin state is disabled. There is no log emitted
upon enabling admin state as there is already a detailed log entry
logged in treat_devices_added_or_updated() function.

Change-Id: I1301db8fea75af211f66a1914d1f0b706a6d5b36
Closes-Bug: 1463891


** Changed in: neutron
   Status: In Progress => 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/1463891

Title:
  Setting admin_state down on port  produces no logs

Status in neutron:
  Fix Released

Bug description:
  Tried to check how admin_state down affects HA ports.
  Noticed that management data between them stoped and cause them to become 
master. Although traffic to connected floating IP remain working.
  Problem is: no log on OVS agent idicated why it's processing a port update or 
why it's setting it's VLAN tag to 4095.
  (06:39:44 PM) amuller: there should be an INFO level log saying something 
like: "Setting port admin_state to {True/False}"(06:39:56 PM) amuller: with the 
port ID of course

  Current log:
  2015-06-08 10:25:25.782 1055 INFO 
neutron.plugins.openvswitch.agent.ovs_neutron_agent 
[req-b5a70070-2c49-47f2-9c77-49ba88851f4b ] Port 'ha-8e0f96c5-78' has lost its 
vlan tag '1'!
  2015-06-08 10:25:25.783 1055 INFO neutron.agent.securitygroups_rpc 
[req-b5a70070-2c49-47f2-9c77-49ba88851f4b ] Refresh firewall rules
  2015-06-08 10:25:26.784 1055 INFO 
neutron.plugins.openvswitch.agent.ovs_neutron_agent 
[req-b5a70070-2c49-47f2-9c77-49ba88851f4b ] Port 
8e0f96c5-7891-46a4-8420-778454949bd0 updated. Details: {u'profile': {}, 
u'allowed_address_pairs': [], u'admin_state_up': False, u'network_id': 
u'6a5116a2-39f7-45bc-a432-3d624765d602', u'segmentation_id': 10, 
u'device_owner': u'network:router_ha_interface', u'physical_network': None, 
u'mac_address': u'fa:16:3e:02:cb:47', u'device': 
u'8e0f96c5-7891-46a4-8420-778454949bd0', u'port_security_enabled': True, 
u'port_id': u'8e0f96c5-7891-46a4-8420-778454949bd0', u'fixed_ips': 
[{u'subnet_id': u'f81913ba-328f-4374-96f2-1a7fd44d7fb1', u'ip_address': 
u'169.254.192.3'}], u'network_type': u'vxlan'}
  2015-06-08 10:25:26.940 1055 INFO 
neutron.plugins.openvswitch.agent.ovs_neutron_agent 
[req-b5a70070-2c49-47f2-9c77-49ba88851f4b ] Configuration for device 
8e0f96c5-7891-46a4-8420-778454949bd0 completed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1463891/+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 1533443] [NEW] Cannot update HA router HA ha_port states after race between HA router creating and deleting

[LIU Yulong]

Public bug reported:

ml2 plugin unable to update HA port status. This happened between L2
agent and neutron server side ml2 plugin. When l2 agent try to get port
details, ml2 plugin will try to get/update a HA port, but the HA port
was deleted by a router delete api, then the exception raised.

DBError: UPDATE statement on table 'ports' expected to update 1 row(s);
0 were matched.

** Affects: neutron
 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/1533443

Title:
  Cannot update HA router HA ha_port states after race between HA router
  creating and deleting

Status in neutron:
  New

Bug description:
  ml2 plugin unable to update HA port status. This happened between L2
  agent and neutron server side ml2 plugin. When l2 agent try to get
  port details, ml2 plugin will try to get/update a HA port, but the HA
  port was deleted by a router delete api, then the exception raised.

  DBError: UPDATE statement on table 'ports' expected to update 1
  row(s); 0 were matched.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1533443/+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 1533440] [NEW] Race between deleting last HA router and a new HA router API call

[LIU Yulong]

Public bug reported:

During the delete of tenant last HA router, neutron will also delete the
HA network which can be racy if a new HA router API call is coming
concurrently.

** Affects: neutron
 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/1533440

Title:
  Race between deleting last HA router and a new HA router API call

Status in neutron:
  New

Bug description:
  During the delete of tenant last HA router, neutron will also delete
  the HA network which can be racy if a new HA router API call is coming
  concurrently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1533440/+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 1533441] [NEW] HA router can not be deleted after race between HA router creating and deleting

[LIU Yulong]

Public bug reported:

HA router can not be deleted after race between HA router creating and
deleting

Exception:
1. Unable to process HA router %s without HA port
2. AttributeError: 'NoneType' object has no attribute 'config'

** Affects: neutron
 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/1533441

Title:
  HA router can not be deleted after race between HA router creating and
  deleting

Status in neutron:
  New

Bug description:
  HA router can not be deleted after race between HA router creating and
  deleting

  Exception:
  1. Unable to process HA router %s without HA port
  2. AttributeError: 'NoneType' object has no attribute 'config'

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1533441/+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 1521160] Re: VMware LBaaSv1 method uses invalid context

[OpenStack Infra]

Reviewed:  https://review.openstack.org/251320
Committed: 
https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=f993da58e81d0fbace9af01fabaf2bf07f6153b4
Submitter: Jenkins
Branch:master

commit f993da58e81d0fbace9af01fabaf2bf07f6153b4
Author: Kobi Samoray 
Date:   Mon Nov 30 14:00:12 2015 +0200

VMware LBaaSv1 method uses invalid context

VMware LBaaSv1 driver supplies the Neutron plugin with a method, which 
allows
detection of Edge appliance use by the LBaaS driver.
The is_edge_in_use() method is using a context which is invalid: the driver
has no self.context property and shouldn't have one.
Instead, the context should pass as parameter.

Change-Id: I7f3b95b43f87b35d641f0c7535d648ee178eda41
Closes-Bug: #1521160


** Changed in: neutron
   Status: In Progress => 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/1521160

Title:
  VMware LBaaSv1 method uses invalid context

Status in neutron:
  Fix Released

Bug description:
  VMware LBaaSv1 driver supplies the Neutron plugin with a method, which allows 
detection of Edge appliance use by the LBaaS driver.
  The is_edge_in_use() method is using a context which is invalid: the driver 
has no self.context property and shouldn't have one.
  Instead, the context should pass as parameter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1521160/+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 1531363] Re: internal server error returned when set gateway of router with an octal ip address

[ibm-cloud-qa]

Hi Jas,
this bug is already fixed and merged,  but current issue still exist, so they 
are different issue.

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

Title:
  internal server error returned when set gateway of router with an
  octal ip address

Status in neutron:
  New

Bug description:
  [Summary]
  internal server error returned when set gateway of router with an octal ip 
address

  [Topo]
  devstack all-in-one node

  [Description and expect result]
  no error returned when set gateway of router with an octal ip address

  [Reproduceable or not]
  reproduceable 

  [Recreate Steps]
  1) create a router:
  root@45-59:/opt/stack/devstack# neutron router-create router100
  Created a new router:
  +-+--+
  | Field   | Value|
  +-+--+
  | admin_state_up  | True |
  | availability_zone_hints |  |
  | availability_zones  |  |
  | distributed | False|
  | external_gateway_info   |  |
  | ha  | False|
  | id  | ab35ac7b-dc5f-4ec4-b3a3-26f90ecd9fd7 |
  | name| router100|
  | routes  |  |
  | status  | ACTIVE   |
  | tenant_id   | 72a70635fa0c42a2bcba67edd760d516 |
  +-+--+

  2)internal server error returned when set gateway of router
   with an octal ip address:
  root@45-59:/opt/stack/devstack# neutron router-gateway-set --fixed-ip 
subnet_id=
  015bc64c-ab58-41a1-a296-b58198cffacc,ip_address=172.168.0.011 router100 
ext-net
  Request Failed: internal server error while processing your request.   
ISSUE
  root@45-59:/opt/stack/devstack# 

  Note: the ip address 172.168.0.011 may be interpreted as octal address since
   there is a leading "0" in the address

  3) if there is no leading "0" in the address, it's ok:
  root@45-59:/opt/stack/devstack# 
  root@45-59:/opt/stack/devstack# neutron router-gateway-set --fixed-ip 
  subnet_id=015bc64c-ab58-41a1-a296-b58198cffacc,ip_address=172.168.0.11 
router100 ext-net
  Set gateway for router router100
  root@45-59:/opt/stack/devstack# neutron router-show router100
  
+-+---
  

  | Field   | Value 


 |
  
+-+---
  

  | admin_state_up  | True  


 |
  | availability_zone_hints |   


 |
  | availability_zones  | nova  


 |
  | distributed | False 


 |
  | external_gateway_info   | {"network_id": 
"1fd330fa-e2f3-40a0-b6fc-5c1caa4981c8"
  , "enable_snat": true, "external_fixed_ips": [{"subnet_id": 
"015bc64c-ab58-41a1
  -a296-b58198cffacc", "ip_address": "172.168.0.11"}]} |
  | ha  | False 


 |
  | id  | ab35ac7b-dc5f-4ec4-b3a3-26f90ecd9fd7  


 |
  | name| router100   

[Yahoo-eng-team] [Bug 1484395] Re: Radware LBaaS v2 driver LB deletion fails when no members exist

[OpenStack Infra]

Reviewed:  https://review.openstack.org/212401
Committed: 
https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=bf2a948cbf46bc38951b922a2185740886f74a05
Submitter: Jenkins
Branch:master

commit bf2a948cbf46bc38951b922a2185740886f74a05
Author: Evgeny Fedoruk 
Date:   Thu Aug 13 01:08:22 2015 -0700

Fixing Radware LBaaS v2 driver LB deletion

It issue re-raised after fix https://bugs.launchpad.net/neutron/+bug/1479406
cancelled the previous fix accidentally

Fixing Radware LBaaS v2 driver failure when trying to
delete LB instance witohut any members defined for its pools

Change-Id: I921df55b0efe6a2144337b8c889978a800917191
Closes-Bug: 1484395


** Changed in: neutron
   Status: In Progress => 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/1484395

Title:
  Radware LBaaS v2 driver LB deletion fails when no members exist

Status in neutron:
  Fix Released

Bug description:
  This bug is a copy of https://bugs.launchpad.net/neutron/+bug/1467243
  It is re-raised after this fix https://bugs.launchpad.net/neutron/+bug/1479406
  cancelled the fix accidentally

  Radware defined as a LBaaS v2 provider.

  LB instance created with or without lister(s)/ pool(s)
  No members created for LB pool(s)

  LB is deleted.
  Radware driver tries to delete LB service on back-end system and fails 
because no LB is created on back-end system until at least one member is 
defined for the LB.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1484395/+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 1533290] Re: nova unit tests failing with os-win 0.1.0

[OpenStack Infra]

Reviewed:  https://review.openstack.org/266495
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=6248dd0ae5ed16a690dfb34909e82f1ee49b4b3e
Submitter: Jenkins
Branch:master

commit 6248dd0ae5ed16a690dfb34909e82f1ee49b4b3e
Author: Claudiu Belu 
Date:   Tue Jan 12 09:19:14 2016 -0800

Fixes Hyper-V unit tests for latest os_win release

os_win release 0.1.0 causes unit tests to fail, as the wmi
module does not exist. Mocking it will fix the issue.

Change-Id: Iad91cd280e04dbb58e1194350489b2044506
Closes-Bug: #1533290


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

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

Title:
  nova unit tests failing with os-win 0.1.0

Status in OpenStack Compute (nova):
  Fix Released
Status in os-win:
  Fix Released

Bug description:
  2016-01-12 16:30:52.921 | Captured traceback:
  2016-01-12 16:30:52.921 | ~~~
  2016-01-12 16:30:52.921 | Traceback (most recent call last):
  2016-01-12 16:30:52.921 |   File 
"nova/tests/unit/virt/hyperv/test_imagecache.py", line 59, in setUp
  2016-01-12 16:30:52.921 | self.imagecache = imagecache.ImageCache()
  2016-01-12 16:30:52.922 |   File "nova/virt/hyperv/imagecache.py", line 
39, in __init__
  2016-01-12 16:30:52.922 | self._pathutils = pathutils.PathUtils()
  2016-01-12 16:30:52.922 |   File 
"/home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/os_win/utils/pathutils.py",
 line 46, in __init__
  2016-01-12 16:30:52.922 | super(PathUtils, self).__init__()
  2016-01-12 16:30:52.922 |   File 
"/home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/os_win/utils/storage/smbutils.py",
 line 35, in __init__
  2016-01-12 16:30:52.922 | self._smb_conn = 
wmi.WMI(moniker=r"root\Microsoft\Windows\SMB")
  2016-01-12 16:30:52.922 | NameError: global name 'wmi' is not defined

  https://jenkins05.openstack.org/job/gate-nova-python27/15232/console

  os-win 0.1.0 was released today which is causing the regression:

  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22NameError%3A%20global%20name%20'wmi'%20is%20not%20defined%5C%22%20AND%20tags%3A%5C%22console%5C%22

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1533290/+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 1533429] [NEW] Add multi-node devstack support to VPNaaS

[OpenStack Infra]

Public bug reported:

https://review.openstack.org/257504
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.

commit e544a4f669950e44bf80a56bd9acf089483979d9
Author: Ryan Moats 
Date:   Mon Dec 14 11:28:00 2015 -0600

Add multi-node devstack support to VPNaaS

Modify devstack plugin to support multi-node confgurations
(i.e. where the network node is split from the controller node).

DocImpact: Migrate HowTo wiki page to additional devref text

Change-Id: Iac5756ffe75b2125faace54b74b296036905a9b0
Signed-off-by: Ryan Moats 

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: neutron-vpnaas

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

Title:
  Add multi-node devstack support to VPNaaS

Status in neutron:
  New

Bug description:
  https://review.openstack.org/257504
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.

  commit e544a4f669950e44bf80a56bd9acf089483979d9
  Author: Ryan Moats 
  Date:   Mon Dec 14 11:28:00 2015 -0600

  Add multi-node devstack support to VPNaaS
  
  Modify devstack plugin to support multi-node confgurations
  (i.e. where the network node is split from the controller node).
  
  DocImpact: Migrate HowTo wiki page to additional devref text
  
  Change-Id: Iac5756ffe75b2125faace54b74b296036905a9b0
  Signed-off-by: Ryan Moats 

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1533429/+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 1533089] Re: there is useless 'u' in the wrong info when execute a wrong neutron command

[Reedip]

This is NOT a neutron bug, its actually a NeutronClient bug.
@manjeet-s-bhatia:
I could see the issue in (1) with a single node devstack.
Besides, a similar issue is already logged for it affecting a different CLI.
https://bugs.launchpad.net/python-neutronclient/+bug/1531418

I think it would be great if  all the NeutronClient CLI can be verified
for Unicode issues in one bug, than reporting them separately.

** Project changed: neutron => python-neutronclient

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

Title:
  there is useless 'u' in the wrong info when execute a wrong neutron
  command

Status in python-neutronclient:
  New

Bug description:
  [Summary]
  there is useless 'u' in the wrong info when execute a wrong neutron command

  [Topo]
  devstack all-in-one node

  [Description and expect result]
  no useless 'u' in the wrong info when execute a wrong neutron command

  [Reproduceable or not]
  reproduceable 

  [Recreate Steps]
  1) there is useless 'u' in the wrong info when execute a wrong neutron 
command:
  root@45-59:/opt/stack/devstack# neutron wrongcmd
  Unknown command [u'wrongcmd']  >>>ISSUE
  root@45-59:/opt/stack/devstack# 

  
  2)below is a correct example for reference:
  root@45-59:/opt/stack/devstack# keystone wrongcmd
  usage: keystone [--version] [--debug] [--os-username ]
  [--os-password ]
  [--os-tenant-name ]
  [--os-tenant-id ] [--os-auth-url ]
  [--os-region-name ]
  [--os-identity-api-version ]
  [--os-token ]
  [--os-endpoint ] [--os-cache]
  [--force-new-token] [--stale-duration ] [--insecure]
  [--os-cacert ] [--os-cert ]
  [--os-key ] [--timeout ]
   ...
  keystone: error: argument : invalid choice: 'wrongcmd' 

  [Configration]
  reproduceable bug, no need

  [logs]
  reproduceable bug, no need

  [Root cause anlyze or debug inf]
  reproduceable bug

  [Attachment]
  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-neutronclient/+bug/1533089/+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 1533405] [NEW] Release networking-powervm 1.0.0

[Adam Reznechek]

Public bug reported:

We are requesting that networking-powervm release 1.0.0 be created. It
should contain everything up to the current tip of the stable/liberty
branch, commit 68e8db46ffbd06e680b63236f32a80185258 from Nov 18,
2015 (http://git.openstack.org/cgit/openstack/networking-
powervm/commit/?h=stable/liberty).

Creating this release should publish both a source package and a python
wheel to pypi.

** Affects: networking-powervm
 Importance: Undecided
 Status: New

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: release-subproject

** Also affects: neutron
   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/1533405

Title:
  Release networking-powervm 1.0.0

Status in networking-powervm:
  New
Status in neutron:
  New

Bug description:
  We are requesting that networking-powervm release 1.0.0 be created. It
  should contain everything up to the current tip of the stable/liberty
  branch, commit 68e8db46ffbd06e680b63236f32a80185258 from Nov 18,
  2015 (http://git.openstack.org/cgit/openstack/networking-
  powervm/commit/?h=stable/liberty).

  Creating this release should publish both a source package and a
  python wheel to pypi.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-powervm/+bug/1533405/+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 1490389] Re: cannot receive extra args for ostestr via tox

[OpenStack Infra]

Reviewed:  https://review.openstack.org/218726
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=240facf9e67aa5b205679f397107abfe059a869a
Submitter: Jenkins
Branch:master

commit 240facf9e67aa5b205679f397107abfe059a869a
Author: gong yong sheng 
Date:   Mon Aug 31 13:03:18 2015 +0800

Allow tox to pass more arguments to ostestr command

Co-Authored-By: Kevin Benton 
Change-Id: Ie9969e0a5254ab5dd33b287f6d3120362b73edd7
Closes-bug: #1490389


** Changed in: neutron
   Status: In Progress => 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/1490389

Title:
  cannot receive extra args for ostestr via tox

Status in neutron:
  Fix Released

Bug description:
  ostestr http://docs.openstack.org/developer/os-testr/ostestr.html has many 
more arguments to run test cases. but out tox.ini
  is limits the usage to just "--regex".

  Such as --serial to run cases in serally etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1490389/+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 1531640] Re: lbaas:Service authentication from Octavia driver

[OpenStack Infra]

Reviewed:  https://review.openstack.org/264382
Committed: 
https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=b3b8f4a3ade11ac401db51a8ae73a2c8883e7125
Submitter: Jenkins
Branch:master

commit b3b8f4a3ade11ac401db51a8ae73a2c8883e7125
Author: ptoohill1 
Date:   Wed Jan 6 16:17:24 2016 -0600

Pass service admin auth from the Octavia driver

Some implementations of Octavia may require authenticated access
to the service. For this, pass the service admin token in a header
along with the API request.

Change-Id: I038f79de5638f1992d9f89972bcb91de331448e3
Closes-Bug: #1531640


** Changed in: neutron
   Status: In Progress => 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/1531640

Title:
  lbaas:Service authentication from Octavia driver

Status in neutron:
  Fix Released

Bug description:
  Some implementations of Octavia may require authenticated access to
  the API. For this, pass the service admin auth token as a header along
  with the request. For those implementations that do not require it, it
  can simply be ignored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1531640/+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 1533380] [NEW] Creating multiple instances with a single request when using cells creates wrong instance names

[Belmiro Moreira]

Public bug reported:

When creating multiple instances with a single request the instance name has 
the format defined in the "multi_instance_display_name_template" option.
By default: multi_instance_display_name_template=%(name)s-%(count)d
When booting two instances (num-instances=2) with the name=test is expected to 
have the following instance names:
test-1
test-2

However, if using cells (only considering 2 levels) we have the following names:
test-1-1
test-1-2

Increasing the number of cell levels adds more hops in the instance name.
Changing the "multi_instance_display_name_template" to uuids has the same 
problem.
For example: (consider  a random uuid)
test--
test--

** Affects: nova
 Importance: Undecided
 Assignee: Belmiro Moreira (moreira-belmiro-email-lists)
 Status: New


** Tags: cells

** Changed in: nova
 Assignee: (unassigned) => Belmiro Moreira (moreira-belmiro-email-lists)

** Description changed:

- When creating multiple instances with a single request the instance name has 
the
- format defined in the "multi_instance_display_name_template" option.
+ When creating multiple instances with a single request the instance name has 
the format defined in the "multi_instance_display_name_template" option.
  By default: multi_instance_display_name_template=%(name)s-%(count)d
- When booting two instances (num-instances=2) with the name=test is expected 
to have
- the following instance names:
+ When booting two instances (num-instances=2) with the name=test is expected 
to have the following instance names:
  test-1
  test-2
  
  However, if using cells (only considering 2 levels) we have the following 
names:
  test-1-1
  test-1-2
  
  Increasing the number of cell levels adds more hops in the instance name.
  Changing the "multi_instance_display_name_template" to uuids has the same 
problem.
  For example: (consider  a random uuid)
  test--
  test--

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

Title:
  Creating multiple instances with a single request when using cells
  creates wrong instance names

Status in OpenStack Compute (nova):
  New

Bug description:
  When creating multiple instances with a single request the instance name has 
the format defined in the "multi_instance_display_name_template" option.
  By default: multi_instance_display_name_template=%(name)s-%(count)d
  When booting two instances (num-instances=2) with the name=test is expected 
to have the following instance names:
  test-1
  test-2

  However, if using cells (only considering 2 levels) we have the following 
names:
  test-1-1
  test-1-2

  Increasing the number of cell levels adds more hops in the instance name.
  Changing the "multi_instance_display_name_template" to uuids has the same 
problem.
  For example: (consider  a random uuid)
  test--
  test--

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1533380/+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 1417603] Re: We should delete the row class for _detail_overview.html

[Diana Whitten]

The detail pages have been completely reworked.  This is no longer an
issue.

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

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

Title:
  We should delete the row class for _detail_overview.html

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  As the below screenshot show, the instance detail page show properly,
  but the image details page can't, because the `row` class in the image
  detail page, we should fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1417603/+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 1533366] [NEW] Stack template detail box's width is too large

[Lucas Palm]

Public bug reported:

On the "Template" tab of the Stack details page (Project -->
Orchestration --> Stacks --> Stack Details), the gray box that surrounds
the template text is just a bit too wide.  The edges extend right up to
the side of the enclosing  element, making it look bad.

** Affects: horizon
 Importance: Undecided
 Assignee: Lucas Palm (lapalm)
 Status: New

** Attachment added: "Screen Shot 2016-01-12 at 3.17.38 PM.png"
   
https://bugs.launchpad.net/bugs/1533366/+attachment/4548791/+files/Screen%20Shot%202016-01-12%20at%203.17.38%20PM.png

** Changed in: horizon
 Assignee: (unassigned) => Lucas Palm (lapalm)

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

Title:
  Stack template detail box's width is too large

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  On the "Template" tab of the Stack details page (Project -->
  Orchestration --> Stacks --> Stack Details), the gray box that
  surrounds the template text is just a bit too wide.  The edges extend
  right up to the side of the enclosing  element, making it look
  bad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1533366/+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 1533346] [NEW] federation create_mapping signature and V9 wrapper incorrect

[Henry Nash]

Public bug reported:

The original abstract signature for the create_mapping() driver method
was wrong in the federation manager in Liberty. This was then
inadvertently copied to the V9wrapper when we created the V9 driver in
Mitaka. This would cause V8 federation drivers to fail with Mitaka.  The
legacy testing did not cover all the CRUD tests, which is why this was
not discovered when the V9 driver was created.

** Affects: keystone
 Importance: High
 Assignee: Henry Nash (henry-nash)
 Status: In Progress

** Changed in: keystone
   Importance: Undecided => High

** Changed in: keystone
 Assignee: (unassigned) => Henry Nash (henry-nash)

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

Title:
  federation create_mapping signature and V9 wrapper incorrect

Status in OpenStack Identity (keystone):
  In Progress

Bug description:
  The original abstract signature for the create_mapping() driver method
  was wrong in the federation manager in Liberty. This was then
  inadvertently copied to the V9wrapper when we created the V9 driver in
  Mitaka. This would cause V8 federation drivers to fail with Mitaka.
  The legacy testing did not cover all the CRUD tests, which is why this
  was not discovered when the V9 driver was created.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1533346/+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 1533341] [NEW] Neutron MTU overhead computation assumes IPv4

[Dustin Lundquist]

Public bug reported:

Neutron's MTU computation assumes 50 bytes overhead for VXLAN. This is
correct for IPv4, but in the case of IPv6 the the overhead is 70 bytes.
Similar assumptions are made for GRE and Geneve tunnels.

Additionally 802.1q tags could increase overhead by 4.

See: http://keepingitclassless.net/2014/03/mtu-considerations-vxlan/

** Affects: neutron
 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/1533341

Title:
  Neutron MTU overhead computation assumes IPv4

Status in neutron:
  New

Bug description:
  Neutron's MTU computation assumes 50 bytes overhead for VXLAN. This is
  correct for IPv4, but in the case of IPv6 the the overhead is 70
  bytes. Similar assumptions are made for GRE and Geneve tunnels.

  Additionally 802.1q tags could increase overhead by 4.

  See: http://keepingitclassless.net/2014/03/mtu-considerations-vxlan/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1533341/+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 1499269] Re: cannot attach direct type port (sr-iov) to existing instance

[Moshe Levi]

** No longer affects: nova

** Project changed: neutron => nova

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

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

Title:
  cannot attach direct type port (sr-iov) to existing instance

Status in OpenStack Compute (nova):
  New

Bug description:
  Whenever I try to attach a direct port to an existing instance It
  fails:

  #neutron port-create Management --binding:vnic_type direct
  Created a new port:
  
+---+-+
  | Field | Value   
|
  
+---+-+
  | admin_state_up| True
|
  | allowed_address_pairs | 
|
  | binding:host_id   | 
|
  | binding:profile   | {}  
|
  | binding:vif_details   | {}  
|
  | binding:vif_type  | unbound 
|
  | binding:vnic_type | direct  
|
  | device_id | 
|
  | device_owner  | 
|
  | fixed_ips | {"subnet_id": 
"6c82ff4c-124e-469a-8444-1446cc5d979f", "ip_address": "10.92.29.123"} |
  | id| ce455654-4eb5-4b89-b868-b426381951c8
|
  | mac_address   | fa:16:3e:6b:15:e8   
|
  | name  | 
|
  | network_id| 5764ca50-1f30-4daa-8c86-a21fed9a679c
|
  | security_groups   | 5d2faf7b-2d32-49a8-978e-a91f57ece17d
|
  | status| DOWN
|
  | tenant_id | d5ecb0eea96f4996b565fd983a768b11
|
  
+---+-+

  # nova interface-attach --port-id ce455654-4eb5-4b89-b868-b426381951c8 
voicisc4srv1
  ERROR (ClientException): Failed to attach interface (HTTP 500) (Request-ID: 
req-11516bf4-7ab7-414c-a4ee-63e44aaf00a5)

  nova-compute.log:

  0a14aeb82013e5a1631de80 d5ecb0eea96f4996b565fd983a768b11 - - -] Exception 
during message handling: Failed to attach network adapter device to 
056d455a-314d-4853-839e-70229a56dfcd
  2015-09-24 10:41:35.434 43535 TRACE oslo_messaging.rpc.dispatcher Traceback 
(most recent call last):
  2015-09-24 10:41:35.434 43535 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 142, 
in _dispatch_and_reply
  2015-09-24 10:41:35.434 43535 TRACE oslo_messaging.rpc.dispatcher 
executor_callback))
  2015-09-24 10:41:35.434 43535 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 186, 
in _dispatch
  2015-09-24 10:41:35.434 43535 TRACE oslo_messaging.rpc.dispatcher 
executor_callback)
  2015-09-24 10:41:35.434 43535 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 130, 
in _do_dispatch
  2015-09-24 10:41:35.434 43535 TRACE oslo_messaging.rpc.dispatcher result 
= func(ctxt, **new_args)
  2015-09-24 10:41:35.434 43535 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6632, in 
attach_interface
  2015-09-24 10:41:35.434 43535 TRACE oslo_messaging.rpc.dispatcher 
port_id, requested_ip)
  2015-09-24 10:41:35.434 43535 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 443, in 
decorated_function
  2015-09-24 10:41:35.434 43535 TRACE oslo_messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
  2015-09-24 10:41:35.434 43535 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/excepti

[Yahoo-eng-team] [Bug 1525076] Re: delete vm, port mac is not be reset

[Moshe Levi]

you can workaround the issue by setting the macs of all the VF to 
00:00:00:00:00:01 before you start to use them, then libvirt will clean the VF.
The problem is with some driver that don't except 00:00:00:00:00:00

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

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

Title:
  delete vm, port mac is not be reset

Status in neutron:
  Invalid

Bug description:
  1 Create a vm with sriov port which use a  fix mac
  2 Delete vm.
  3 Use "ip link show" to see the sriov port's vf mac. we found it not change.

  We think that if we delete vm which use a fix mac ,the port's mac
  should be clear.

  def unplug_hw_veb(self, instance, vif):
  if vif['vnic_type'] == network_model.VNIC_TYPE_MACVTAP:
  # The ip utility doesn't accept the MAC 00:00:00:00:00:00.
  # Therefore, keep the MAC unchanged.  Later operations on
  # the same VF will not be affected by the existing MAC.
  linux_net.set_vf_interface_vlan(vif['profile']['pci_slot'],
  mac_addr=vif['address'])

  mac_addr=vif['address'] should be a random one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1525076/+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 1484085] Re: Changing Webroot not fully applied in LESS/CSS

[Diana Whitten]

the SCSS actually uses $static_url, which it now pulls directly from
local_settings.py / settings.py

Fix was here: https://review.openstack.org/#/c/206592/

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

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

Title:
  Changing Webroot not fully applied in LESS/CSS

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Changing the webroot in /etc/openstack-dashboard/local_settings seems
  to work mostly, expect for some font files.

  In File:
  
/usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/scss/_variables.scss
  Line 7:
  $webroot: "/dashboard" !default;

  This $webroot variable here is not automatically set to the setting in
  local_settings.

  Sidenotes: i used packstack to install OpenStack Kilo on Centos 7
  machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1484085/+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 1524643] Re: port 'binding:profile' can't be removed when VM is deleted

[Moshe Levi]

** Project changed: neutron => nova

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

Title:
  port 'binding:profile' can't be removed when VM is deleted

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  reproduce this problem:
  1. create a sriov port
  2. use this port to boot a VM
  3. delete this VM
  4. we can see port still exist, but the 'binding:profile' can't be removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1524643/+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 1533330] [NEW] Some protection test cases have incorrect domain id setup

[Lance Bragstad]

Public bug reported:

The IdentityTestv3CloudPolicySample test classes has it's own setup
method, similar to other test classes. The setup method for
IdentityTestv3CloudPolicySample loads in sample data that can be used
throughout the tests in the module.

However, the IdentityTestv3CloudPolicySample setup method creates a
domain in such a way that is incompatible with how domains are created
in real world deployments. Keystone doesn't allow admins to specify
domain_id on request, making it so keystone always issues uuid.hex
formatted id strings for domain ids. The only domain that is the
exception to this rule is the default domain id, which is specified in
keystone's configuration.

The IdentityTestv3CloudPolicySample tests and setup should be refactored
to not use 'admin_domain' and instead rely on actual domain ids created
by keystone [0].

[0]
https://github.com/openstack/keystone/blob/ae87c03813fa0a1bfcd9d690817c8d45ee76fcb1/keystone/tests/unit/test_v3_protection.py#L608-L609

** Affects: keystone
 Importance: Undecided
 Status: New


** Tags: low-hanging-fruit test-improvement

** Tags added: low-hanging-fruit test-improvement

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

Title:
  Some protection test cases have incorrect domain id setup

Status in OpenStack Identity (keystone):
  New

Bug description:
  The IdentityTestv3CloudPolicySample test classes has it's own setup
  method, similar to other test classes. The setup method for
  IdentityTestv3CloudPolicySample loads in sample data that can be used
  throughout the tests in the module.

  However, the IdentityTestv3CloudPolicySample setup method creates a
  domain in such a way that is incompatible with how domains are created
  in real world deployments. Keystone doesn't allow admins to specify
  domain_id on request, making it so keystone always issues uuid.hex
  formatted id strings for domain ids. The only domain that is the
  exception to this rule is the default domain id, which is specified in
  keystone's configuration.

  The IdentityTestv3CloudPolicySample tests and setup should be
  refactored to not use 'admin_domain' and instead rely on actual domain
  ids created by keystone [0].

  [0]
  
https://github.com/openstack/keystone/blob/ae87c03813fa0a1bfcd9d690817c8d45ee76fcb1/keystone/tests/unit/test_v3_protection.py#L608-L609

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/150/+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 1480789] Re: "Create Network" page has css error when in a new page

[Diana Whitten]

I am not able to recreate this bug.  Was this a specific browser?

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

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

Title:
  "Create Network" page has css error when in a new page

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Reproduce the bug:
  1, Right-click the "Create Network" button in the networks index page,  open 
a new page to "Create Network".
  2, Now you can see the css error, and i will provide a picture blow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1480789/+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 1532534] Re: [RFE] InfiniBand support

[Moshe Levi]

** Changed in: ironic-inspector
 Assignee: (unassigned) => Moshe Levi (moshele)

** Changed in: ironic-inspector
   Status: Confirmed => In Progress

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

** Changed in: nova
 Assignee: (unassigned) => Moshe Levi (moshele)

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

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

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

Title:
  [RFE] InfiniBand support

Status in Ironic:
  In Progress
Status in Ironic Inspector:
  In Progress
Status in OpenStack Compute (nova):
  In Progress

Bug description:
  today Ironic doesn't support InfiniBand interface
  this RFE adds support of  the following:
  1. Hardware inspection for InfiniBand - by increasing the address to 60 
characters
  2. PXE boot over InfiniBand interlace - by adding the GID (port address) as 
client-id to the neutron port

To manage notifications about this bug go to:
https://bugs.launchpad.net/ironic/+bug/1532534/+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 1417314] Re: IE9 cuts off CSS rules

[Diana Whitten]

we no longer support ie9/ie10

** Changed in: horizon
   Status: Confirmed => Invalid

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

Title:
  IE9 cuts off CSS rules

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  The generated css file has many css rules. When open the parsed css
  rules in IE9 and IE10, some css selectors can be found in IE10 but
  cannot be found in IE9.

  Steps to reproduce:

  Do the same thing on IE9 and IE10:
  1. Open Horizon.
  2. Open F12 developer tools.
  3. Switch to CSS tab.
  4. In the dropdown list, select [host]/static/dashboard/css/.css
  5. in the top-right corner of the developer tools, search for '.help-panel'

  It can be found in IE10, cannot be found in IE9

  UI effect:
  help-panel is not properly styled in IE9, styled properly in IE10, IE11, 
Firefox and Chrome.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1417314/+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 1527759] Re: Default domain no longer lets keystone tenant-list work

[Steve Martinelli]

patch for liberty: https://review.openstack.org/#/c/265023/

patch for kilo: https://review.openstack.org/#/c/265019/

** Also affects: keystone/liberty
   Importance: Undecided
   Status: New

** Also affects: keystone/kilo
   Importance: Undecided
   Status: New

** Tags added: liberty-backport-potential

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

** Changed in: keystone/kilo
   Importance: Undecided => Medium

** Changed in: keystone/liberty
   Importance: Undecided => Medium

** Changed in: keystone/kilo
   Status: New => In Progress

** Changed in: keystone/liberty
   Status: New => In Progress

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

Title:
  Default domain no longer lets keystone tenant-list work

Status in OpenStack Identity (keystone):
  Fix Released
Status in OpenStack Identity (keystone) kilo series:
  In Progress
Status in OpenStack Identity (keystone) liberty series:
  In Progress

Bug description:
  We recently upgraded from kilo.0 to kilo.2 in our dev environment and
  noticed that keystone tenant-list is always failing for the admin
  user.

  Our config is as follows default domain is tied to read-only ldap
  (AD), a heat domain is created to use for trusts to handle the created
  heatstack users/passwords. Under kilo.0 everything was happy. Under
  kilo0.2 we get the following error:

  keystone tenant-list
  The request you have made requires authentication. (HTTP 401) (Request-ID: 
req-d30289f0-778d-4577-8150-7ddd5438ad9c)

  The main error message is:
  2015-12-16 17:07:36.493 20386 WARNING keystone.common.wsgi [-] Authorization 
failed. Non-default domain is not supported (Disable debug mode to suppress 
these details.) (Disable debug mode to suppress these details.) from 
10.224.48.132

  Looking at the differences between kilo.0 and kilo.2  it seems like:
  
https://github.com/openstack/keystone/commit/9dfad21201251364c6d205e8e79813bfe78e6107
  is the most likely culprit for this regression. However, I have not
  yet been able to test if reverting that change fixes the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1527759/+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 1341740] Re: some less to scss updates in horizon.scss

[Diana Whitten]

Fixed in I63f933e57093bd7672992c1383c4f10f4f698891

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

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

Title:
  some less to scss updates in horizon.scss

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  
https://review.openstack.org/#/c/90371/20/openstack_dashboard/static/dashboard/scss/horizon.scss

  Gradients, box-shadows have not been converted to scss yet, so have
  been commented out.  We can use scss mixins to resolve these.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1341740/+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 1528235] Re: [RFE]Add weight to l3 agent

[Armando Migliaccio]

@Assaf: so you concur with me?

** Changed in: neutron
   Status: Triaged => Won't Fix

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

Title:
  [RFE]Add weight to l3 agent

Status in neutron:
  Won't Fix

Bug description:
  [Existing problem]
  Currently, neutron will treat all l3 agent as the same. The default 
LeastRoutersScheduler will chose l3 agent, based on the load of l3 agents. But 
the hosts of l3 agents may be different. Some hosts may have better CPU, larger 
memory and better network bandwidth. Admins/Operators may want the host with 
higher performance to take more load.

  [Proposal]
  Add a configuration to l3_agent.ini to represent the weight of l3 agent. 
Admins/Operators can set higher weight to the l3 agent with higher performance. 
The l3 agent with higher weight will have higher chance to be selected by the 
L3Scheduler.

  A simple algorithm of weight is to be linear correlation with performance of 
hosts. And Admins/Operators will need to estimate the performance of hosts. For 
example, performance of host A is 10 times than host B. Admins/Operators then 
set weight of l3 agent in host A to 10, and l3 agent in host B to 1. 
L3Scheduler will calculate load of l3 agents with such comparison:
  X/10 ~ Y/1(X=routers in l3 agent A; Y=routers in l3 agent B)

  [Benefits]
  Neutron can provide a better scheduling by leveraging the difference of 
performance of l3 agents' hosts

  [What is the enhancement?]
  Configuration file changes.
  Code change in the L3 scheduler.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1528235/+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 1533322] [NEW] "extra_resources" is hidden in ComputeNode

[xiaobin]

Public bug reported:

"extra_resources" is a text field defined in ComputeNode model:
https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/models.py#L165

But it's not defined in objects.compute_node.ComputeNode:
https://github.com/openstack/nova/blob/master/nova/objects/compute_node.py#L52

True that it's not used anywhere in projects, but it's critical for
some customized schedulers.

No clue shows this field is about to deprecate, can we expose this field
in objects.compute_node.ComputeNode?

** Affects: nova
 Importance: Undecided
 Status: New

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

Title:
  "extra_resources" is hidden in ComputeNode

Status in OpenStack Compute (nova):
  New

Bug description:
  "extra_resources" is a text field defined in ComputeNode model:
  
https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/models.py#L165

  But it's not defined in objects.compute_node.ComputeNode:
  https://github.com/openstack/nova/blob/master/nova/objects/compute_node.py#L52

  True that it's not used anywhere in projects, but it's critical for
  some customized schedulers.

  No clue shows this field is about to deprecate, can we expose this
  field in objects.compute_node.ComputeNode?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1533322/+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 1401132] Re: The logic in linux dhcp-agent disable for removing ports is broken

[Armando Migliaccio]

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

Title:
  The logic in linux dhcp-agent disable for removing ports is broken

Status in neutron:
  Fix Released

Bug description:
  
https://github.com/openstack/neutron/blob/master/neutron/agent/linux/dhcp.py#L215

  def disable(self, retain_port=False):
  """Disable DHCP for this network by killing the local process."""
  pid = self.pid

  if pid:
  if self.active:
  cmd = ['kill', '-9', pid]
  utils.execute(cmd, self.root_helper)
  else:
  LOG.debug('DHCP for %(net_id)s is stale, pid %(pid)d '
    'does not exist, performing cleanup',
    {'net_id': self.network.id, 'pid': pid})
  if not retain_port:
  self.device_manager.destroy(self.network,
  self.interface_name)
  else:
  LOG.debug('No DHCP started for %s', self.network.id)

  if there was no pid (for some reason the local process (dnsmasq) didn't 
  start, but the port was created, the port will be left there, and no 
  disable will remove the actual port.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1401132/+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 1508687] Re: lbaasv2- Only uppercase string for protocol are accepted while creating listener

[Armando Migliaccio]

** Also affects: python-neutronclient
   Importance: Undecided
   Status: New

** Changed in: python-neutronclient
   Status: New => Fix Released

** Changed in: neutron
   Status: Fix Committed => Won't Fix

** Changed in: python-neutronclient
 Assignee: (unassigned) => Manjeet Singh Bhatia (manjeet-s-bhatia)

** Changed in: python-neutronclient
   Importance: Undecided => Low

** Changed in: neutron
 Assignee: Manjeet Singh Bhatia (manjeet-s-bhatia) => (unassigned)

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

Title:
  lbaasv2- Only uppercase string for protocol are accepted while
  creating listener

Status in neutron:
  Won't Fix
Status in python-neutronclient:
  Fix Released

Bug description:
  while creating listener only upper case protocol value is accepted where as 
in neutron securitygroups both uppercase and lower
  case strings for protocol are accepted. 

  try

  neutron lbaas-listener-create --loadbalancer 
  --protocol http --protocol-port 80

  You will see exception 
  neutron lbaas-listener-create: error: argument --protocol: invalid choice: 
u'http' (choose from 'TCP', 'HTTP', 'HTTPS'│
  , 'TERMINATED_HTTPS')

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1508687/+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 1524913] Re: Potential gate problem for neutron-linuxbridge job in stable/liberty

[Armando Migliaccio]

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

Title:
  Potential gate problem for neutron-linuxbridge job in stable/liberty

Status in neutron:
  Fix Released

Bug description:
  The neutron-linuxbridge gate job repeatedly fails for the following
  patch to stable/liberty:

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

  Perhaps useful:

  http://logs.openstack.org/53/251753/3/check/gate-tempest-dsvm-neutron-
  linuxbridge/76832b3/logs/screen-q-l3.txt.gz#_2015-12-10_11_52_31_751

  http://logs.openstack.org/53/251753/3/gate/gate-tempest-dsvm-neutron-
  linuxbridge/3a4e5fc/logs/devstacklog.txt.gz#_2015-12-08_13_25_33_311

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1524913/+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 1405543] Re: quota bar chart and title doesn't display well in chrome and IE

[Diana Whitten]

** Attachment added: "Screenshot 2016-01-12 11.43.27.png"
   
https://bugs.launchpad.net/horizon/+bug/1405543/+attachment/4548695/+files/Screenshot%202016-01-12%2011.43.27.png

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

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

Title:
  quota bar chart and title doesn't display well in chrome and IE

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  quota bar chart and title doesn't display well in chrome and IE

  Envrionment:

  Horizon:
  Upstream source code

  Chrome:
  Version: 36.0.1985.125 m

  IE:
  Version: 10.0.9200.16921
  update:10.0.17

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1405543/+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 1486136] Re: Neutron create_flavor_service_profile returns list not dict

[Armando Migliaccio]

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

Title:
  Neutron create_flavor_service_profile returns list not dict

Status in neutron:
  Fix Released

Bug description:
  The Neutron flavor framework routine create_flavor_service_profile
  incorrectly returns a list instead of the expected dictionary.

  For example, this causes an internal server error in 
_exclude_attributes_by_policy when using curl to create a Neutron flavor 
service profile:
  File "/opt/stack/neutron/neutron/api/v2/base.py", line 143, in 
_exclude_attributes_by_policy
  for attr_name in data.keys():
  AttributeError: 'list' object has no attribute 'keys'

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1486136/+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 1522761] Re: Kilo: can't extend supported_extension_aliases from the remote repo in PLUMgrid plugin

[Armando Migliaccio]

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

Title:
  Kilo: can't extend supported_extension_aliases from the remote repo in
  PLUMgrid plugin

Status in neutron:
  Fix Released

Bug description:
  Kilo: can't extend supported_extension_aliases from the remote repo in
  PLUMgrid plugin

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1522761/+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 1527420] Re: Neutron does not log UserID or TenantID

[Armando Migliaccio]

This hasn't merged yet.

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

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

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

Title:
  Neutron does not log UserID or TenantID

Status in neutron:
  In Progress

Bug description:
  Neutron shows the same issues as this devstack bug:
  https://bugs.launchpad.net/devstack/+bug/1399788

  We are using user_identity, which is showing 'none' in the logs.

  from log.py/options.py:

  log_opts = [
  cfg.StrOpt('logging_context_format_string',
     default='%(asctime)s.%(msecs)03d %(process)d %(levelname)s '
     '%(name)s [%(request_id)s %(user_identity)s] '
     '%(instance)s%(message)s',

  Log Snippets:

   | success | rc=0 >>
  2015-12-15 13:26:48.298 43398 INFO neutron.wsgi 
[req-f408d470-2b16-49e4-8f93-3b4c3ef284e7 None] 172.29.236.10 - - [15/Dec/2015 
13:26:48] "DELETE /v2.0/routers/27354e70-87d7-4266-a5f6-0f09827f6b42.json 
HTTP/1.1" 204 149 0.198291

   | success | rc=0 >>
  2015-12-15 13:26:50.278 43009 INFO neutron.wsgi 
[req-a07e31a6-b85f-4a83-baf2-c3c18c259877 None] 172.29.236.10 - - [15/Dec/2015 
13:26:50] "DELETE /v2.0/routers/698f8934-a85d-455c-aa4f-eec7fde36dd7.json 
HTTP/1.1" 204 149 0.115795

  I propose changing the default to the fix used in devstack:

  log_opts = [
  cfg.StrOpt('logging_context_format_string',
     default='%(asctime)s.%(msecs)03d %(process)d %(levelname)s '
     '%(name)s [%(request_id)s %(user_name)s 
%(project_name)s] '
     '%(instance)s%(message)s',

  This applies to both Juno and Kilo, I have not checked anything
  earlier.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1527420/+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 1531607] Re: gate-neutron-dsvm-api: all tests fail with "TypeError: Invalid credentials"

[Armando Migliaccio]

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

Title:
  gate-neutron-dsvm-api: all tests fail with "TypeError: Invalid
  credentials"

Status in neutron:
  Fix Released

Bug description:
  I've hit this twice on submitted patches in the last few days; all
  tests fail with a "TypeError: Invalid Credentials"

  ft1.1: setUpClass 
(neutron.tests.api.admin.test_agent_management.AgentManagementTestJSON)_StringException:
 Traceback (most recent call last):
File "neutron/tests/tempest/test.py", line 260, in setUpClass
  cls.resource_setup()
File "neutron/tests/api/admin/test_agent_management.py", line 24, in 
resource_setup
  super(AgentManagementTestJSON, cls).resource_setup()
File "neutron/tests/api/base.py", line 495, in resource_setup
  super(BaseAdminNetworkTest, cls).resource_setup()
File "neutron/tests/api/base.py", line 65, in resource_setup
  os = cls.get_client_manager()
File "neutron/tests/tempest/test.py", line 391, in get_client_manager
  force_tenant_isolation=force_tenant_isolation,
File "neutron/tests/tempest/common/credentials.py", line 37, in 
get_isolated_credentials
  network_resources=network_resources)
File "neutron/tests/tempest/common/isolated_creds.py", line 39, in __init__
  self._get_admin_clients())
File "neutron/tests/tempest/common/isolated_creds.py", line 48, in 
_get_admin_clients
  os = clients.AdminManager()
File "neutron/tests/api/clients.py", line 115, in __init__
  'identity_admin'),
File "neutron/tests/tempest/common/cred_provider.py", line 64, in 
get_configured_credentials
  credentials = get_credentials(fill_in=fill_in, **params)
File "neutron/tests/tempest/common/cred_provider.py", line 91, in 
get_credentials
  **params)
File "neutron/tests/tempest/auth.py", line 486, in get_credentials
  ca_certs=ca_certs, trace_requests=trace_requests)
File "neutron/tests/tempest/auth.py", line 188, in __init__
  super(KeystoneAuthProvider, self).__init__(credentials)
File "neutron/tests/tempest/auth.py", line 42, in __init__
  raise TypeError("Invalid credentials")
  TypeError: Invalid credentials

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1531607/+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 1533313] [NEW] _get_dvr_sync_data should be optimized for 'dvr' mode agent

[ZongKai LI]

Public bug reported:

Per patch https://review.openstack.org/#/c/239908 for bug "Function
sync_routers always call _get_dvr_sync_data in ha scenario", it will
make _get_dvr_sync_data only be called for agent in 'dvr'/'dvr_snat'
mode, and avoid additional floatingip processing for legacy/HA router
than DVR router.

But for DVR scenario, only query floatingips associated ports on given
host should be necessary, and no need to do additional filter processing
which should be done sql.

** Affects: neutron
 Importance: Undecided
 Assignee: ZongKai LI (lzklibj)
 Status: In Progress

** Changed in: neutron
 Assignee: (unassigned) => ZongKai LI (lzklibj)

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

Title:
  _get_dvr_sync_data should be optimized for 'dvr' mode agent

Status in neutron:
  In Progress

Bug description:
  Per patch https://review.openstack.org/#/c/239908 for bug "Function
  sync_routers always call _get_dvr_sync_data in ha scenario", it will
  make _get_dvr_sync_data only be called for agent in 'dvr'/'dvr_snat'
  mode, and avoid additional floatingip processing for legacy/HA router
  than DVR router.

  But for DVR scenario, only query floatingips associated ports on given
  host should be necessary, and no need to do additional filter
  processing which should be done sql.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1533313/+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 1516765] Re: xenapi: volume_utils._parse_volume_info can leak connection password via StorageError (CVE-2015-8749)

[Grant Murphy]

** Changed in: ossa
   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/1516765

Title:
  xenapi: volume_utils._parse_volume_info can leak connection password
  via StorageError (CVE-2015-8749)

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) juno series:
  Won't Fix
Status in OpenStack Compute (nova) kilo series:
  Fix Committed
Status in OpenStack Compute (nova) liberty series:
  Fix Committed
Status in OpenStack Compute (nova) mitaka series:
  Fix Released
Status in OpenStack Security Advisory:
  Fix Released

Bug description:
  This code dumps the connection_info dict into the StorageError
  message:

  
https://github.com/openstack/nova/blob/12.0.0/nova/virt/xenapi/volume_utils.py#L85-L87

  As can be seen a few lines later, auth_password can be in that dict:

  
https://github.com/openstack/nova/blob/12.0.0/nova/virt/xenapi/volume_utils.py#L96

  So the password would be leaked into the error message that's raised
  up.  This could eventually get back to the logs or a user if not
  handled properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1516765/+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 1533290] Re: nova unit tests failing with os-win 0.1.0

[OpenStack Infra]

Reviewed:  https://review.openstack.org/266505
Committed: 
https://git.openstack.org/cgit/openstack/os-win/commit/?id=0afac9d789de699d87e950955a9c5fd914ce3ae7
Submitter: Jenkins
Branch:master

commit 0afac9d789de699d87e950955a9c5fd914ce3ae7
Author: Claudiu Belu 
Date:   Tue Jan 12 19:29:50 2016 +0200

Avoid initializing WMI connections on Linux

Nova unit tests are failing due to a WMI connection
initialization on Linux. WMI is a Windows specific
module.

Change-Id: I67bf08517707e992f45045511350a884faf260f2
Closes-Bug: #1533290


** Changed in: os-win
   Status: Confirmed => 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/1533290

Title:
  nova unit tests failing with os-win 0.1.0

Status in OpenStack Compute (nova):
  In Progress
Status in os-win:
  Fix Released

Bug description:
  2016-01-12 16:30:52.921 | Captured traceback:
  2016-01-12 16:30:52.921 | ~~~
  2016-01-12 16:30:52.921 | Traceback (most recent call last):
  2016-01-12 16:30:52.921 |   File 
"nova/tests/unit/virt/hyperv/test_imagecache.py", line 59, in setUp
  2016-01-12 16:30:52.921 | self.imagecache = imagecache.ImageCache()
  2016-01-12 16:30:52.922 |   File "nova/virt/hyperv/imagecache.py", line 
39, in __init__
  2016-01-12 16:30:52.922 | self._pathutils = pathutils.PathUtils()
  2016-01-12 16:30:52.922 |   File 
"/home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/os_win/utils/pathutils.py",
 line 46, in __init__
  2016-01-12 16:30:52.922 | super(PathUtils, self).__init__()
  2016-01-12 16:30:52.922 |   File 
"/home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/os_win/utils/storage/smbutils.py",
 line 35, in __init__
  2016-01-12 16:30:52.922 | self._smb_conn = 
wmi.WMI(moniker=r"root\Microsoft\Windows\SMB")
  2016-01-12 16:30:52.922 | NameError: global name 'wmi' is not defined

  https://jenkins05.openstack.org/job/gate-nova-python27/15232/console

  os-win 0.1.0 was released today which is causing the regression:

  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22NameError%3A%20global%20name%20'wmi'%20is%20not%20defined%5C%22%20AND%20tags%3A%5C%22console%5C%22

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1533290/+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 1533290] Re: nova unit tests failing with os-win 0.1.0

[Matt Riedemann]

There is a nova patch proposed here:
https://review.openstack.org/#/c/266495/

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

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

** Changed in: nova
 Assignee: (unassigned) => Claudiu Belu (cbelu)

** Changed in: nova
   Importance: Undecided => High

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

Title:
  nova unit tests failing with os-win 0.1.0

Status in OpenStack Compute (nova):
  In Progress
Status in os-win:
  Confirmed

Bug description:
  2016-01-12 16:30:52.921 | Captured traceback:
  2016-01-12 16:30:52.921 | ~~~
  2016-01-12 16:30:52.921 | Traceback (most recent call last):
  2016-01-12 16:30:52.921 |   File 
"nova/tests/unit/virt/hyperv/test_imagecache.py", line 59, in setUp
  2016-01-12 16:30:52.921 | self.imagecache = imagecache.ImageCache()
  2016-01-12 16:30:52.922 |   File "nova/virt/hyperv/imagecache.py", line 
39, in __init__
  2016-01-12 16:30:52.922 | self._pathutils = pathutils.PathUtils()
  2016-01-12 16:30:52.922 |   File 
"/home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/os_win/utils/pathutils.py",
 line 46, in __init__
  2016-01-12 16:30:52.922 | super(PathUtils, self).__init__()
  2016-01-12 16:30:52.922 |   File 
"/home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/os_win/utils/storage/smbutils.py",
 line 35, in __init__
  2016-01-12 16:30:52.922 | self._smb_conn = 
wmi.WMI(moniker=r"root\Microsoft\Windows\SMB")
  2016-01-12 16:30:52.922 | NameError: global name 'wmi' is not defined

  https://jenkins05.openstack.org/job/gate-nova-python27/15232/console

  os-win 0.1.0 was released today which is causing the regression:

  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22NameError%3A%20global%20name%20'wmi'%20is%20not%20defined%5C%22%20AND%20tags%3A%5C%22console%5C%22

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1533290/+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 1533290] [NEW] nova unit tests failing with os-win 0.1.0

[Matt Riedemann]

Public bug reported:

2016-01-12 16:30:52.921 | Captured traceback:
2016-01-12 16:30:52.921 | ~~~
2016-01-12 16:30:52.921 | Traceback (most recent call last):
2016-01-12 16:30:52.921 |   File 
"nova/tests/unit/virt/hyperv/test_imagecache.py", line 59, in setUp
2016-01-12 16:30:52.921 | self.imagecache = imagecache.ImageCache()
2016-01-12 16:30:52.922 |   File "nova/virt/hyperv/imagecache.py", line 39, 
in __init__
2016-01-12 16:30:52.922 | self._pathutils = pathutils.PathUtils()
2016-01-12 16:30:52.922 |   File 
"/home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/os_win/utils/pathutils.py",
 line 46, in __init__
2016-01-12 16:30:52.922 | super(PathUtils, self).__init__()
2016-01-12 16:30:52.922 |   File 
"/home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/os_win/utils/storage/smbutils.py",
 line 35, in __init__
2016-01-12 16:30:52.922 | self._smb_conn = 
wmi.WMI(moniker=r"root\Microsoft\Windows\SMB")
2016-01-12 16:30:52.922 | NameError: global name 'wmi' is not defined

https://jenkins05.openstack.org/job/gate-nova-python27/15232/console

os-win 0.1.0 was released today which is causing the regression:

http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22NameError%3A%20global%20name%20'wmi'%20is%20not%20defined%5C%22%20AND%20tags%3A%5C%22console%5C%22

** Affects: os-win
 Importance: Undecided
 Status: Confirmed


** Tags: hyper-v testing

** Also affects: os-win
   Importance: Undecided
   Status: New

** No longer affects: nova

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

Title:
  nova unit tests failing with os-win 0.1.0

Status in os-win:
  Confirmed

Bug description:
  2016-01-12 16:30:52.921 | Captured traceback:
  2016-01-12 16:30:52.921 | ~~~
  2016-01-12 16:30:52.921 | Traceback (most recent call last):
  2016-01-12 16:30:52.921 |   File 
"nova/tests/unit/virt/hyperv/test_imagecache.py", line 59, in setUp
  2016-01-12 16:30:52.921 | self.imagecache = imagecache.ImageCache()
  2016-01-12 16:30:52.922 |   File "nova/virt/hyperv/imagecache.py", line 
39, in __init__
  2016-01-12 16:30:52.922 | self._pathutils = pathutils.PathUtils()
  2016-01-12 16:30:52.922 |   File 
"/home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/os_win/utils/pathutils.py",
 line 46, in __init__
  2016-01-12 16:30:52.922 | super(PathUtils, self).__init__()
  2016-01-12 16:30:52.922 |   File 
"/home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/os_win/utils/storage/smbutils.py",
 line 35, in __init__
  2016-01-12 16:30:52.922 | self._smb_conn = 
wmi.WMI(moniker=r"root\Microsoft\Windows\SMB")
  2016-01-12 16:30:52.922 | NameError: global name 'wmi' is not defined

  https://jenkins05.openstack.org/job/gate-nova-python27/15232/console

  os-win 0.1.0 was released today which is causing the regression:

  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22NameError%3A%20global%20name%20'wmi'%20is%20not%20defined%5C%22%20AND%20tags%3A%5C%22console%5C%22

To manage notifications about this bug go to:
https://bugs.launchpad.net/os-win/+bug/1533290/+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 1508442] Re: LOG.warn is deprecated

[sumit]

Python 3 deprecated the logger.warn method in favor of warning

Python 3 deprecated the logger.warn method, see:
https://docs.python.org/3/library/logging.html#logging.warning, so we
prefer to use warning to avoid DeprecationWarning.

Change-Id: Ibc234aedad20351861462f1ebd0457632bdfd048
Closes-Bug: #1508442

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

** Changed in: shaker
 Assignee: (unassigned) => sumit (er-sksumit)

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

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

Title:
  LOG.warn is deprecated

Status in Aodh:
  In Progress
Status in Astara:
  Fix Released
Status in Blazar:
  In Progress
Status in Ceilometer:
  Fix Released
Status in cloud-init:
  In Progress
Status in cloudkitty:
  Fix Released
Status in Designate:
  Fix Released
Status in django-openstack-auth:
  Fix Released
Status in DragonFlow:
  Fix Released
Status in Glance:
  In Progress
Status in Gnocchi:
  In Progress
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in Ironic Inspector:
  Fix Released
Status in ironic-lib:
  Fix Committed
Status in ironic-python-agent:
  Fix Released
Status in OpenStack Identity (keystone):
  In Progress
Status in kolla:
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Released
Status in networking-cisco:
  In Progress
Status in networking-odl:
  In Progress
Status in networking-ofagent:
  In Progress
Status in networking-vsphere:
  In Progress
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  In Progress
Status in nova-powervm:
  Fix Released
Status in octavia:
  In Progress
Status in openstack-ansible:
  In Progress
Status in oslo.cache:
  Fix Released
Status in oslo.privsep:
  In Progress
Status in Packstack:
  Fix Released
Status in python-magnumclient:
  Fix Released
Status in shaker:
  In Progress
Status in Solum:
  In Progress
Status in tempest:
  In Progress
Status in tripleo:
  In Progress
Status in tuskar:
  In Progress
Status in zaqar:
  In Progress

Bug description:
  LOG.warn is deprecated in Python 3 [1] . But it still used in a few
  places, non-deprecated LOG.warning should be used instead.

  Note: If we are using logger from oslo.log, warn is still valid [2],
  but I agree we can switch to LOG.warning.

  [1]https://docs.python.org/3/library/logging.html#logging.warning
  [2]https://github.com/openstack/oslo.log/blob/master/oslo_log/log.py#L85

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1508442/+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 1508243] Re: Store Private Key Passphrase in Neutron-LBaaS for TLS Terminations

[Doug Wiegley]

** Changed in: neutron
   Status: Triaged => Won't Fix

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

Title:
  Store Private Key Passphrase in Neutron-LBaaS for TLS Terminations

Status in neutron:
  Won't Fix

Bug description:
  The current workflow for TLS Termination on loadbalancers has a couple
  of interesting security vulnerabilities that need to be addressed
  somehow. The solution I propose is to encourage the use of passphrase
  encryption on private keys, and to store that passphrase in Neutron-
  LBaaS along with the Barbican href, instead of inside Barbican.

  Spec: https://review.openstack.org/237807

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1508243/+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 1517839] Re: Make CONF.set_override with paramter enforce_type=True by default

[tingwang]

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

** Changed in: watcher
 Assignee: (unassigned) => tingwang (bx-wang)

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

Title:
  Make CONF.set_override with paramter enforce_type=True by default

Status in Ceilometer:
  New
Status in cloudkitty:
  New
Status in Designate:
  New
Status in Gnocchi:
  In Progress
Status in heat:
  New
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  New
Status in neutron:
  New
Status in oslo.config:
  New
Status in oslo.messaging:
  Fix Released
Status in Rally:
  Fix Released
Status in watcher:
  New

Bug description:
  1. Problems :
 oslo_config provides method CONF.set_override[1] , developers usually use 
it to change config option's value in tests. That's convenient .
 By default  parameter enforce_type=False,  it doesn't check any type or 
value of override. If set enforce_type=True , will check parameter
 override's type and value.  In production code(running time code),  
oslo_config  always checks  config option's value.
 In short, we test and run code in different ways. so there's  gap:  config 
option with wrong type or invalid value can pass tests when
 parameter enforce_type = False in consuming projects.  that means some 
invalid or wrong tests are in our code base.
 There is nova POC result when I enable "enforce_type=true" [2],  and I 
must fix them in [3]

 [1] 
https://github.com/openstack/oslo.config/blob/master/oslo_config/cfg.py#L2173
 [2] 
http://logs.openstack.org/16/242416/1/check/gate-nova-python27/97b5eff/testr_results.html.gz
 [3]  https://review.openstack.org/#/c/242416/  
https://review.openstack.org/#/c/242717/  
https://review.openstack.org/#/c/243061/

  2. Proposal 
 1) Make  method CONF.set_override with  enforce_type=True  in consuming 
projects. and  fix violations when  enforce_type=True in each project.

2) Make  method CONF.set_override with  enforce_type=True by default
  in oslo_config

 Hope some one from consuming projects can help make
  enforce_type=True in consuming projects and fix violations,

 You can find more details and comments  in
  https://etherpad.openstack.org/p/enforce_type_true_by_default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1517839/+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 1517839] Re: Make CONF.set_override with paramter enforce_type=True by default

[tingwang]

** No longer affects: glance

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

Title:
  Make CONF.set_override with paramter enforce_type=True by default

Status in Ceilometer:
  New
Status in cloudkitty:
  New
Status in Designate:
  New
Status in Gnocchi:
  In Progress
Status in heat:
  New
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  New
Status in neutron:
  New
Status in oslo.config:
  New
Status in oslo.messaging:
  Fix Released
Status in Rally:
  Fix Released

Bug description:
  1. Problems :
 oslo_config provides method CONF.set_override[1] , developers usually use 
it to change config option's value in tests. That's convenient .
 By default  parameter enforce_type=False,  it doesn't check any type or 
value of override. If set enforce_type=True , will check parameter
 override's type and value.  In production code(running time code),  
oslo_config  always checks  config option's value.
 In short, we test and run code in different ways. so there's  gap:  config 
option with wrong type or invalid value can pass tests when
 parameter enforce_type = False in consuming projects.  that means some 
invalid or wrong tests are in our code base.
 There is nova POC result when I enable "enforce_type=true" [2],  and I 
must fix them in [3]

 [1] 
https://github.com/openstack/oslo.config/blob/master/oslo_config/cfg.py#L2173
 [2] 
http://logs.openstack.org/16/242416/1/check/gate-nova-python27/97b5eff/testr_results.html.gz
 [3]  https://review.openstack.org/#/c/242416/  
https://review.openstack.org/#/c/242717/  
https://review.openstack.org/#/c/243061/

  2. Proposal 
 1) Make  method CONF.set_override with  enforce_type=True  in consuming 
projects. and  fix violations when  enforce_type=True in each project.

2) Make  method CONF.set_override with  enforce_type=True by default
  in oslo_config

 Hope some one from consuming projects can help make
  enforce_type=True in consuming projects and fix violations,

 You can find more details and comments  in
  https://etherpad.openstack.org/p/enforce_type_true_by_default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1517839/+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 1533270] [NEW] Adding remote image in v2 when cache is enabled results 500 error

[Mike Fedosin]

Public bug reported:

To reproduce the issue:

1) Add an image without specifying the size
2) Enable caching
3) Get image data. This will succeed because the Content-Length is pulled from 
the remote store (i.e. swift). At this point, the image will be properly cached.
4) Get image data again with v2 api. This will fail with 500 error 
http://paste.openstack.org/show/483545/

It happens for the reason cache middleware couldn't assign value to
image_meta['size'] because it expects a dictionary (as it was in v1
api), but in v2 api it's ImageTarget object.

** Affects: glance
 Importance: Undecided
 Assignee: Darja Shakhray (dshakhray)
 Status: New

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

Title:
  Adding remote image in v2 when cache is enabled results 500 error

Status in Glance:
  New

Bug description:
  To reproduce the issue:

  1) Add an image without specifying the size
  2) Enable caching
  3) Get image data. This will succeed because the Content-Length is pulled 
from the remote store (i.e. swift). At this point, the image will be properly 
cached.
  4) Get image data again with v2 api. This will fail with 500 error 
http://paste.openstack.org/show/483545/

  It happens for the reason cache middleware couldn't assign value to
  image_meta['size'] because it expects a dictionary (as it was in v1
  api), but in v2 api it's ImageTarget object.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1533270/+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 1517839] Re: Make CONF.set_override with paramter enforce_type=True by default

[tingwang]

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

** Changed in: designate
 Assignee: (unassigned) => tingwang (bx-wang)

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

Title:
  Make CONF.set_override with paramter enforce_type=True by default

Status in Ceilometer:
  New
Status in cloudkitty:
  New
Status in Designate:
  New
Status in Glance:
  New
Status in Gnocchi:
  In Progress
Status in heat:
  New
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  New
Status in neutron:
  New
Status in oslo.config:
  New
Status in oslo.messaging:
  Fix Released
Status in Rally:
  Fix Released

Bug description:
  1. Problems :
 oslo_config provides method CONF.set_override[1] , developers usually use 
it to change config option's value in tests. That's convenient .
 By default  parameter enforce_type=False,  it doesn't check any type or 
value of override. If set enforce_type=True , will check parameter
 override's type and value.  In production code(running time code),  
oslo_config  always checks  config option's value.
 In short, we test and run code in different ways. so there's  gap:  config 
option with wrong type or invalid value can pass tests when
 parameter enforce_type = False in consuming projects.  that means some 
invalid or wrong tests are in our code base.
 There is nova POC result when I enable "enforce_type=true" [2],  and I 
must fix them in [3]

 [1] 
https://github.com/openstack/oslo.config/blob/master/oslo_config/cfg.py#L2173
 [2] 
http://logs.openstack.org/16/242416/1/check/gate-nova-python27/97b5eff/testr_results.html.gz
 [3]  https://review.openstack.org/#/c/242416/  
https://review.openstack.org/#/c/242717/  
https://review.openstack.org/#/c/243061/

  2. Proposal 
 1) Make  method CONF.set_override with  enforce_type=True  in consuming 
projects. and  fix violations when  enforce_type=True in each project.

2) Make  method CONF.set_override with  enforce_type=True by default
  in oslo_config

 Hope some one from consuming projects can help make
  enforce_type=True in consuming projects and fix violations,

 You can find more details and comments  in
  https://etherpad.openstack.org/p/enforce_type_true_by_default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1517839/+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 1517839] Re: Make CONF.set_override with paramter enforce_type=True by default

[tingwang]

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

** No longer affects: sahara

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

Title:
  Make CONF.set_override with paramter enforce_type=True by default

Status in Ceilometer:
  New
Status in cloudkitty:
  New
Status in Designate:
  New
Status in Glance:
  New
Status in Gnocchi:
  In Progress
Status in heat:
  New
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  New
Status in neutron:
  New
Status in oslo.config:
  New
Status in oslo.messaging:
  Fix Released
Status in Rally:
  Fix Released

Bug description:
  1. Problems :
 oslo_config provides method CONF.set_override[1] , developers usually use 
it to change config option's value in tests. That's convenient .
 By default  parameter enforce_type=False,  it doesn't check any type or 
value of override. If set enforce_type=True , will check parameter
 override's type and value.  In production code(running time code),  
oslo_config  always checks  config option's value.
 In short, we test and run code in different ways. so there's  gap:  config 
option with wrong type or invalid value can pass tests when
 parameter enforce_type = False in consuming projects.  that means some 
invalid or wrong tests are in our code base.
 There is nova POC result when I enable "enforce_type=true" [2],  and I 
must fix them in [3]

 [1] 
https://github.com/openstack/oslo.config/blob/master/oslo_config/cfg.py#L2173
 [2] 
http://logs.openstack.org/16/242416/1/check/gate-nova-python27/97b5eff/testr_results.html.gz
 [3]  https://review.openstack.org/#/c/242416/  
https://review.openstack.org/#/c/242717/  
https://review.openstack.org/#/c/243061/

  2. Proposal 
 1) Make  method CONF.set_override with  enforce_type=True  in consuming 
projects. and  fix violations when  enforce_type=True in each project.

2) Make  method CONF.set_override with  enforce_type=True by default
  in oslo_config

 Hope some one from consuming projects can help make
  enforce_type=True in consuming projects and fix violations,

 You can find more details and comments  in
  https://etherpad.openstack.org/p/enforce_type_true_by_default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1517839/+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 1517839] Re: Make CONF.set_override with paramter enforce_type=True by default

[tingwang]

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

** Changed in: manila
 Assignee: (unassigned) => tingwang (bx-wang)

** Changed in: glance
 Assignee: (unassigned) => tingwang (bx-wang)

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

Title:
  Make CONF.set_override with paramter enforce_type=True by default

Status in Ceilometer:
  New
Status in cloudkitty:
  New
Status in Glance:
  New
Status in Gnocchi:
  In Progress
Status in heat:
  New
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  New
Status in neutron:
  New
Status in oslo.config:
  New
Status in oslo.messaging:
  Fix Released
Status in Rally:
  Fix Released
Status in Sahara:
  New

Bug description:
  1. Problems :
 oslo_config provides method CONF.set_override[1] , developers usually use 
it to change config option's value in tests. That's convenient .
 By default  parameter enforce_type=False,  it doesn't check any type or 
value of override. If set enforce_type=True , will check parameter
 override's type and value.  In production code(running time code),  
oslo_config  always checks  config option's value.
 In short, we test and run code in different ways. so there's  gap:  config 
option with wrong type or invalid value can pass tests when
 parameter enforce_type = False in consuming projects.  that means some 
invalid or wrong tests are in our code base.
 There is nova POC result when I enable "enforce_type=true" [2],  and I 
must fix them in [3]

 [1] 
https://github.com/openstack/oslo.config/blob/master/oslo_config/cfg.py#L2173
 [2] 
http://logs.openstack.org/16/242416/1/check/gate-nova-python27/97b5eff/testr_results.html.gz
 [3]  https://review.openstack.org/#/c/242416/  
https://review.openstack.org/#/c/242717/  
https://review.openstack.org/#/c/243061/

  2. Proposal 
 1) Make  method CONF.set_override with  enforce_type=True  in consuming 
projects. and  fix violations when  enforce_type=True in each project.

2) Make  method CONF.set_override with  enforce_type=True by default
  in oslo_config

 Hope some one from consuming projects can help make
  enforce_type=True in consuming projects and fix violations,

 You can find more details and comments  in
  https://etherpad.openstack.org/p/enforce_type_true_by_default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1517839/+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 1533260] [NEW] Unexpected API Error is returned, when trying to add fixed IP to an instance in ERROR state

[Anna Babich]

Public bug reported:

A negative test case returns an Unexpected API Error, while there is
more detailed message in nova-api.log:

2016-01-12 15:12:49.357 22446 ERROR nova.api.openstack.extensions 
NovaException: Unable to find host for Instance 
efbbb0cb-fe5f-4047-868e-69305536bcd4
2016-01-12 15:12:49.391 22446 INFO nova.osapi_compute.wsgi.server 
[req-e22c4d4d-37c8-443d-8038-15ec3f47d01a 7f0fce3a7e3f479b9933eff3df35649d 
65d0c9e644ac4c518e76bc9922ef47ee - - -] 192.168.0.2 "POST 
/v2/65d0c9e644ac4c518e76bc9922ef47ee/servers/efbbb0cb-fe5f-4047-868e-69305536bcd4/action
 HTTP/1.1" status: 500 len: 428 time: 0.3730938

Steps to reproduce:
1. Create net01: net01__subnet, 192.168.1.0/24:
neutron net-create net01
neutron subnet-create net01 192.168.1.0/24 --enable-dhcp --name net01__subnet
2. Boot an instance vm1 in net01 with incorrect compute node:
NET_ID=$(neutron net-list | grep 'net01' | awk '{print $2}')
nova boot --flavor m1.micro --image TestVM --nic net-id=$NET_ID 
--security-groups default --availability-zone 
nova: vm1
3. Check that the instance is in ERROR state now and isn’t assigned to any host:
nova show vm1 | grep OS-EXT-SRV-ATTR:host && nova show vm1 | grep status
| OS-EXT-SRV-ATTR:host | -  


|
| status   | ERROR  


 
4. Try to assign fixed IP to the instance vm1 and ensure that it returns an 
error:
nova add-fixed-ip vm1 $NET_ID

The expected result: 
An error message, something like " Returning 409 to user: Cannot 
'attach_interface' instance efbbb0cb-fe5f-4047-868e-69305536bcd4 while it is in 
vm_state error " appears

The actual  result:  
ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
 (HTTP 500) (Request-ID: 
req-e22c4d4d-37c8-443d-8038-15ec3f47d01a) 
appears

Nova version - http://paste.openstack.org/show/483603/
nova-api logs for faulty instance - http://paste.openstack.org/show/483611/

** Affects: nova
 Importance: Undecided
 Status: New

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

Title:
  Unexpected API Error is returned, when trying to add fixed IP to an
  instance in ERROR state

Status in OpenStack Compute (nova):
  New

Bug description:
  A negative test case returns an Unexpected API Error, while there is
  more detailed message in nova-api.log:

  2016-01-12 15:12:49.357 22446 ERROR nova.api.openstack.extensions 
NovaException: Unable to find host for Instance 
efbbb0cb-fe5f-4047-868e-69305536bcd4
  2016-01-12 15:12:49.391 22446 INFO nova.osapi_compute.wsgi.server 
[req-e22c4d4d-37c8-443d-8038-15ec3f47d01a 7f0fce3a7e3f479b9933eff3df35649d 
65d0c9e644ac4c518e76bc9922ef47ee - - -] 192.168.0.2 "POST 
/v2/65d0c9e644ac4c518e76bc9922ef47ee/servers/efbbb0cb-fe5f-4047-868e-69305536bcd4/action
 HTTP/1.1" status: 500 len: 428 time: 0.3730938

  Steps to reproduce:
  1. Create net01: net01__subnet, 192.168.1.0/24:
  neutron net-create net01
  neutron subnet-create net01 192.168.1.0/24 --enable-dhcp --name net01__subnet
  2. Boot an instance vm1 in net01 with incorrect compute node:
  NET_ID=$(neutron net-list | grep 'net01' | awk '{print $2}')
  nova boot --flavor m1.micro --image TestVM --nic net-id=$NET_ID 
--security-groups default --availability-zone 
nova: vm1
  3. Check that the instance is in ERROR state now and isn’t assigned to any 
host:
  nova show vm1 | grep OS-EXT-SRV-ATTR:host && nova show vm1 | grep status
  | OS-EXT-SRV-ATTR:host | -


  |
  | status   | ERROR


   
  4. Try to assign fixed IP to the instance vm1 and ensure that it returns an 
error:
  nova add-fixed-ip vm1 $NET_ID

  The expected result: 
  An error message, something like " Returning 409 to user: Cannot 
'attach_interface' instance efbbb0cb-fe5f-4047-868e-69305536bcd4 while it is in 
vm_state error " appears

  The actual  result:  
  ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
   (HTTP 500) (Request-ID: 
re

[Yahoo-eng-team] [Bug 1517839] Re: Make CONF.set_override with paramter enforce_type=True by default

[tingwang]

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

** Changed in: heat
 Assignee: (unassigned) => tingwang (bx-wang)

** Also affects: manila
   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/1517839

Title:
  Make CONF.set_override with paramter enforce_type=True by default

Status in Ceilometer:
  New
Status in cloudkitty:
  New
Status in Glance:
  New
Status in Gnocchi:
  In Progress
Status in heat:
  New
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  New
Status in neutron:
  New
Status in oslo.config:
  New
Status in oslo.messaging:
  Fix Released
Status in Rally:
  Fix Released

Bug description:
  1. Problems :
 oslo_config provides method CONF.set_override[1] , developers usually use 
it to change config option's value in tests. That's convenient .
 By default  parameter enforce_type=False,  it doesn't check any type or 
value of override. If set enforce_type=True , will check parameter
 override's type and value.  In production code(running time code),  
oslo_config  always checks  config option's value.
 In short, we test and run code in different ways. so there's  gap:  config 
option with wrong type or invalid value can pass tests when
 parameter enforce_type = False in consuming projects.  that means some 
invalid or wrong tests are in our code base.
 There is nova POC result when I enable "enforce_type=true" [2],  and I 
must fix them in [3]

 [1] 
https://github.com/openstack/oslo.config/blob/master/oslo_config/cfg.py#L2173
 [2] 
http://logs.openstack.org/16/242416/1/check/gate-nova-python27/97b5eff/testr_results.html.gz
 [3]  https://review.openstack.org/#/c/242416/  
https://review.openstack.org/#/c/242717/  
https://review.openstack.org/#/c/243061/

  2. Proposal 
 1) Make  method CONF.set_override with  enforce_type=True  in consuming 
projects. and  fix violations when  enforce_type=True in each project.

2) Make  method CONF.set_override with  enforce_type=True by default
  in oslo_config

 Hope some one from consuming projects can help make
  enforce_type=True in consuming projects and fix violations,

 You can find more details and comments  in
  https://etherpad.openstack.org/p/enforce_type_true_by_default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1517839/+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 1531743] Re: ipsec site connection status is blocked on "DOWN"

[OpenStack Infra]

Reviewed:  https://review.openstack.org/264712
Committed: 
https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=d6a1c3cda8403a45dc08c6cedad31befedb2cd43
Submitter: Jenkins
Branch:master

commit d6a1c3cda8403a45dc08c6cedad31befedb2cd43
Author: Sun Zhengnan 
Date:   Thu Jan 7 03:23:50 2016 -0500

ipsec site connection status is blocked on "DOWN"

when a normal tenant creates a ipsec-site-connection, it will report
all the vpnservices status（including other tenant's resources, which
status is changed but not reported by the looping call) on the same
network node to the neutron-server.
But the status report will be ignored, as it is another tenant.
As a result, when the other tenant does a status update,
it won't see the change.

This change prevents a non-admin tenant from updating the internal
status for a connections owned by other tenants and thereby preventing
the other client from seeing the status change.

Change-Id: I31b8ed1454a645b8c68c28feeeb628ddf5d1eebc
Closes-Bug: #1531743


** Changed in: neutron
   Status: In Progress => 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/1531743

Title:
  ipsec site connection status is blocked on "DOWN"

Status in neutron:
  Fix Released

Bug description:
  When I create two ipsec-site-connections as the following steps,
  the first ipsec-site-connection's status is blocked on "DOWN"
  the environment has only one network node.
  step1: use tenantA create ipsec-site-connection-A
  step2: use tenantB(not admin tenant)create  ipsec-site-connection-B

  After  ipsec-site-connection-B is created,  ipsec-site-connection-B's
  status becomes "ACTIVE" while  ipsec-site-connection-A's status
  is blocked on "DOWN"

  This can happen on the following condition too.
  environment A has only one network node.
  step1: use tenantA create ipsec-site-connection-A on environment A
  step2: use tenantB create ipsec-site-connection-B on environment B
  step3: before the neutron-vpn-agent's loopcall is executed on environment A
   use tenantC(not admin tenant) to create ipsec-site-connection-C
  After ipsec-site-connection-C is created,  ipsec-site-connection-A's status
  is blocked on "DOWN" and can not be changed by the neutron-vpn-agent's 
loopcall.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1531743/+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 1479243] Re: _core_plugin should be put into plugins\common\utils.py

[Martin Hickey]

Hi huangpengtaohw,

Setting to invalid. Re-open if you think differently.

Thanks,
Martin

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

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

Title:
  _core_plugin should be put into plugins\common\utils.py

Status in neutron:
  Invalid

Bug description:
  the below function: 
 @property
  def _core_plugin(self):
  return manager.NeutronManager.get_plugin()
  is put into many class 'L3_NAT_dbonly_mixin', 'Firewall_db_mixin', and so on.
  as a common useful function , it should be put in ' plugins\common\utils.py' 
file  to avoid many definition.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1479243/+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] Re: Fix usage of assertions

[Eric Harney]

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

** Changed in: cinder
 Assignee: Yatin Kumbhare (yatinkumbhare-c) => (unassigned)

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

Title:
  Fix usage of assertions

Status in Aodh:
  Fix Released
Status in Barbican:
  Fix Released
Status in Blazar:
  In Progress
Status in Cinder:
  Invalid
Status in congress:
  Fix Released
Status in Cue:
  In Progress
Status in Glance:
  Won't Fix
Status in Group Based Policy:
  In Progress
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic:
  Fix Released
Status in Ironic Inspector:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in kuryr:
  In Progress
Status in Magnum:
  In Progress
Status in Manila:
  Fix Released
Status in Murano:
  In Progress
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Health:
  In Progress
Status in os-brick:
  Fix Released
Status in os-net-config:
  In Progress
Status in os-testr:
  In Progress
Status in oslo.cache:
  Fix Released
Status in oslo.messaging:
  Fix Released
Status in oslo.utils:
  In Progress
Status in Packstack:
  Fix Released
Status in python-barbicanclient:
  In Progress
Status in python-ceilometerclient:
  Fix Released
Status in python-novaclient:
  Fix Released
Status in python-openstackclient:
  Fix Released
Status in OpenStack SDK:
  Fix Released
Status in Rally:
  In Progress
Status in refstack:
  In Progress
Status in requests-mock:
  In Progress
Status in Sahara:
  Fix Released
Status in shaker:
  Fix Released
Status in Solum:
  In Progress
Status in Stackalytics:
  Fix Released
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress
Status in Trove:
  Fix Released
Status in tuskar:
  In Progress
Status in Vitrage:
  Fix Released
Status in watcher:
  Fix Released
Status in zaqar:
  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/aodh/+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 1533083] Re: useless HTTP info in the error info for creating existing flavor

[Fahri Cihan Demirci]

Thank you very much. Marking invalid for nova, adding python-novaclient
as affects.

** Also affects: python-novaclient
   Importance: Undecided
   Status: New

** Changed in: nova
   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/1533083

Title:
  useless HTTP info in the error info for creating existing flavor

Status in OpenStack Compute (nova):
  Invalid
Status in python-novaclient:
  New

Bug description:
  [Summary]
  useless HTTP info in the error info for creating existing flavor
  [Topo]
  devstack all-in-one node

  [Description and expect result]
  no useless HTTP info in the error info for creating existing flavor

  [Reproduceable or not]
  reproduceable 

  [Recreate Steps]
  1) create an existing flavor:
  root@45-59:/opt/stack/devstack# nova flavor-create --is-public
   false f1 13 1024 1 1
  ERROR (Conflict): Flavor with name f1 already exists. (HTTP 409) 
  (Request-ID: req-3769491c-5f82-4064-8b45-ef1a3442957d)
  root@45-59:/opt/stack/devstack# 

  ISSUE: For a cli user, the info "ERROR (Conflict): Flavor with name
   f1 already exists." is enough, it let user know what happened. 
  But the info "HTTP 409" is useless

  2) same issue when remove a non-existing flavor-access:
  root@45-59:/opt/stack/devstack# nova  flavor-access-remove 13 adminm
  ERROR (NotFound): Flavor access not found for 13 / adminm combination.
   (HTTP 404) (Request-ID: req-2eeb9656-72a9-45d8-bbe0-48536c8e0b5d)
  root@45-59:/opt/stack/devstack# 

  3)Below is the error info when remove a non-existing flavor for reference:
  root@45-59:/opt/stack/devstack# nova flavor-delete aa
  ERROR (CommandError): No flavor with a name or ID of 'aa' exists.
  root@45-59:/opt/stack/devstack# 


  [Configration]
  reproduceable bug, no need

  [logs]
  reproduceable bug, no need

  [Root cause anlyze or debug inf]
  reproduceable bug

  [Attachment]
  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1533083/+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 1282265] Re: Create Backup under Database Detail doesn't populate Database Instance

[Timur Sufiev]

** Project changed: horizon => trove-dashboard

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

Title:
  Create Backup under Database Detail doesn't populate Database Instance

Status in trove-dashboard:
  New

Bug description:
  To reproduce:

  1. Create two database instances.
  2. Click one of them to go to the Database Details view.
  3. Click the Backups tab.
  4. Click the Create Backup button. Note the Database Instance field. Repeat 
steps 2-4 for the other database instance.

  Depending on the sorting of the Database Instances, one of the two
  Create Backup attempts will not populate the Database Instance
  correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/trove-dashboard/+bug/1282265/+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 1427277] Re: [UI] Detailed error on job binary creation is not shown

[Rob Cresswell]

** Summary changed:

- [sahara] Detailed error on job binary creation is not shown
+ [UI] Detailed error on job binary creation is not shown

** Tags removed: sahara
** Tags added: dashboard

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

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

Title:
  [UI] Detailed error on job binary creation is not shown

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in Sahara:
  New

Bug description:
  When a job binary with an invalid name is created (for example: too long, 
like currently test_script_name_a5a330ee-bce0-11e4-beaf-3c970e1836cf), Sahara 
returns an well-defined exception, from the logs:
  DEBUG sahara.utils.api [-] Validation Error occurred: error_code=400, 
error_message=u'test_script_name_a5a330ee-bce0-11e4-beaf-3c970e1836cf' is too 
long, error_name=VALIDATION_ERROR bad_request 
/usr/lib/python2.7/site-packages/sahara/utils/api.py:245
  but Horizon just says:
  Error: Unable to create job binary 

  Tested on current Horizon master, Sahara from Juno (even if this is an
  horizon issue, I think).

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1427277/+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 1500468] Re: [Sahara] Cluster Node Process list display is unsightly

[Rob Cresswell]

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

** Tags removed: sahara
** Tags added: dashboard

** Summary changed:

- [Sahara] Cluster Node Process list display is unsightly
+ [UI] Cluster Node Process list display is unsightly

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

Title:
  [UI] Cluster Node Process list display is unsightly

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in Sahara:
  New

Bug description:
  ** Low Priority **

  Under Data Processing -> Clusters ->  to see the
  details page, then click on the Node Groups tab.

  The alignment of the list of node processes is rather ugly.  The dots
  for the list appear to the left of everything else in the node group
  details.  It seems like the list should be indented with respect to
  the Node Processes label.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1500468/+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 1322005] Re: change default first panel to the clicked panel

[Rob Cresswell]

The expected behaviour is what I observe in master. Please reopen the
bug if I have misunderstood.

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

** Changed in: horizon
 Assignee: tinytmy (tangmeiyan77) => (unassigned)

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

Title:
  change default first panel to the clicked panel

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Steps to reproduce:
  1.login as admin
  2.click 'Project Dashboard',it default expand 'Compute' panel.
  3.click 'Network' panel header
  4.click 'Project Dashboard' collapse all panels
  5.click 'Project Dashboard'
  we see it again expand 'Compute Panel', maybe it is better expand 'Network 
Panel'

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1322005/+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 1498219] Re: Address comments for Database Clustering patch

[Matthias Runge]

** Also affects: trove-dashboard
   Importance: Undecided
   Status: New

** No longer affects: horizon

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

Title:
  Address comments for Database Clustering patch

Status in trove-dashboard:
  New

Bug description:
  There are still couple of comments and question for database
  clustering patch.

  https://review.openstack.org/#/c/110411/40

  The comments are minor and not worth blocking the patch.

  The patch was merged and this bug is for tracking the work to follow-
  up on the comments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/trove-dashboard/+bug/1498219/+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 1410941] Re: [data processing] The "Plugin Select" dialogs use unnecessary javascript

[Rob Cresswell]

** Tags removed: sahara
** Tags added: dashboard

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

** Summary changed:

- [data processing] The "Plugin Select" dialogs use unnecessary javascript
+ [UI] The "Plugin Select" dialogs use unnecessary javascript

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

Title:
  [UI] The "Plugin Select" dialogs use unnecessary javascript

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in Sahara:
  New

Bug description:
  * This is a technical debt item that is leftover from when we merged
  the Sahara dashboard into horizon.

  When clicking on the "create/launch" button for node group templates,
  cluster templates, or clusters the user is presented with a form to
  choose their plugin and version.  Currently, the "version" select
  boxes are hidden or shown by some custom javascript on each of those
  pages.  Instead, the switched/switchable mechanic from horizon should
  be used to control the appearance/hiding of each of the version
  dropdowns.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1410941/+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 1524291] Re: check_ports_on_host_and_subnet() duplicates check_ports_exist_on_l3agent()

[OpenStack Infra]

Reviewed:  https://review.openstack.org/255374
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=56eb877d250794a38bcf4f6b94aee1add4723ae0
Submitter: Jenkins
Branch:master

commit 56eb877d250794a38bcf4f6b94aee1add4723ae0
Author: Oleg Bondarev 
Date:   Wed Dec 9 17:58:14 2015 +0300

Remove duplicate for check_ports_exist_on_l3agent

This removes check_ports_on_host_and_subnet which mostly duplicates what
check_ports_exist_on_l3agent is doing.
Also rename check_ports_exist_on_l3agent to 
check_dvr_serviceable_ports_on_host
for more clarity.

Closes-Bug: #1524291
Change-Id: Ie02c68279c2bbafffc7be4d9a81fe25a0e983d58


** Changed in: neutron
   Status: In Progress => 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/1524291

Title:
  check_ports_on_host_and_subnet() duplicates
  check_ports_exist_on_l3agent()

Status in neutron:
  Fix Released

Bug description:
  check_ports_on_host_and_subnet() mostly duplicates
  check_ports_exist_on_l3agent() and should be removed

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1524291/+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 1529836] Re: Fix deprecated library function (os.popen()).

[LiuNanke]

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

** Changed in: heat
 Assignee: (unassigned) => LiuNanke (nanke-liu)

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

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

Title:
  Fix deprecated library function (os.popen()).

Status in Ceilometer:
  In Progress
Status in Cinder:
  In Progress
Status in devstack:
  In Progress
Status in Glance:
  In Progress
Status in heat:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  Fix Released
Status in Murano:
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo-incubator:
  In Progress
Status in python-keystoneclient:
  Fix Released
Status in Python client library for Zaqar:
  In Progress
Status in Sahara:
  Fix Released
Status in senlin:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress

Bug description:
  Deprecated library function os.popen is still in use at some places.
  Need to replace it using subprocess module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1529836/+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 1410586] Re: Sahara: Copy template does not preserve security groups

[Rob Cresswell]

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

** Tags added: dashboard

** Summary changed:

- Sahara: Copy template does not preserve security groups
+ [UI] Copy template does not preserve security groups

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

Title:
  [UI] Copy template does not preserve security groups

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in Sahara:
  New

Bug description:
  When clicking "copy template" from the Node Group Templates panel of
  Data Processing, all fields are shown as copied from the original
  template, except for security groups. The checkbox selections under
  "Processes" are carried-over, but all security groups are unchecked,
  regardless of which are checked in the original template.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1410586/+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 1427328] Re: [sahara] The mechanism used to avoid duplicate script names in jobs binaries is fragile

[Rob Cresswell]

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

** Summary changed:

- [sahara] The mechanism used to avoid duplicate script names in jobs binaries 
is fragile
+ [UI] The mechanism used to avoid duplicate script names in jobs binaries is 
fragile

** Tags removed: sahara
** Tags added: dashboard

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

Title:
  [UI] The mechanism used to avoid duplicate script names in jobs
  binaries is fragile

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in Sahara:
  New

Bug description:
  Create a Job Binary in the internal db, with a specific script name
  (for example, "script_name").

  If the user creates another job binary with the same script name, a unique 
UUID is added so that the name is unique. 
  But, if the script name is long, the addition of the UUID can make it longer 
than the field limit (80 characters) and the job creation fails.
  Moreover, this mechanism is counterintuitive as it is not implemented for the 
job binary "name" field (an error is returned).

  Proposal:
  - remove the mechanism which tries to create an unique script name, and 
simply returns a validation error if a script name is duplicated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1427328/+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 1456250] Re: [UI] launch job configuration preset names are incorrect

[Rob Cresswell]

** Summary changed:

- [sahara] launch job configuration preset names are incorrect
+ [UI] launch job configuration preset names are incorrect

** Tags added: dashboard

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

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

Title:
  [UI] launch job configuration preset names are incorrect

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in Sahara:
  New

Bug description:
  When we launch a job by a job_template, e.g., a hive job_template, go
  to "Configure" tab, and click "Add" under Configuration, then click
  the "Name" input box, you are supposed to get a default key list.
  However, you get a default value list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1456250/+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 1427304] Re: [sahara] When the job binary creating fails, the job binary data is created anyway

[Rob Cresswell]

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

** Summary changed:

- [sahara] When the job binary creating fails, the job binary data is created 
anyway
+ [UI] When the job binary creating fails, the job binary data is created anyway

** Tags removed: sahara
** Tags added: dashboard

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

Title:
  [UI] When the job binary creating fails, the job binary data is
  created anyway

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in Sahara:
  New

Bug description:
  If the user tries to create a Job Binary using the internal db as
  storage, and the creating fails for a validation error, the job binary
  data is created anyway.

  The job data creation code should be executed at the same time/in the
  same transaction of the job binary creation (and rolled back if the
  latter fails).

  Found on current Horizon git master (Sahara from Juno, but the problem
  seems more Horizon-related).

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1427304/+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 1430112] Re: [sahara]loading node group template page takes a long time for cdh plugin

[Rob Cresswell]

** Tags added: dashboard

** Summary changed:

- [sahara]loading node group template page takes a long time for cdh plugin
+ [UI] Loading node group template page takes a long time for cdh plugin

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

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

Title:
  [UI] Loading node group template page takes a long time for cdh plugin

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in Sahara:
  New

Bug description:
  Steps to reproduce:
  1. Launch horizon console from browser
  2. Click "Node Group Templates" page in "Project" - "Data Processing"
  3. Click "Create Template"
  4. You will see the page is loading and after several minutes the page could 
be error because of the timeout of loading

  I can have success loading sometimes, the success cases usually happened in 
IE 11.
  And it always failed in Chrome.

  However, it looks like the root cause is because there are so many services 
listed in node group templates for cdh plugin.
  Is there any way to solve it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1430112/+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 1394794] Re: [Sahara] Internal error during cluster deletion

[Rob Cresswell]

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

** Tags removed: sahara
** Tags added: dashboard

** Summary changed:

- [Sahara] Internal error during cluster deletion
+ [UI] Internal error during cluster deletion

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

Title:
  [UI] Internal error during cluster deletion

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in Sahara:
  New

Bug description:
  I had 3 clusters I wanted to delete. I marked all three of them and
  clicked 'delete clusters'. After some time 'Failed to update row'
  message occurred on client side.

  Stacktrace from horizon:
  Internal Server Error: /project/data_processing/clusters/
  Traceback (most recent call last):
    File 
"/Users/alazarev/openstack/horizon/.venv/lib/python2.7/site-packages/django/core/handlers/base.py",
 line 112, in get_response
  response = wrapped_callback(request, *callback_args, **callback_kwargs)
    File "/Users/alazarev/openstack/horizon/horizon/decorators.py", line 36, in 
dec
  return view_func(request, *args, **kwargs)
    File "/Users/alazarev/openstack/horizon/horizon/decorators.py", line 52, in 
dec
  return view_func(request, *args, **kwargs)
    File "/Users/alazarev/openstack/horizon/horizon/decorators.py", line 36, in 
dec
  return view_func(request, *args, **kwargs)
    File "/Users/alazarev/openstack/horizon/horizon/decorators.py", line 84, in 
dec
  return view_func(request, *args, **kwargs)
    File 
"/Users/alazarev/openstack/horizon/.venv/lib/python2.7/site-packages/django/views/generic/base.py",
 line 69, in view
  return self.dispatch(request, *args, **kwargs)
    File 
"/Users/alazarev/openstack/horizon/.venv/lib/python2.7/site-packages/django/views/generic/base.py",
 line 87, in dispatch
  return handler(request, *args, **kwargs)
    File "/Users/alazarev/openstack/horizon/horizon/tables/views.py", line 157, 
in get
  handled = self.construct_tables()
    File "/Users/alazarev/openstack/horizon/horizon/tables/views.py", line 143, 
in construct_tables
  preempted = table.maybe_preempt()
    File "/Users/alazarev/openstack/horizon/horizon/tables/base.py", line 1518, 
in maybe_preempt
  error = exceptions.handle(request, ignore=True)
    File "/Users/alazarev/openstack/horizon/horizon/exceptions.py", line 334, 
in handle
  six.reraise(exc_type, exc_value, exc_traceback)
    File "/Users/alazarev/openstack/horizon/horizon/tables/base.py", line 1511, 
in maybe_preempt
  if self.get_object_id(datum) == self.current_item_id:
    File "/Users/alazarev/openstack/horizon/horizon/tables/base.py", line 1655, 
in get_object_id
  return datum.id
  AttributeError: 'NoneType' object has no attribute 'id'
  [20/Nov/2014 23:20:12] "GET 
/project/data_processing/clusters/?action=row_update&table=clusters&obj_id=9a43709b-d998-4a14-be38-8318a44821d7
 HTTP/1.1" 200 1019
  [20/Nov/2014 23:20:13] "GET 
/project/data_processing/clusters/?action=row_update&table=clusters&obj_id=8608c1ba-bb45-4a85-9734-fd602770cba4
 HTTP/1.1" 500 31829

  No errors on sahara side.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1394794/+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 1391698] Re: Sahara should handle 100 response on row update

[Rob Cresswell]

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

** Tags removed: sahara
** Tags added: dashboard

** Summary changed:

- Sahara should handle 100 response on row update
+ [UI] Sahara should handle 100 response on row update

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

Title:
  [UI] Sahara should handle 100 response on row update

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in Sahara:
  New

Bug description:
  I created cluster and was waiting while it is Active. After some time
  I observed in Sahara logs that cluster is already Active. In Horizon
  it was still in Starting state and didn't update. Here what I see in
  horizon logs:

  [12/Nov/2014 00:07:13] "GET 
/project/data_processing/clusters/?action=row_update&table=clusters&obj_id=e11d0970-2163-4521-92e3-25671087f633
 HTTP/1.1" 200 1033
  [12/Nov/2014 00:07:15] "GET 
/project/data_processing/clusters/?action=row_update&table=clusters&obj_id=e11d0970-2163-4521-92e3-25671087f633
 HTTP/1.1" 200 1033
  [12/Nov/2014 00:07:20] "GET 
/project/data_processing/clusters/?action=row_update&table=clusters&obj_id=e11d0970-2163-4521-92e3-25671087f633
 HTTP/1.1" 100 0

  It looks like horizon stops updating cluster table row after 100
  response. I'm not sure why server responded 100, but this is
  definitely wrong behavior either of server side (must not respond with
  100 or should log why this happened) or client side (100 is a valid
  response and should not be treated as fatal error).

  Error from javascript log:
  Failed to load resource: net::ERR_EMPTY_RESPONSE 
http://localhost:8080/project/data_processing/clusters/?action=row_update&table=clusters&obj_id=e11d0970-2163-4521-92e3-25671087f633

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1391698/+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 1341750] Re: [data processing] Replace hard coded form with django form

[Timur Sufiev]

** Project changed: horizon => sahara

** Tags removed: sahara
** Tags added: dashboard

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

Title:
  [data processing] Replace hard coded form with django form

Status in Sahara:
  Confirmed

Bug description:
  This came up during the review of
  https://review.openstack.org/#/c/91058/

  In the data processing -> cluster templates panel, the
  cluster_node_groups_template.html file defines a form in a not-so-
  typical fashion.

  Brifely, there is a javascript variable string that is used to define
  a template for a set of inputs/controls.  The user can add, remove or
  modify sets of these templatized controls before submitting the form.
  It was recommended in a review that we turn this into a more standard
  django form, but agreed that it should be done as a bug fix rather
  than as part of the merge.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sahara/+bug/1341750/+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 1533216] [NEW] item allocator should return same value for same key

[venkata anil]

Public bug reported:

When ItemAllocator.allocate[1] called with same key again,
it is returning different value.

So in dvr, if allocate_rule_priority() called again with same key, it is 
returning different priority value.
So trying to  add same ip rule again is succeeding as we got different priority 
from  allocate_rule_priority(for same key). 
As a consequence we will have same ip rule in router namespace but with 
different priorities.

[1]
https://github.com/openstack/neutron/blob/master/neutron/agent/l3/item_allocator.py#L51

** Affects: neutron
 Importance: Undecided
 Assignee: venkata anil (anil-venkata)
 Status: In Progress

** Changed in: neutron
 Assignee: (unassigned) => venkata anil (anil-venkata)

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

Title:
  item allocator should return same value for same key

Status in neutron:
  In Progress

Bug description:
  When ItemAllocator.allocate[1] called with same key again,
  it is returning different value.

  So in dvr, if allocate_rule_priority() called again with same key, it is 
returning different priority value.
  So trying to  add same ip rule again is succeeding as we got different 
priority from  allocate_rule_priority(for same key). 
  As a consequence we will have same ip rule in router namespace but with 
different priorities.

  [1]
  
https://github.com/openstack/neutron/blob/master/neutron/agent/l3/item_allocator.py#L51

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1533216/+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 1369870] Re: The "message" cookie is not marked as "secure"

[Rob Cresswell]

The default value for SESSION_COOKIE_SECURE is False, but the deployment
guide advises changing it to True.

** Changed in: horizon
   Status: Incomplete => Won't Fix

** Changed in: horizon
 Assignee: Kent Wang (k.wang) => (unassigned)

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

Title:
  The "message" cookie is not marked as "secure"

Status in OpenStack Dashboard (Horizon):
  Won't Fix

Bug description:
  The message cookie is not marked as 'secure', as identified by the
  following security report.  If might contain sensitive information,
  and would benefit from being marked as secure.

  ---

  Affected URL: https://Ip_address/settings/
  Affected Entity: messages, django_timezone, horizon_pagesize, and 
horizon_language
  Risk: It may be possible to steal user and session information (cookies) that 
was sent during an encrypted session

  Causes: The web application sends non-secure cookies over SSL

  Recommend Fix: Add the 'Secure' attribute to all sensitive cookies

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1369870/+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 1361328] Re: trove not supporting multiple regions

[Timur Sufiev]

** Project changed: horizon => trove-dashboard

** Changed in: trove-dashboard
Milestone: next => None

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

Title:
  trove not supporting multiple regions

Status in trove-dashboard:
  Triaged

Bug description:
  refactor of trove code in Horizon broke multi-region support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/trove-dashboard/+bug/1361328/+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 1395897] Re: Database Instance Status confusion

[Timur Sufiev]

** Project changed: horizon => trove-dashboard

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

Title:
  Database Instance Status confusion

Status in trove-dashboard:
  New

Bug description:
  As a new user to Trove, I was confused by the user interface and
  specifically the usage of action tense for the communication of the
  current database status. After what I thought was already launched,
  the status message appeared as "Build". So I naturally assumed that I
  needed to build it. But I did not see a "Build" button, only a
  terminate button. I then assumed that I needed to click the "Launch
  Instance" button in order to build it, but that gave me the modal to
  launch/create a new instance. After some discussion with a colleague
  more familiar with Trove, he told me that Build actually means that
  the database is "building" or being provisioned. So why don't we say
  "Building" instead of "Build", or even more direct -- "Provisioning"?
  I think if we add the "ING" to Build, Reboot and Resize statuses it
  will be much less confusing. Plus this has the added benefit of being
  consistent with Nova (it uses the 'ing' form for statuses). Also
  shouldn't there be a progress bar that appears in the UI when trove is
  working in the background on either the building, rebooting or
  resizing statuses?

  I propose the following renaming of the database statuses to more
  clearly indicate that the action is in progress (and to be consistent
  with Nova):

  Build --> Building
  Reboot --> Rebooting
  Resize --> Resizing

To manage notifications about this bug go to:
https://bugs.launchpad.net/trove-dashboard/+bug/1395897/+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 1503384] Re: Trove - Update launch instance to use datastore-flavors

[Timur Sufiev]

** Project changed: horizon => trove-dashboard

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

Title:
  Trove - Update launch instance to use datastore-flavors

Status in trove-dashboard:
  New

Bug description:
  The Trove launch cluster dialog introduced the use of datastore
  specific flavors.  The launch instance dialog should be updated to use
  the datastore flavors as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/trove-dashboard/+bug/1503384/+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 1514734] Re: gate-horizon-npm-run-lint times out

[Matthias Runge]

seems to be fixed right now.

** Changed in: horizon
   Status: Confirmed => Invalid

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

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

Title:
  gate-horizon-npm-run-lint times out

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  in logs:

  2015-11-10 06:48:33.386 | Err http://us.archive.ubuntu.com trusty InRelease
  2015-11-10 06:48:33.386 |   
  2015-11-10 06:50:05.127 | Get:10 http://us.archive.ubuntu.com trusty-updates 
InRelease [64.4 kB]
  .
  2015-11-10 07:13:27.133 | Hit http://us.archive.ubuntu.com 
trusty-backports/multiverse amd64 Packages
  2015-11-10 07:18:56.251 | Build timed out (after 40 minutes). Marking the 
build as failed.

  
  Looks like a broken mirror slows us down here.

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