[Yahoo-eng-team] [Bug 1583915] [NEW] SRIOV : AttributeError: 'dict' object has no attribute 'partition'
Public bug reported:
With the below pci whitelist in nova.conf , getting the below ERROr
pci_passthrough_whitelist = {"address":{"domain": ".*","bus": "04", "slot":
"00","function": "[1-2]"},"physical_network":"physnet1"}
pci_passthrough_whitelist ={"address":{"domain": ".*","bus": "04", "slot":
"00","function": "[3-4]"},"physical_network":"physnet2"}
2016-05-20 02:37:30.100 ERROR nova.compute.manager
[req-67cc2371-7005-4485-bbb0-b19d5075fd09 None None] Error updating resources
for node stack.
2016-05-20 02:37:30.100 TRACE nova.compute.manager Traceback (most recent call
last):
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/compute/manager.py", line 6275, in
update_available_resource_for_node
2016-05-20 02:37:30.100 TRACE nova.compute.manager
rt.update_available_resource(context)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/compute/resource_tracker.py", line 478, in
update_available_resource
2016-05-20 02:37:30.100 TRACE nova.compute.manager
self._update_available_resource(context, resources)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py", line
271, in inner
2016-05-20 02:37:30.100 TRACE nova.compute.manager return f(*args, **kwargs)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/compute/resource_tracker.py", line 499, in
_update_available_resource
2016-05-20 02:37:30.100 TRACE nova.compute.manager
self._init_compute_node(context, resources)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/compute/resource_tracker.py", line 377, in
_init_compute_node
2016-05-20 02:37:30.100 TRACE nova.compute.manager
self._setup_pci_tracker(context, resources)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/compute/resource_tracker.py", line 396, in
_setup_pci_tracker
2016-05-20 02:37:30.100 TRACE nova.compute.manager self.pci_tracker =
pci_manager.PciDevTracker(context, node_id=n_id)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/pci/manager.py", line 58, in __init__
2016-05-20 02:37:30.100 TRACE nova.compute.manager self.dev_filter =
whitelist.Whitelist(CONF.pci_passthrough_whitelist)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/pci/whitelist.py", line 78, in __init__
2016-05-20 02:37:30.100 TRACE nova.compute.manager self.specs =
self._parse_white_list_from_config(whitelist_spec)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/pci/whitelist.py", line 59, in
_parse_white_list_from_config
2016-05-20 02:37:30.100 TRACE nova.compute.manager spec =
devspec.PciDeviceSpec(ds)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/pci/devspec.py", line 134, in __init__
2016-05-20 02:37:30.100 TRACE nova.compute.manager self._init_dev_details()
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/pci/devspec.py", line 159, in _init_dev_details
2016-05-20 02:37:30.100 TRACE nova.compute.manager self.address =
PciAddress(self.address, pf)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/pci/devspec.py", line 67, in __init__
2016-05-20 02:37:30.100 TRACE nova.compute.manager
self._init_address_fields(pci_addr)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/pci/devspec.py", line 80, in _init_address_fields
2016-05-20 02:37:30.100 TRACE nova.compute.manager dbs, sep, func =
pci_addr.partition('.')
2016-05-20 02:37:30.100 TRACE nova.compute.manager AttributeError: 'dict'
object has no attribute 'partition'
** Affects: nova
Importance: Undecided
Status: Invalid
** Tags: pci sriov
** Project changed: python-novaclient => nova
** Tags added: pci sriov
** 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/1583915
Title:
SRIOV : AttributeError: 'dict' object has no attribute 'partition'
Status in OpenStack Compute (nova):
Invalid
Bug description:
With the below pci whitelist in nova.conf , getting the below ERROr
pci_passthrough_whitelist = {"address":{"domain": ".*","bus": "04", "slot":
"00","function": "[1-2]"},"physical_network":"physnet1"}
pci_passthrough_whitelist ={"address":{"domain": ".*","bus": "04", "slot":
"00","function": "[3-4]"},"physical_network":"physnet2"}
2016-05-20 02:37:30.100 ERROR nova.compute.manager
[req-67cc2371-7005-4485-bbb0-b19d5075fd09 None None] Error updating resources
for node stack.
2016-05-20 02:37:30.100 TRACE nova.compute.manager Traceback (most recent
call last):
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/
[Yahoo-eng-team] [Bug 1583915] [NEW] SRIOV : AttributeError: 'dict' object has no attribute 'partition'
You have been subscribed to a public bug:
With the below pci whitelist in nova.conf , getting the below ERROr
pci_passthrough_whitelist = {"address":{"domain": ".*","bus": "04", "slot":
"00","function": "[1-2]"},"physical_network":"physnet1"}
pci_passthrough_whitelist ={"address":{"domain": ".*","bus": "04", "slot":
"00","function": "[3-4]"},"physical_network":"physnet2"}
2016-05-20 02:37:30.100 ERROR nova.compute.manager
[req-67cc2371-7005-4485-bbb0-b19d5075fd09 None None] Error updating resources
for node stack.
2016-05-20 02:37:30.100 TRACE nova.compute.manager Traceback (most recent call
last):
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/compute/manager.py", line 6275, in
update_available_resource_for_node
2016-05-20 02:37:30.100 TRACE nova.compute.manager
rt.update_available_resource(context)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/compute/resource_tracker.py", line 478, in
update_available_resource
2016-05-20 02:37:30.100 TRACE nova.compute.manager
self._update_available_resource(context, resources)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py", line
271, in inner
2016-05-20 02:37:30.100 TRACE nova.compute.manager return f(*args, **kwargs)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/compute/resource_tracker.py", line 499, in
_update_available_resource
2016-05-20 02:37:30.100 TRACE nova.compute.manager
self._init_compute_node(context, resources)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/compute/resource_tracker.py", line 377, in
_init_compute_node
2016-05-20 02:37:30.100 TRACE nova.compute.manager
self._setup_pci_tracker(context, resources)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/compute/resource_tracker.py", line 396, in
_setup_pci_tracker
2016-05-20 02:37:30.100 TRACE nova.compute.manager self.pci_tracker =
pci_manager.PciDevTracker(context, node_id=n_id)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/pci/manager.py", line 58, in __init__
2016-05-20 02:37:30.100 TRACE nova.compute.manager self.dev_filter =
whitelist.Whitelist(CONF.pci_passthrough_whitelist)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/pci/whitelist.py", line 78, in __init__
2016-05-20 02:37:30.100 TRACE nova.compute.manager self.specs =
self._parse_white_list_from_config(whitelist_spec)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/pci/whitelist.py", line 59, in
_parse_white_list_from_config
2016-05-20 02:37:30.100 TRACE nova.compute.manager spec =
devspec.PciDeviceSpec(ds)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/pci/devspec.py", line 134, in __init__
2016-05-20 02:37:30.100 TRACE nova.compute.manager self._init_dev_details()
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/pci/devspec.py", line 159, in _init_dev_details
2016-05-20 02:37:30.100 TRACE nova.compute.manager self.address =
PciAddress(self.address, pf)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/pci/devspec.py", line 67, in __init__
2016-05-20 02:37:30.100 TRACE nova.compute.manager
self._init_address_fields(pci_addr)
2016-05-20 02:37:30.100 TRACE nova.compute.manager File
"/opt/stack/nova/nova/pci/devspec.py", line 80, in _init_address_fields
2016-05-20 02:37:30.100 TRACE nova.compute.manager dbs, sep, func =
pci_addr.partition('.')
2016-05-20 02:37:30.100 TRACE nova.compute.manager AttributeError: 'dict'
object has no attribute 'partition'
** Affects: nova
Importance: Undecided
Status: New
--
SRIOV : AttributeError: 'dict' object has no attribute 'partition'
https://bugs.launchpad.net/bugs/1583915
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
--
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 1582298] Re: Django compressor cannot find custom theme templates
Reviewed: https://review.openstack.org/317051
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=4b870b12c139bda715c9d68e53daf80b51034d42
Submitter: Jenkins
Branch:master
commit 4b870b12c139bda715c9d68e53daf80b51034d42
Author: Diana Whitten
Date: Mon May 16 10:34:21 2016 -0700
Django compressor cannot find custom theme templates
An else condition was missed in the Theme Template loader. Some
templates that are loaded from a theme do start with '/', so
another elif was added to catching this possibility.
Closes-bug: #1582298
Change-Id: I74e147d5abdcb2ab12f1a0c8e7af7fc7f89aff1e
** 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/1582298
Title:
Django compressor cannot find custom theme templates
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
Looks like django compressor can't find templates files from custom
theme. When I try to run .manage.py compress I have the following
errors:
`Non-existent template at:
/home/paul/horizon/openstack_dashboard/themes/custom/templates/header/_header.html`
And Horizon can find that template because I see that overriden page
has been changed.
If I run it with material theme with followinf settings:
AVAILABLE_THEMES = [
('custom', 'Custom', 'themes/custom'),
('material', 'Material', 'themes/material')
]
DEFAULT_THEME = 'material'
I will get the following errors:
Non-existent template at:
/home/paul/horizon/openstack_dashboard/themes/material/templates/header/_header.html
Non-existent template at:
/home/paul/horizon/openstack_dashboard/themes/material/templates/auth/_splash.html
Non-existent template at:
/home/paul/horizon/openstack_dashboard/themes/material/templates/horizon/_sidebar.html
Non-existent template at:
/home/paul/horizon/openstack_dashboard/themes/material/templates/header/_brand.html
If I remove DEFAULT_THEME and AVAILABLE_THEMES consts, there is no
errors.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1582298/+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 1583900] [NEW] neutron-dynamic-routing setup.cfg missing "neutron-bgp-dragent"
Public bug reported: In previous patch, "neutron-bgp-dragent" is missing. ** Affects: neutron Importance: Undecided Status: Invalid ** Changed in: neutron Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1583900 Title: neutron-dynamic-routing setup.cfg missing "neutron-bgp-dragent" Status in neutron: Invalid Bug description: In previous patch, "neutron-bgp-dragent" is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583900/+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 1582668] Re: healthmonitor-id is not an optional argument for neutron lbaas-pool-create
I believe that this report has done in https://bugs.launchpad.net
/python-neutronclient/+bug/1582623
** 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/1582668
Title:
healthmonitor-id is not an optional argument for neutron lbaas-pool-
create
Status in neutron:
Invalid
Bug description:
It is in kilo branch.
From the help information of lbaas-pool-create, --healthmonitor-id is
an optional argument, but actually it is not allowed to use, so should
it be removed from the help information?
Details:
1.From the following help information, --healthmonitor-id is an optional
argument;
[root@opencos2 ~(keystone_admin)]# neutron lbaas-pool-create -h
usage: neutron lbaas-pool-create [-h] [-f {shell,table,value}] [-c COLUMN]
[--max-width ] [--prefix PREFIX]
[--request-format {json,xml}]
[--tenant-id TENANT_ID] [--admin-state-down]
[--description DESCRIPTION]
[--healthmonitor-id HEALTHMONITOR_ID]
[--session-persistence TYPE:VALUE]
--lb-algorithm
{ROUND_ROBIN,LEAST_CONNECTIONS,SOURCE_IP}
--listener LISTENER --protocol
{HTTP,HTTPS,TCP}
NAME
LBaaS v2 Create a pool.
positional arguments:
NAME The name of the pool.
optional arguments:
-h, --helpshow this help message and exit
--request-format {json,xml}
The XML or JSON request format.
--tenant-id TENANT_ID
The owner tenant ID.
--admin-state-downSet admin state up to false.
--description DESCRIPTION
Description of the pool.
--healthmonitor-id HEALTHMONITOR_ID
ID of the health monitor to use.
--session-persistence TYPE:VALUE
The type of session persistence to use.
--lb-algorithm {ROUND_ROBIN,LEAST_CONNECTIONS,SOURCE_IP}
The algorithm used to distribute load between the
members of the pool.
--listener LISTENER The listener to associate with the pool
--protocol {HTTP,HTTPS,TCP}
Protocol for balancing.
output formatters:
output formatter options
-f {shell,table,value}, --format {shell,table,value}
the output format, defaults to table
-c COLUMN, --column COLUMN
specify the column(s) to include, can be repeated
table formatter:
--max-width
Maximum display width, 0 to disable
shell formatter:
a format a UNIX shell can parse (variable="value")
--prefix PREFIX add a prefix to all variable names
2. If I add the --healthmonitor-id, lbaas-pool-create fails.
[root@opencos2 ~(keystone_admin)]# neutron lbaas-pool-create
--healthmonitor-id 3aeac49b-11a2-4d38-801a-33f5befa4c52 --lb-algorithm
ROUND_ROBIN --listener 981a81b5-6b33-4a9d-a683-f64bf9904eea --protocol HTTP
lbpool
Attribute 'healthmonitor_id' not allowed in POST
3. After removing the --healthmonitor-id, it creates successfully.
[root@opencos2 ~(keystone_admin)]# neutron lbaas-pool-create --lb-algorithm
ROUND_ROBIN --listener 981a81b5-6b33-4a9d-a683-f64bf9904eea --protocol HTTP
lbpool
Created a new pool:
+-++
| Field | Value |
+-++
| admin_state_up | True |
| description ||
| healthmonitor_id||
| id | a3582715-53af-42e2-8867-1f9608aafbea |
| lb_algorithm| ROUND_ROBIN|
| listeners | {"id": "981a81b5-6b33-4a9d-a683-f64bf9904eea"} |
| members ||
| name| lbpool |
| protocol| HTTP |
| session_persistence ||
| tenant_id | be58eaec789d44f296a65f96b944a9f5 |
+-++
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1582668/+subscriptions
--
Mailing list: htt
[Yahoo-eng-team] [Bug 1583700] Re: deprecate neutron-debug
Reviewed: https://review.openstack.org/318786 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1f4c82ce9ea0676c4e813cc34bdb8687f63452e3 Submitter: Jenkins Branch:master commit 1f4c82ce9ea0676c4e813cc34bdb8687f63452e3 Author: Armando Migliaccio Date: Thu May 19 10:04:40 2016 -0700 Deprecate neutron-debug We will not follow the typical deprecation cycle and thus we will not remove this in the release after the deprecation is advertised. Nonetheless we want to signal the need for a more comprehensive set of tools and APIs that will eventually make people want to move away from the limitations of neutron-debug. Closes-bug: #1583700 Change-Id: Ibe471f186b9b5c9c15c5857a35cbaca6b8d284d6 ** 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/1583700 Title: deprecate neutron-debug Status in neutron: Fix Released Bug description: Some context: http://lists.openstack.org/pipermail/openstack- dev/2016-May/095476.html https://review.openstack.org/#/c/318746/ https://review.openstack.org/#/c/314079/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583700/+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 1583870] [NEW] creating loadbalancer fails with AttributeError: 'HaproxyOnHostPluginDriver' object has no attribute 'load_balancer'
Public bug reported:
When I try to create loadbalancer using this command, I get error:
neutron lbaas-loadbalancer-create --name loadbalancer-1 a5e1fd8e-22c6
-40ad-88a4-a4a5cf0c68b9
neutron lbaas-loadbalancer-create --name loadbalancer-1
a5e1fd8e-22c6-40ad-88a4-a4a5cf0c68b9
Request Failed: internal server error while processing your request.
Neutron server returns request_ids: ['req-dae67e28-40d8-406e-8ccf-2cafb9abe59c']
and neutron server log indicates this traceback:
016-05-19 23:39:04.581 50 DEBUG neutron.api.v2.base
[req-b5741559-9982-4377-aa9c-30e1450c882a 7533552168244a7f9cf4dfd18aad60cf
a6d47b4364dd4cffa77075da7fca8080 - - -] Request body: {u'loadbalancer':
{u'vip_subnet_id': u'a5e1fd8e-22c6-40ad-88a4-a4a5cf0c68b9', u'name':
u'loadbalancer-1', u'admin_state_up': True}} prepare_request_body
/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/api/v2/base.py:658
2016-05-19 23:39:04.586 50 DEBUG neutron.db.quota.driver
[req-b5741559-9982-4377-aa9c-30e1450c882a 7533552168244a7f9cf4dfd18aad60cf
a6d47b4364dd4cffa77075da7fca8080 - - -] Resources
subnet,network,l7policy,subnetpool,listener,healthmonitor,port have unlimited
quota limit. It is not required to calculated headroom make_reservation
/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/db/quota/driver.py:191
2016-05-19 23:39:04.595 50 DEBUG neutron.db.quota.driver
[req-b5741559-9982-4377-aa9c-30e1450c882a 7533552168244a7f9cf4dfd18aad60cf
a6d47b4364dd4cffa77075da7fca8080 - - -] Attempting to reserve 1 items for
resource loadbalancer. Total usage: 0; quota limit: 10; headroom:10
make_reservation
/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/db/quota/driver.py:223
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource
[req-b5741559-9982-4377-aa9c-30e1450c882a 7533552168244a7f9cf4dfd18aad60cf
a6d47b4364dd4cffa77075da7fca8080 - - -] create failed
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource Traceback (most recent
call last):
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource File
"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/api/v2/resource.py",
line 84, in resource
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource result =
method(request=request, **args)
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource File
"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/api/v2/base.py", line
412, in create
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource return
self._create(request, body, **kwargs)
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource File
"/var/lib/kolla/venv/lib/python2.7/site-packages/oslo_db/api.py", line 148, in
wrapper
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource ectxt.value =
e.inner_exc
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource File
"/var/lib/kolla/venv/lib/python2.7/site-packages/oslo_utils/excutils.py", line
221, in __exit__
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource
self.force_reraise()
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource File
"/var/lib/kolla/venv/lib/python2.7/site-packages/oslo_utils/excutils.py", line
197, in force_reraise
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource
six.reraise(self.type_, self.value, self.tb)
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource File
"/var/lib/kolla/venv/lib/python2.7/site-packages/oslo_db/api.py", line 138, in
wrapper
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource return f(*args,
**kwargs)
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource File
"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/api/v2/base.py", line
523, in _create
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource obj =
do_create(body)
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource File
"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/api/v2/base.py", line
505, in do_create
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource request.context,
reservation.reservation_id)
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource File
"/var/lib/kolla/venv/lib/python2.7/site-packages/oslo_utils/excutils.py", line
221, in __exit__
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource
self.force_reraise()
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource File
"/var/lib/kolla/venv/lib/python2.7/site-packages/oslo_utils/excutils.py", line
197, in force_reraise
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource
six.reraise(self.type_, self.value, self.tb)
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource File
"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/api/v2/base.py", line
498, in do_create
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource return
obj_creator(request.context, **kwargs)
2016-05-19 23:39:04.613 50 ERROR neutron.api.v2.resource File
"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron_lbaas/services/loadbalancer/plugin.py",
line 575, in create_loadbala
[Yahoo-eng-team] [Bug 1583844] [NEW] pecan exception handler inconsistent with legacy exception handler
Public bug reported: the exception handler for pecan is missing logic for handling NotImplemented error, language translation, and error logging that is present in the legacy framework, which results in inconsistent error results for the user depending on the API used. ** Affects: neutron Importance: Undecided Assignee: Kevin Benton (kevinbenton) Status: New ** Changed in: neutron Assignee: (unassigned) => Kevin Benton (kevinbenton) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1583844 Title: pecan exception handler inconsistent with legacy exception handler Status in neutron: New Bug description: the exception handler for pecan is missing logic for handling NotImplemented error, language translation, and error logging that is present in the legacy framework, which results in inconsistent error results for the user depending on the API used. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583844/+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 1583841] Re: cc_chef fails when using 'gems' installer because Ubuntu 16.04 no longer includes Ruby 1.8
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1583841
Title:
cc_chef fails when using 'gems' installer because Ubuntu 16.04 no
longer includes Ruby 1.8
Status in cloud-init:
New
Status in cloud-init package in Ubuntu:
New
Bug description:
Ubuntu 16.04
# dpkg -l | grep cloud-init
ii cloud-init 0.7.7~bzr1212-0ubuntu1 all
Init scripts for cloud instances
ii cloud-initramfs-copymods 0.27ubuntu1 all
copy initramfs modules into root filesystem for later use
ii cloud-initramfs-dyn-netconf 0.27ubuntu1 all
write a network interface file in /run for BOOTIF
Minimum Ruby version supported in Ubuntu 16.04 is Ruby 2.3.
Syslog output:
May 19 23:41:38 ubuntu [CLOUDINIT] util.py[DEBUG]: apt-update [eatmydata
apt-get --option=Dpkg::Options::=--force-confold
--option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet update] took
20.50
1 seconds
May 19 23:41:38 ubuntu [CLOUDINIT] util.py[DEBUG]: Running command
['eatmydata', 'apt-get', '--option=Dpkg::Options::=--force-confold',
'--option=Dpkg::options::=--force-unsafe-io', '--assume-yes', '--qui
et', 'install', 'ruby1.8', 'ruby1.8-dev', 'libopenssl-ruby1.8',
'rubygems1.8'] with allowed return codes [0] (shell=False, capture=False)
May 19 23:41:39 ubuntu [CLOUDINIT] util.py[DEBUG]: apt-install [eatmydata
apt-get --option=Dpkg::Options::=--force-confold
--option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install ruby1.8
r
uby1.8-dev libopenssl-ruby1.8 rubygems1.8] took 0.295 seconds
May 19 23:41:39 ubuntu [CLOUDINIT] handlers.py[DEBUG]: finish:
modules-config/config-chef: FAIL: running config-chef with frequency
once-per-instance
May 19 23:41:39 ubuntu [CLOUDINIT] util.py[WARNING]: Running module chef
() failed
May 19 23:41:39 ubuntu [CLOUDINIT] util.py[DEBUG]: Running module chef
()
failed#012Traceback (most rec
ent call last):#012 File
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 739, in
_run_modules#012freq=freq)#012 File
"/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 70, in run#0
12return self._runners.run(name, functor, args, freq, clear_on_fail)#012
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 199, in
run#012results = functor(*args)#012 File "/usr/l
ib/python3/dist-packages/cloudinit/config/cc_chef.py", line 257, in
handle#012run = install_chef(cloud, chef_cfg, log)#012 File
"/usr/lib/python3/dist-packages/cloudinit/config/cc_chef.py", line 296,
in install_chef#012install_chef_from_gems(ruby_version, chef_version,
cloud.distro)#012 File
"/usr/lib/python3/dist-packages/cloudinit/config/cc_chef.py", line 330, in
install_chef_from_gems#012
distro.install_packages(get_ruby_packages(ruby_version))#012 File
"/usr/lib/python3/dist-packages/cloudinit/distros/debian.py", line 75, in
install_packages#012self.package_command('install', pkgs=pk
glist)#012 File
"/usr/lib/python3/dist-packages/cloudinit/distros/debian.py", line 176, in
package_command#012args=(cmd,), kwargs={'env': e, 'capture': False})#012
File "/usr/lib/python3/dist-packag
es/cloudinit/util.py", line 2040, in log_time#012ret = func(*args,
**kwargs)#012 File "/usr/lib/python3/dist-packages/cloudinit/util.py", line
1704, in subp#012cmd=args)#012cloudinit.util.Process
ExecutionError: Unexpected error while running command.#012Command:
['eatmydata', 'apt-get', '--option=Dpkg::Options::=--force-confold',
'--option=Dpkg::options::=--force-unsafe-io', '--assume-yes', '--qu
iet', 'install', 'ruby1.8', 'ruby1.8-dev', 'libopenssl-ruby1.8',
'rubygems1.8']#012Exit code: 100#012Reason: -#012Stdout: ''#012Stderr: ''
# apt-cache policy ruby
ruby:
Installed: (none)
Candidate: 1:2.3.0+1
Version table:
1:2.3.0+1 500
500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu xenial/main amd64
Packages
# apt-cache search ^ruby
rake - ruby make-like utility
ruby - Interpreter of object-oriented scripting language Ruby (default
version)
ruby-all-dev - Ruby development environment (all versions supported in Debian)
ruby-dev - Header files for compiling extension modules for Ruby (default
version)
ruby-did-you-mean - smart error messages for Ruby > 2.3
ruby-minitest - Ruby test tools supporting TDD, BDD, mocking, and benchmarking
ruby-net-telnet - telnet client library
ruby-power-assert - library showing values of variables and method calls in
an expression
ruby-rrd - time-series data storage and display system (Ruby interfaces)
ruby-test-unit - unit testing framework for Ruby
ruby2.3 - Interpreter of object-oriented scripting language Ruby
ruby2.3-dev - Header files for
[Yahoo-eng-team] [Bug 1583837] Re: cc_chef fails when using omnibus installer because UrlResponse doesn't have an 'encode' method
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags added: omnibus -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1583837 Title: cc_chef fails when using omnibus installer because UrlResponse doesn't have an 'encode' method Status in cloud-init: New Status in cloud-init package in Ubuntu: New Bug description: Ubuntu 16.04 # dpkg -l | grep cloud-init ii cloud-init 0.7.7~bzr1212-0ubuntu1 all Init scripts for cloud instances ii cloud-initramfs-copymods 0.27ubuntu1 all copy initramfs modules into root filesystem for later use ii cloud-initramfs-dyn-netconf 0.27ubuntu1 all write a network interface file in /run for BOOTIF util.write_file is trying to UTF-8 encode the text before writing, but UrlResponse doesn't have an "encode" method. Trace from syslog: May 19 23:27:09 ubuntu [CLOUDINIT] util.py[DEBUG]: Running module chef () failed#012Traceback (most rec ent call last):#012 File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 739, in _run_modules#012freq=freq)#012 File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 70, in run#0 12return self._runners.run(name, functor, args, freq, clear_on_fail)#012 File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 199, in run#012results = functor(*args)#012 File "/usr/l ib/python3/dist-packages/cloudinit/config/cc_chef.py", line 257, in handle#012run = install_chef(cloud, chef_cfg, log)#012 File "/usr/lib/python3/dist-packages/cloudinit/config/cc_chef.py", line 313, in install_chef#012util.write_file(tmpf, content, mode=0o700)#012 File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1643, in write_file#012content = encode_text(content)#012 File "/ usr/lib/python3/dist-packages/cloudinit/util.py", line 97, in encode_text#012 return text.encode(encoding)#012AttributeError: 'UrlResponse' object has no attribute 'encode' To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1583837/+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 1583069] Re: neutron.tests.unit.agent.ovsdb.native.test_connection raises exception in different thread
Reviewed: https://review.openstack.org/317929 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=99f2224e6b0ceeff952d8eca615baf5326bb498a Submitter: Jenkins Branch:master commit 99f2224e6b0ceeff952d8eca615baf5326bb498a Author: Jakub Libosvar Date: Wed May 18 09:36:13 2016 + Mock out poller in ovsdb unittests The second thread running in ovsdb connection crashed due to not passing file descriptor to poller. This patch mocks out the poller as it's not used in the tests to avoid false tracebacks in the logs. Change-Id: I62e87e3248d176e5db7fe57bfb4467176ba05392 Closes-Bug: 1583069 ** 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/1583069 Title: neutron.tests.unit.agent.ovsdb.native.test_connection raises exception in different thread Status in neutron: Fix Released Bug description: neutron.tests.unit.agent.ovsdb.native.test_connection raises following exception due to mock object passed to poll() function. Exception in thread Thread-1: Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 804, in __bootstrap_inner self.run() File "/usr/lib64/python2.7/threading.py", line 757, in run self.__target(*self.__args, **self.__kwargs) File "neutron/agent/ovsdb/native/connection.py", line 110, in safe_run self.run() File "neutron/agent/ovsdb/native/connection.py", line 122, in run self.poller.fd_wait(self.txns.alert_fileno, poller.POLLIN) File "/usr/lib/python2.7/site-packages/ovs/poller.py", line 122, in fd_wait self.poll.register(fd, events) File "/usr/lib/python2.7/site-packages/ovs/poller.py", line 55, in register assert isinstance(fd, int) AssertionError To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583069/+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 1583841] [NEW] cc_chef fails when using 'gems' installer because Ubuntu 16.04 no longer includes Ruby 1.8
Public bug reported:
Ubuntu 16.04
# dpkg -l | grep cloud-init
ii cloud-init 0.7.7~bzr1212-0ubuntu1 all
Init scripts for cloud instances
ii cloud-initramfs-copymods 0.27ubuntu1 all
copy initramfs modules into root filesystem for later use
ii cloud-initramfs-dyn-netconf 0.27ubuntu1 all
write a network interface file in /run for BOOTIF
Minimum Ruby version supported in Ubuntu 16.04 is Ruby 2.3.
Syslog output:
May 19 23:41:38 ubuntu [CLOUDINIT] util.py[DEBUG]: apt-update [eatmydata
apt-get --option=Dpkg::Options::=--force-confold
--option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet update] took
20.50
1 seconds
May 19 23:41:38 ubuntu [CLOUDINIT] util.py[DEBUG]: Running command
['eatmydata', 'apt-get', '--option=Dpkg::Options::=--force-confold',
'--option=Dpkg::options::=--force-unsafe-io', '--assume-yes', '--qui
et', 'install', 'ruby1.8', 'ruby1.8-dev', 'libopenssl-ruby1.8', 'rubygems1.8']
with allowed return codes [0] (shell=False, capture=False)
May 19 23:41:39 ubuntu [CLOUDINIT] util.py[DEBUG]: apt-install [eatmydata
apt-get --option=Dpkg::Options::=--force-confold
--option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install ruby1.8
r
uby1.8-dev libopenssl-ruby1.8 rubygems1.8] took 0.295 seconds
May 19 23:41:39 ubuntu [CLOUDINIT] handlers.py[DEBUG]: finish:
modules-config/config-chef: FAIL: running config-chef with frequency
once-per-instance
May 19 23:41:39 ubuntu [CLOUDINIT] util.py[WARNING]: Running module chef
() failed
May 19 23:41:39 ubuntu [CLOUDINIT] util.py[DEBUG]: Running module chef ()
failed#012Traceback (most rec
ent call last):#012 File "/usr/lib/python3/dist-packages/cloudinit/stages.py",
line 739, in _run_modules#012freq=freq)#012 File
"/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 70, in run#0
12return self._runners.run(name, functor, args, freq, clear_on_fail)#012
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 199, in
run#012results = functor(*args)#012 File "/usr/l
ib/python3/dist-packages/cloudinit/config/cc_chef.py", line 257, in handle#012
run = install_chef(cloud, chef_cfg, log)#012 File
"/usr/lib/python3/dist-packages/cloudinit/config/cc_chef.py", line 296,
in install_chef#012install_chef_from_gems(ruby_version, chef_version,
cloud.distro)#012 File
"/usr/lib/python3/dist-packages/cloudinit/config/cc_chef.py", line 330, in
install_chef_from_gems#012
distro.install_packages(get_ruby_packages(ruby_version))#012 File
"/usr/lib/python3/dist-packages/cloudinit/distros/debian.py", line 75, in
install_packages#012self.package_command('install', pkgs=pk
glist)#012 File "/usr/lib/python3/dist-packages/cloudinit/distros/debian.py",
line 176, in package_command#012args=(cmd,), kwargs={'env': e, 'capture':
False})#012 File "/usr/lib/python3/dist-packag
es/cloudinit/util.py", line 2040, in log_time#012ret = func(*args,
**kwargs)#012 File "/usr/lib/python3/dist-packages/cloudinit/util.py", line
1704, in subp#012cmd=args)#012cloudinit.util.Process
ExecutionError: Unexpected error while running command.#012Command:
['eatmydata', 'apt-get', '--option=Dpkg::Options::=--force-confold',
'--option=Dpkg::options::=--force-unsafe-io', '--assume-yes', '--qu
iet', 'install', 'ruby1.8', 'ruby1.8-dev', 'libopenssl-ruby1.8',
'rubygems1.8']#012Exit code: 100#012Reason: -#012Stdout: ''#012Stderr: ''
# apt-cache policy ruby
ruby:
Installed: (none)
Candidate: 1:2.3.0+1
Version table:
1:2.3.0+1 500
500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu xenial/main amd64
Packages
# apt-cache search ^ruby
rake - ruby make-like utility
ruby - Interpreter of object-oriented scripting language Ruby (default version)
ruby-all-dev - Ruby development environment (all versions supported in Debian)
ruby-dev - Header files for compiling extension modules for Ruby (default
version)
ruby-did-you-mean - smart error messages for Ruby > 2.3
ruby-minitest - Ruby test tools supporting TDD, BDD, mocking, and benchmarking
ruby-net-telnet - telnet client library
ruby-power-assert - library showing values of variables and method calls in an
expression
ruby-rrd - time-series data storage and display system (Ruby interfaces)
ruby-test-unit - unit testing framework for Ruby
ruby2.3 - Interpreter of object-oriented scripting language Ruby
ruby2.3-dev - Header files for compiling extension modules for the Ruby 2.3
ruby2.3-doc - Documentation for Ruby 2.3
** Affects: cloud-init
Importance: Undecided
Status: New
** Tags: chef ruby
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1583841
Title:
cc_chef fails when using 'gems' installer because Ubuntu 16.04 no
longer includes Ruby 1.8
Status in cloud-init:
New
Bug description:
Ubuntu 16.04
# d
[Yahoo-eng-team] [Bug 1372441] Re: [RFE] Creating port in dual-stack network requires IPv4 and IPv6 addresses to be allocated
The consensus is that Neutron has enough existing primitives to address user's expectations when dealing with dualstack environments. The situation that prompted this RFE where address exhaustion on one subnet may lead to a user facing error may be prevented by being explicit on what subnet to allocate from. This is inline with comment #13, therefore there's really no more room for confusion. ** Changed in: neutron Status: Triaged => Won't Fix ** Changed in: neutron Milestone: newton-1 => None ** Changed in: neutron Assignee: Sean M. Collins (scollins) => (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/1372441 Title: [RFE] Creating port in dual-stack network requires IPv4 and IPv6 addresses to be allocated Status in neutron: Won't Fix Bug description: Currently, when creating port in dual-stack network (network with one ore more IPv4 subnets and one or more IPv6 subnets), Neutron allocates fixed-ip from both, v4 and v6 subnets. If one of the subnets do not have available addresses, it is considered as error. IMO, this is wrong. Operation should succeed if at least one address (IPv4 of IPv6) was allocated. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1372441/+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 1583837] [NEW] cc_chef fails when using omnibus installer because UrlResponse doesn't have an 'encode' method
Public bug reported: Ubuntu 16.04 # dpkg -l | grep cloud-init ii cloud-init 0.7.7~bzr1212-0ubuntu1 all Init scripts for cloud instances ii cloud-initramfs-copymods 0.27ubuntu1 all copy initramfs modules into root filesystem for later use ii cloud-initramfs-dyn-netconf 0.27ubuntu1 all write a network interface file in /run for BOOTIF util.write_file is trying to UTF-8 encode the text before writing, but UrlResponse doesn't have an "encode" method. Trace from syslog: May 19 23:27:09 ubuntu [CLOUDINIT] util.py[DEBUG]: Running module chef () failed#012Traceback (most rec ent call last):#012 File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 739, in _run_modules#012freq=freq)#012 File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 70, in run#0 12return self._runners.run(name, functor, args, freq, clear_on_fail)#012 File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 199, in run#012results = functor(*args)#012 File "/usr/l ib/python3/dist-packages/cloudinit/config/cc_chef.py", line 257, in handle#012 run = install_chef(cloud, chef_cfg, log)#012 File "/usr/lib/python3/dist-packages/cloudinit/config/cc_chef.py", line 313, in install_chef#012util.write_file(tmpf, content, mode=0o700)#012 File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1643, in write_file#012content = encode_text(content)#012 File "/ usr/lib/python3/dist-packages/cloudinit/util.py", line 97, in encode_text#012 return text.encode(encoding)#012AttributeError: 'UrlResponse' object has no attribute 'encode' ** Affects: cloud-init Importance: Undecided Status: New ** Tags: chef -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1583837 Title: cc_chef fails when using omnibus installer because UrlResponse doesn't have an 'encode' method Status in cloud-init: New Bug description: Ubuntu 16.04 # dpkg -l | grep cloud-init ii cloud-init 0.7.7~bzr1212-0ubuntu1 all Init scripts for cloud instances ii cloud-initramfs-copymods 0.27ubuntu1 all copy initramfs modules into root filesystem for later use ii cloud-initramfs-dyn-netconf 0.27ubuntu1 all write a network interface file in /run for BOOTIF util.write_file is trying to UTF-8 encode the text before writing, but UrlResponse doesn't have an "encode" method. Trace from syslog: May 19 23:27:09 ubuntu [CLOUDINIT] util.py[DEBUG]: Running module chef () failed#012Traceback (most rec ent call last):#012 File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 739, in _run_modules#012freq=freq)#012 File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 70, in run#0 12return self._runners.run(name, functor, args, freq, clear_on_fail)#012 File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 199, in run#012results = functor(*args)#012 File "/usr/l ib/python3/dist-packages/cloudinit/config/cc_chef.py", line 257, in handle#012run = install_chef(cloud, chef_cfg, log)#012 File "/usr/lib/python3/dist-packages/cloudinit/config/cc_chef.py", line 313, in install_chef#012util.write_file(tmpf, content, mode=0o700)#012 File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1643, in write_file#012content = encode_text(content)#012 File "/ usr/lib/python3/dist-packages/cloudinit/util.py", line 97, in encode_text#012 return text.encode(encoding)#012AttributeError: 'UrlResponse' object has no attribute 'encode' To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1583837/+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 1583835] [NEW] dhcp api method get_active_networks is unused
Public bug reported: This method was originally left for backwards compatibility during an upgrade of neutron. It stopped being used in havana so I think it should be safe to remove now. ** Affects: neutron Importance: Undecided Assignee: Aaron Rosen (arosen) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Aaron Rosen (arosen) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1583835 Title: dhcp api method get_active_networks is unused Status in neutron: In Progress Bug description: This method was originally left for backwards compatibility during an upgrade of neutron. It stopped being used in havana so I think it should be safe to remove now. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583835/+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 1576054] Re: [lbaasv2] listener and member can be created with protocol_port 0
Reviewed: https://review.openstack.org/311631 Committed: https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=4b6858902faefba5c0aa7abbacb7978a2e9a0801 Submitter: Jenkins Branch:master commit 4b6858902faefba5c0aa7abbacb7978a2e9a0801 Author: Joseph Bajin Date: Sun May 1 13:26:08 2016 -0400 Updated port validation to not allow port 0 The default port validation allowed ports 0-65535 to be created on members and listeners. Port 0 is not a valid port 0 to listen on. Modified the extenstions for both v1 and v2 loadbalancer to validate starting at port 1 and not port 0. Change-Id: I204e0032d0fa59776b3a5bc6be03a23991a5aeeb Closes-Bug: #1576054 ** 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/1576054 Title: [lbaasv2] listener and member can be created with protocol_port 0 Status in neutron: Fix Released Bug description: protocol_port 0 is reserved.But in lbaasv2,users can create listener or member with protocol_port 0. For example: Created a new member: ++--+ | Field | Value| ++--+ | address| 1.1.1.2 | | admin_state_up | True | | id | 72eab0e7-f51f-4927-aaf3-71177a0ed34a | | protocol_port | 0| | subnet_id | 1b86ca37-738c-4ada-8026-cf65acd20a27 | | tenant_id | be58eaec789d44f296a65f96b944a9f5 | | weight | 1| ++--+ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1576054/+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 1577913] Re: [RFE] On-demand segment and subnet allocation
@Han Zhou: Neutron's core provides enough pluggable points to allow you to go and manage your physical infrastructure to support the provisioning of logical networking. I don't expect us to have the ability abstract all possible DC infrastructures and turn Neutron into a full blown Data Center Management platform, but you're welcome to use the extension mechanisms that exist today to accomplish what you have in mind. Those plugins you are referring to are not part of Neutron today, and I don't believe your proposal needs to be in order to be useful. ** Changed in: neutron Status: Confirmed => 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/1577913 Title: [RFE] On-demand segment and subnet allocation Status in neutron: Won't Fix Bug description: While routed networks [1] provides us the capability of managing L2 segments and related subnets with a view of L3 network, it assumes that the related infrastructure resources are always provisioned (vlans, host-segment bindings, subnets) beforehand and is not managed by neutron. However, in a large deployment cloud, there are use cases for on-demand resource provisioning. - On-demand segment provisioning: A host can be multi-tenancy, so when a host is provisioned, it may be unknown which tenant's VMs will be scheduled to the host, so some segments may not be needed for the host. On the other hand, new tenant can be added later on. So, it will be good if we can dynamically create the segment (i.e. create the vlan on the ToR) when the first VM of the tenant is scheduled under the ToR, then we don't need to pre- allocate all the possible vlans and create segments for all the ToRs. The information that is known during host onboarding is the ToR that the host is located. We can model this as a BridgeGroup object (a group of vlans/l2 segments spanning across the same set of hosts, which are usually connected to a group of network devices, and the number of devices is usually 1, e.g. the ToR connecting the hosts under a rack), and BridgeGroup-Host mapping. And when the first neutron port is requested to be created on a routed network for a host under a BridgeGroup, a new segment is created within the BridgeGroup and bound to the host. (Not sure if BridgeGroup is a good name here, maybe we can call it Physnet) - On-demand subnet provisioning: In a shared infrastructure the workload location is flexible, so it is hard to predict the number of IPs required for a segment. To use IP resource (especially IPv4) efficiently, it will be good to be able to dynamically allocate subnets to a segment only when it is needed, i.e. when there are workloads scheduled to the segment. This feature request requires [1] but put additional requirements on top of it. [1] https://review.openstack.org/#/c/225384/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1577913/+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 1583790] [NEW] Soft reboot fails for an instance that is shut down
Public bug reported: Steps to reproduce 1. Login as admin or non admin user. 2. Spin up a new instance if none are available. 3. Shut down instance. 4. Soft reboot instance. Operation fails Expected behavior: Soft reboot should not be an available option for an instance that has been shut down. Openstack CLI does not allow soft reboot of an instance that has been shutdown. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1583790 Title: Soft reboot fails for an instance that is shut down Status in OpenStack Dashboard (Horizon): New Bug description: Steps to reproduce 1. Login as admin or non admin user. 2. Spin up a new instance if none are available. 3. Shut down instance. 4. Soft reboot instance. Operation fails Expected behavior: Soft reboot should not be an available option for an instance that has been shut down. Openstack CLI does not allow soft reboot of an instance that has been shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1583790/+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 1583769] [NEW] DHCP agent still refers to deprecated dhcp_domain
Public bug reported: DESCRIPTION: VMs were coming up with a hostname configured as "vm_name.openstacklocal" despite having configured a dns_domain in neutron.conf. However, the DHCP host file had the correct entry with the domain, "vm_name.testdomain.net". Also, ping connectivity worked using just DNS name, and with testdomain.net Agent was using dhcp_domain (a deprecated field), when spawning dnsmasq process with a "--domain" argument. If dhcp_domain is never set in the dhcp_agent.ini file, it picks up the default value openstacklocal. The reason the DHCP hosts file is correct, is because it is sent as the dns_assignment field in the neutron port. Neutron server correctly uses the newer dns_domain, and the port's dns_name/assignment is not used in spawning dnsmasq. Setting dhcp_domain in dhcp_agent.ini fixed issue locally. But since this field has been deprecated since liberty, all references to dhcp_domain should be changed to dns_domain. I have fixed this locally on my deployment which uses liberty, will apply fix to master and send out for a review Pre-conditions: - Have the neutron and nova side changes for setting dns_name and dns_assignment on the port (present in master) - Set the dns_domain in neutron.conf Reproduction Steps: Create a VM like normal. Port it gets attached to should have dns_name set according to instance_name, and dns_assignment should have correct hostname and domain. Verify DHCP host file on network node has correct entry. Then login to VM, and do "hostname -f". Verify it displays with a .openstacklocal Version: Tested and discovered on Liberty, Centos 7.1 hosts and Centos 7.1 VMs. Upon code inspection, bug also exists in master (neutron/agent/linux/dhcp.py has a few references to conf.dhcp_domain) ** Affects: neutron Importance: Undecided Assignee: xagent (xagent-9) Status: In Progress ** Tags: dns ** Changed in: neutron Status: New => In Progress ** Changed in: neutron Assignee: (unassigned) => xagent (xagent-9) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1583769 Title: DHCP agent still refers to deprecated dhcp_domain Status in neutron: In Progress Bug description: DESCRIPTION: VMs were coming up with a hostname configured as "vm_name.openstacklocal" despite having configured a dns_domain in neutron.conf. However, the DHCP host file had the correct entry with the domain, "vm_name.testdomain.net". Also, ping connectivity worked using just DNS name, and with testdomain.net Agent was using dhcp_domain (a deprecated field), when spawning dnsmasq process with a "--domain" argument. If dhcp_domain is never set in the dhcp_agent.ini file, it picks up the default value openstacklocal. The reason the DHCP hosts file is correct, is because it is sent as the dns_assignment field in the neutron port. Neutron server correctly uses the newer dns_domain, and the port's dns_name/assignment is not used in spawning dnsmasq. Setting dhcp_domain in dhcp_agent.ini fixed issue locally. But since this field has been deprecated since liberty, all references to dhcp_domain should be changed to dns_domain. I have fixed this locally on my deployment which uses liberty, will apply fix to master and send out for a review Pre-conditions: - Have the neutron and nova side changes for setting dns_name and dns_assignment on the port (present in master) - Set the dns_domain in neutron.conf Reproduction Steps: Create a VM like normal. Port it gets attached to should have dns_name set according to instance_name, and dns_assignment should have correct hostname and domain. Verify DHCP host file on network node has correct entry. Then login to VM, and do "hostname -f". Verify it displays with a .openstacklocal Version: Tested and discovered on Liberty, Centos 7.1 hosts and Centos 7.1 VMs. Upon code inspection, bug also exists in master (neutron/agent/linux/dhcp.py has a few references to conf.dhcp_domain) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583769/+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 1583763] [NEW] neutron.tests.functional.agent.linux.test_ovsdb_monitor.TestSimpleInterfaceMonitor.test_get_events reads output sometimes too early
Public bug reported: The test expects that stdout buffers are populated right after ovsdb- monitor async process is spawned. Sometimes get_events() is called before ovsdb output is read that causes following failure: http://logs.openstack.org/15/316615/1/check/gate-neutron-dsvm- functional/c3be6f8/testr_results.html.gz ** Affects: neutron Importance: Undecided Assignee: Jakub Libosvar (libosvar) Status: 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/1583763 Title: neutron.tests.functional.agent.linux.test_ovsdb_monitor.TestSimpleInterfaceMonitor.test_get_events reads output sometimes too early Status in neutron: In Progress Bug description: The test expects that stdout buffers are populated right after ovsdb- monitor async process is spawned. Sometimes get_events() is called before ovsdb output is read that causes following failure: http://logs.openstack.org/15/316615/1/check/gate-neutron-dsvm- functional/c3be6f8/testr_results.html.gz To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583763/+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 1583759] [NEW] Invalid input for operation: IP allocation requires subnets for network
Public bug reported: Several people now, including Brian Haley and me, have been chasing down this stack trace [1] for a few weeks. We've seen it in failed jobs and we begin chasing it down only to find out that it is a red herring. I'm filing this bug because we ought to capture what we know about it, figure out if it is correlated with any failures, and hopefully eliminate the trace so that no longer distracts us from other problems. I was poking through the stack trace in github. Since I had the links handy, I thought I'd include them here [2-11]. Also, this logstash query might be helpful [12]. [1] http://paste.openstack.org/show/497738/ [2] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/api/rpc/handlers/dhcp_rpc.py#L211 [3] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/api/rpc/handlers/dhcp_rpc.py#L93 [4] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/plugins/common/utils.py#L162 [5] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/plugins/ml2/plugin.py#L1137 [6] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/plugins/ml2/plugin.py#L1106 [7] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/db/db_base_plugin_v2.py#L1247 [8] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/db/ipam_non_pluggable_backend.py#L204 [9] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/db/ipam_non_pluggable_backend.py#L362 [10] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/db/ipam_non_pluggable_backend.py#L245 [11] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/db/ipam_backend_mixin.py#L335-L337 [12] http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%20%5C%22InvalidInput%3A%20Invalid%20input%20for%20operation%3A%20IP%20allocation%20requires%20subnets%20for%20network%5C%22 ** Affects: neutron Importance: Medium Status: New ** Tags: l3-ipam-dhcp ** Changed in: neutron Importance: Undecided => Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1583759 Title: Invalid input for operation: IP allocation requires subnets for network Status in neutron: New Bug description: Several people now, including Brian Haley and me, have been chasing down this stack trace [1] for a few weeks. We've seen it in failed jobs and we begin chasing it down only to find out that it is a red herring. I'm filing this bug because we ought to capture what we know about it, figure out if it is correlated with any failures, and hopefully eliminate the trace so that no longer distracts us from other problems. I was poking through the stack trace in github. Since I had the links handy, I thought I'd include them here [2-11]. Also, this logstash query might be helpful [12]. [1] http://paste.openstack.org/show/497738/ [2] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/api/rpc/handlers/dhcp_rpc.py#L211 [3] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/api/rpc/handlers/dhcp_rpc.py#L93 [4] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/plugins/common/utils.py#L162 [5] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/plugins/ml2/plugin.py#L1137 [6] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/plugins/ml2/plugin.py#L1106 [7] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/db/db_base_plugin_v2.py#L1247 [8] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/db/ipam_non_pluggable_backend.py#L204 [9] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/db/ipam_non_pluggable_backend.py#L362 [10] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/db/ipam_non_pluggable_backend.py#L245 [11] https://github.com/openstack/neutron/blob/79c1d7efc1/neutron/db/ipam_backend_mixin.py#L335-L337 [12] http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%20%5C%22InvalidInput%3A%20Invalid%20input%20for%20operation%3A%20IP%20allocation%20requires%20subnets%20for%20network%5C%22 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583759/+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 1583757] [NEW] multiline blocktrans in django templates should use 'trimmed' option
Public bug reported:
Django templates support 'trimmed' option [1]. remove newline characters
from the beginning and the end of the content of the {% blocktrans %}
tag, replace any whitespace at the beginning and end of a line and merge
all lines into one using a space character to separate them.
Without 'trimmed' option, translators will get source strings with
meaningless newlines and whitespaces like below. Zanata (translation
check site) checks the number of newlines, so translators need to insert
newlines to silent Zanata validations. It is really annoying and
meaningless.
#:
openstack_dashboard/dashboards/admin/volumes/templates/volumes/snapshots/_update_status.html:10
msgid ""
"\n"
"The status of a volume snapshot is normally managed automatically. "
"In some circumstances\n"
"an administrator may need to explicitly update the status value. This"
" is equivalent to\n"
"the cinder snapshot-reset-state command.\n"
""
msgstr ""
By using 'trimmed' option in Django templates, we can get rid of meaningless
newlines in extracted message strings.
The recent released version of django-bebal supports 'trimmed' option [2] and
now we can move the situation forward.
[1]
https://docs.djangoproject.com/ja/1.9/topics/i18n/translation/#blocktrans-template-tag
[2]
https://github.com/python-babel/django-babel/commit/88b389381c0e269605311ae07029555b65a86bc5
** Affects: horizon
Importance: Medium
Assignee: Akihiro Motoki (amotoki)
Status: New
** Tags: i18n
--
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/1583757
Title:
multiline blocktrans in django templates should use 'trimmed' option
Status in OpenStack Dashboard (Horizon):
New
Bug description:
Django templates support 'trimmed' option [1]. remove newline
characters from the beginning and the end of the content of the {%
blocktrans %} tag, replace any whitespace at the beginning and end of
a line and merge all lines into one using a space character to
separate them.
Without 'trimmed' option, translators will get source strings with
meaningless newlines and whitespaces like below. Zanata (translation
check site) checks the number of newlines, so translators need to
insert newlines to silent Zanata validations. It is really annoying
and meaningless.
#:
openstack_dashboard/dashboards/admin/volumes/templates/volumes/snapshots/_update_status.html:10
msgid ""
"\n"
"The status of a volume snapshot is normally managed automatically. "
"In some circumstances\n"
"an administrator may need to explicitly update the status value. This"
" is equivalent to\n"
"the cinder snapshot-reset-state command.\n"
""
msgstr ""
By using 'trimmed' option in Django templates, we can get rid of meaningless
newlines in extracted message strings.
The recent released version of django-bebal supports 'trimmed' option [2] and
now we can move the situation forward.
[1]
https://docs.djangoproject.com/ja/1.9/topics/i18n/translation/#blocktrans-template-tag
[2]
https://github.com/python-babel/django-babel/commit/88b389381c0e269605311ae07029555b65a86bc5
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1583757/+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 1583754] [NEW] Style: Default Theme: Should Support Dropup Menus
Public bug reported: Bootstrap supports dropup menus in addition to dropdown menus, seen here: http://getbootstrap.com/components/#dropdowns Right now, our little dropdown arrow only works for drop'down' menus. ** Affects: horizon Importance: Wishlist Assignee: Diana Whitten (hurgleburgler) Status: In Progress ** Tags: branding themes -- 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/1583754 Title: Style: Default Theme: Should Support Dropup Menus Status in OpenStack Dashboard (Horizon): In Progress Bug description: Bootstrap supports dropup menus in addition to dropdown menus, seen here: http://getbootstrap.com/components/#dropdowns Right now, our little dropdown arrow only works for drop'down' menus. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1583754/+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 1583739] [NEW] dns_name was reset, when delete VM or detach-interface
Public bug reported: When delete VM ,or detach port. the dns_name of port should be retained ,when it was assigned by the user At this fix: https://bugs.launchpad.net/nova/mitaka/+bug/1572593. reset dns_name directly. ** 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/1583739 Title: dns_name was reset,when delete VM or detach-interface Status in neutron: New Bug description: When delete VM ,or detach port. the dns_name of port should be retained ,when it was assigned by the user At this fix: https://bugs.launchpad.net/nova/mitaka/+bug/1572593. reset dns_name directly. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583739/+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 1583720] [NEW] "Migration instance not found" is logged repeatedly to nova-compute.log after an instance was deleted
Public bug reported: After migrating an instance and then deleting the instance, a migration record of status "completed" is not filtered from a query of in-progress migrations. This causes the following to be logged periodically forever: 2016-04-24 21:19:39.652 24323 DEBUG nova.compute.resource_tracker [req-...] Migration instance not found: Instance 585ac641-... could not be found. ** Affects: nova Importance: Undecided Assignee: Dan Smith (danms) Status: In Progress ** Tags: mitaka-backport-potential -- 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/1583720 Title: "Migration instance not found" is logged repeatedly to nova- compute.log after an instance was deleted Status in OpenStack Compute (nova): In Progress Bug description: After migrating an instance and then deleting the instance, a migration record of status "completed" is not filtered from a query of in-progress migrations. This causes the following to be logged periodically forever: 2016-04-24 21:19:39.652 24323 DEBUG nova.compute.resource_tracker [req-...] Migration instance not found: Instance 585ac641-... could not be found. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1583720/+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 1583700] [NEW] deprecate neutron-debug
Public bug reported: Some context: http://lists.openstack.org/pipermail/openstack-dev/2016-May/095476.html https://review.openstack.org/#/c/318746/ https://review.openstack.org/#/c/314079/ ** Affects: neutron Importance: Wishlist Status: Confirmed ** Tags: deprecation ** Tags added: deprecation ** Changed in: neutron Importance: Undecided => Wishlist ** Changed in: neutron Status: New => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1583700 Title: deprecate neutron-debug Status in neutron: Confirmed Bug description: Some context: http://lists.openstack.org/pipermail/openstack- dev/2016-May/095476.html https://review.openstack.org/#/c/318746/ https://review.openstack.org/#/c/314079/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583700/+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 1583701] [NEW] Use correct type for UUIDs
Public bug reported: Description === In http://developer.openstack.org/api-ref/compute/ there many cases where the Type is a string instead of a uuid. For example tenant_id: Name InTypeDescription tenant_id path string The UUID of the tenant in a multi-tenancy cloud. should be: Name InTypeDescription tenant_id path uuidThe UUID of the tenant in a multi-tenancy cloud. Also: NameIn TypeDescription servers bodyarray List of server objects. id bodystring The UUID of the server. NameIn TypeDescription servers bodyarray List of server objects. id bodyuuidThe UUID of the server. ** 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/1583701 Title: Use correct type for UUIDs Status in OpenStack Compute (nova): New Bug description: Description === In http://developer.openstack.org/api-ref/compute/ there many cases where the Type is a string instead of a uuid. For example tenant_id: NameInTypeDescription tenant_id pathstring The UUID of the tenant in a multi-tenancy cloud. should be: NameInTypeDescription tenant_id pathuuidThe UUID of the tenant in a multi-tenancy cloud. Also: Name In TypeDescription servers body array List of server objects. idbodystring The UUID of the server. Name In TypeDescription servers body array List of server objects. idbodyuuidThe UUID of the server. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1583701/+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 1583694] [NEW] [RFE] DVR support for Allowed_address_pair port that are bound to multiple ACTIVE VM ports used by Octavia
Public bug reported: DVR support for Allowed_address_pair ports with FloatingIP that are unbound and assgined to Multiple VMs that are active. Problem Statement: When FloatingIP is asssigned to Allowed_address_pair port and assigned to multiple VMs that are ACTIVE and connected to DVR (Distributed Virtual Router) routers, the FloatingIP is not functional. The use case here is to provide redundancy to the VMs that are serviced by the DVR routers. This feature works good for Legacy Routers ( Centralized Routers). Theory: Distributed Virtual Routers were designed for scalability and performance and to reduce the load on the single network node. Distributed Virtual Routers are created on each Compute node dynamically on demand and removed when not required. Distributed Virtual Routers heavily depend on the port binding to identify the requirement of a DVR service on a particular node. Today we only create/update/delete floatingip based on the router and the host in which the floatingip service is required. So the 'host' part is very critical for the operation of the DVR. In the above mentioned use case, we are dealing with Allowed_address_pair port, which is unbound to any specific host and are also assigned to multiple VMs that are ACTIVE at the same time. We have a work around today to inherit the parent VMs port binding properties for the allowed_address_pair port if the parent VMs port is ACTIVE. This has a limitation, that we assume that there would be only one "ACTIVE" VM port with the allowed_address_pair port for this to work. The reason for this is, if we have multiple "ACTIVE" VM port associated with the same allowed_address_pair port, and if the allowed_address_pair port has a FloatingIP associated with it, we can't provide the FloatingIP service on all the nodes were the VM's port is ACTIVE. This would create an issue because we will be seeing the same FloatingIP being advertised(GARP) from all nodes, and so the users on the external network will get confused on where the actual "ACTIVE" port is. Why is it working with Legacy Routers: In the case of legacy routers, the routers are always located a the network node and the DNAT is also done at the router_namespace in the Network node. They don't depend on the host-binding, since all the traffic have to flow through the centralized router in the network node. Also in the case of centralized routers, there is not issue of Floatingip GARP, since it is always going to be coming in through a single node. So in the background, the allowed_address_pair port MAC is being dynamically switched from one VM to another VM by the keepalived that runs in the VM. So neutron does not need to know about any of those and it works as expected. Why it is not working with DVR Routers: 1. Allowed_address_pair does not have host-binding. 2. If we were to inherit from the VMs host-binding, there are multiple VMs that are ACTIVE, so we can't have a single host-binding for these allowed_address_pair ports. 3. Even if we ignore the port_binding on the allowed_address_pair port and try to start providing the plumbing for the FloatingIP on multiple nodes based on the VMs it is assoicated with, there are issues with the same FloatingIP being GARP from different compute nodes that would confuse. How we can make it to work with DVR: Option 1: Neutron should have a some visibility on the state of the VM port, when the switch between ACTIVE and STANDBY happens. Today it is done by the keepalived on the VM and so it is not being logged anywhere. If the keepalived can log the event in neutron port, then it can be used by the neutron to determine when to allow FloatingIP traffic and block FloatingIP traffic for a particular node, and then send the GARP from the respective node. There is some delay introduced in this as well. (Desired) Low-hanging fruit. Option 2: Option 2 basically negates the Distributed nature of DVR and makes it centralized for North-South. The other option is to have the FloatingIP functionality centralized for such features. But this would be more complex, since we need to introduce config options for agents and floatingip. Also in this case, we can't have both the local floatingip and centralized floatingip support for the same node. A compute node can only have either localized floatingip or centralized floatingip. Complex ( Negates the purpose of DVR) References: Some references to the patches that we have already to support a single use case for the Allowed_address_pair with FloatingIP in DVR. https://review.openstack.org/#/c/254439/ https://review.openstack.org/#/c/301410/ https://review.openstack.org/#/c/304905/ ** Affects: neutron Importance: Undecided Status: New ** Tags: l3-dvr-backlog lbaas neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1583694 Title: [RFE] DVR support for All
[Yahoo-eng-team] [Bug 1567049] Re: DHCP agent not reusing iface device when namespace is missing
I haven't been able to reproduce this lately using my single node devstack
w/ovs env.
Closing as invalid. If the issue (re)crops up, I'll reopen the dug accordingly.
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1567049
Title:
DHCP agent not reusing iface device when namespace is missing
Status in neutron:
Invalid
Bug description:
Using neutron master with devstack all-in-one installation.
Under specific circumstances, the neutron dhcp agent (with dnsmasq
driver) will incorrectly create a new interface device rather than
reusing the existing one if the network's namespace is accidentally
deleted.
1. Neutron net created.
2. Neutron subnet created for network in step #1 with dhcp enabled.
3. Network dhcp namespace accidentally deleted.
4. New subnet added to network in #1 with dhcp enabled.
--> DHCP agent incorrectly creates a new interface device rather than reusing
the existing. The initial iface is now "orphaned".
The script below reproduces the error on my devstack all-in-one:
#!/bin/bash
source ~/devstack/openrc admin admin
neutron net-create dhcp-net
echo "Interfaces before..."
sudo ovs-vsctl show
neutron subnet-create dhcp-net 192.168.1.0/24 --name dhcp-subnet1
sleep 2
for ns in `sudo ip netns list | grep qdhcp-*`; do
echo "Deleting namespace $ns"
sudo ip netns delete ${ns}
done
neutron subnet-create dhcp-net 192.168.2.0/24 --name dhcp-subnet2
sleep 2
neutron net-delete dhcp-net
sleep 2
echo "Interfaces after..."
sudo ovs-vsctl show
Sample ovs output from running the script:
...
Interfaces before...
0b073a08-021d-49d9-b176-5008bf87ae39
Manager "tcp:127.0.0.1:6632"
Bridge br-int
Port br-int
Interface br-int
type: internal
ovs_version: "2.0.2"
...
Interfaces after...
0b073a08-021d-49d9-b176-5008bf87ae39
Manager "tcp:127.0.0.1:6632"
Bridge br-int
Port br-int
Interface br-int
type: internal
Port "tapcf35e3b7-06"
Interface "tapcf35e3b7-06"
ovs_version: "2.0.2"
As shown in the output, a port device is left over, even after the
network + subnets are deleted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1567049/+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 1583562] Re: neutronclient should update tempest_lib to tempest.lib
** 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/1583562 Title: neutronclient should update tempest_lib to tempest.lib Status in python-neutronclient: New Bug description: As tempest_lib had been moved to tempest.lib Per http://specs.openstack.org/openstack/qa-specs/specs/tempest /reintegrate-tempest-lib.html the tempest-lib project is going to live in the tempest repo. So neutronclient should update them in tempest tests. To manage notifications about this bug go to: https://bugs.launchpad.net/python-neutronclient/+bug/1583562/+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 1547271] Re: Preserve subnet_create behavior in presence of subnet pools
This is no longer relevant. The default subnetpool behavior has changed in Mitaka. You need to request the use of a default subnetpool explicitly. That makes this problem moot. ** Changed in: neutron Status: Confirmed => Invalid ** Changed in: openstack-manuals Status: Confirmed => 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/1547271 Title: Preserve subnet_create behavior in presence of subnet pools Status in neutron: Invalid Status in openstack-api-site: Invalid Status in openstack-manuals: Invalid Bug description: https://review.openstack.org/279378 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit d38aeade9db7169955b4524a5fc8d814067dec15 Author: Armando Migliaccio Date: Thu Feb 11 20:56:20 2016 -0800 Preserve subnet_create behavior in presence of subnet pools The development of the auto_allocate extension, which relies on subnet pools, revealed some discrepancies in the behavior of the subnet_create API: if a user specifies a cidr on subnet_create like he/she is used to, the API outcome changes in presence of default subnetpools. For instance the command 'neutron subnet-create network ' returns a subnet associated to a pool, if a default pool exists, but it does not otherwise. At the same time, attempting to create a subnet without passing any detail but the ip version also behaves unexpectedly depending on the state of the system. Whilst this could be considered convenient in some circumstances, it is problematic for a couple of reasons: a) it breaks a well defined contract (backward compat of the subnet-create command), and b) it leads to ambiguity of the API. This patch restores the semantic of the subnet_create API where it is mandatory to specify CIDR/IP version regardless of the conditions under which the request is issued. On the other hand, associating subnets to subnet pools will have to be more prescriptive, and require the user to explicitly state his/her intentions when creating the subnet: if a user does want a subnet (CIDR) to belong to a subnet pool, he/she will have to state so, either by specifying a subnetpool name/uuid, or by asking for a default one. This will be tackled as a follow-up, especially in order to address the needs of prefix delegation which currently rely on the ambiguous behavior that this patch is fixing. Closes-bug: 1545199 DocImpact: subnetpools can be used to simplify IPAM, and can be specified during subnet creation. Change-Id: Idf516ed9db24d779742cdff0584b48182a8502d6 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1547271/+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
** Also affects: freezer Importance: Undecided Status: New ** Changed in: freezer Status: New => In Progress ** Changed in: freezer Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- 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 anvil: In Progress Status in Aodh: Fix Released Status in Astara: Fix Released Status in Barbican: Fix Released Status in bilean: 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 congress: Fix Released Status in Designate: Fix Released Status in django-openstack-auth: Fix Released Status in django-openstack-auth-kerberos: In Progress Status in DragonFlow: Fix Released Status in ec2-api: Fix Released Status in Evoque: In Progress Status in Freezer: In Progress Status in gce-api: Fix Released Status in Gnocchi: Fix Released Status in heat: Fix Released Status in heat-cfntools: In Progress Status in OpenStack Identity (keystone): Fix Released Status in KloudBuster: Fix Released Status in kolla: Fix Released Status in Magnum: Fix Released Status in Manila: Fix Released Status in Mistral: In Progress Status in networking-arista: In Progress Status in networking-calico: In Progress Status in networking-cisco: In Progress Status in networking-fujitsu: Fix Released Status in networking-odl: In Progress Status in networking-ofagent: In Progress Status in networking-plumgrid: In Progress Status in networking-powervm: Fix Released Status in networking-vsphere: Fix Released Status in neutron: In Progress Status in OpenStack Compute (nova): In Progress Status in nova-powervm: Fix Released Status in nova-solver-scheduler: In Progress Status in octavia: Fix Released Status in openstack-ansible: Fix Released Status in oslo.cache: Fix Released Status in Packstack: Fix Released Status in python-dracclient: Fix Released Status in python-magnumclient: Fix Released Status in RACK: In Progress Status in python-watcherclient: In Progress Status in OpenStack Search (Searchlight): Fix Released Status in shaker: Fix Released Status in Solum: Fix Released Status in tempest: In Progress Status in tripleo: In Progress Status in trove-dashboard: Fix Released Status in watcher: Fix Released 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/anvil/+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 1582663] Re: Node should not exposed to nova if no port associated with it
Moving this to Nova, as Ironic does not control what Nova tracks. ** Project changed: ironic => nova ** Summary changed: - Node should not exposed to nova if no port associated with it + An Ironic node should not be exposed to Nova if no Ironic port is associated with it ** Tags added: ironic -- 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/1582663 Title: An Ironic node should not be exposed to Nova if no Ironic port is associated with it Status in OpenStack Compute (nova): New Bug description: We should check whether there are ports associated with the node during verifying process, then we can enroll a node without any port, but it can't be available to nova. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1582663/+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 1583499] Re: ironic instance_info does not update when nova instance has been changed
We don't sync information back from Nova, so it's up to Nova to provide
any updates. I seriously doubt they will, though.
** Project changed: ironic => nova
** Tags added: ironic
--
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/1583499
Title:
ironic instance_info does not update when nova instance has been
changed
Status in OpenStack Compute (nova):
New
Bug description:
like this :
[root@controller1 ironic]# ironic node-show
7f63ec59-d791-43fd-933d-16c05490a8ee | grep instance_info
| instance_info | {u'root_gb': u'100', u'display_name': u'test',
u'image_source': |
[root@controller1 ironic]#
[root@controller1 ironic]# nova list
+--+--+++-+---+
| ID | Name | Status | Task State |
Power State | Networks |
+--+--+++-+---+
| 1e5149f4-4923-4e21-ad1b-c418edfb0479 | test | ACTIVE | - |
Running | ironic=192.168.189.37 |
+--+--+++-+---+
[root@controller1 ironic]#
this display_name is different, ironic does not update the
instance_info from time to time
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1583499/+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 1557378] Re: tox gives invalid uuid warnings in unit test
Reviewed: https://review.openstack.org/302658
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=b1d9c3edd87fb9e547c5e374d836b673989747a7
Submitter: Jenkins
Branch:master
commit b1d9c3edd87fb9e547c5e374d836b673989747a7
Author: srushti
Date: Tue Apr 5 13:27:43 2016 +
Fix invalid uuid warnings
Currently, unit testcases emit FutureWarnings from oslo.versionedobjects
about invalid uuids as documented here[1].
This commit changes these tests to use valid uuids so
that when they are run these warnings are no longer emitted.
[1]
http://docs.openstack.org/developer/oslo.versionedobjects/api/fields.html#oslo_versionedobjects.fields.UUIDField
Closes-Bug: #1557378
Change-Id: I21a60e916e183f7c0fc6193d4b7caa88ae3b6d56
** 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/1557378
Title:
tox gives invalid uuid warnings in unit test
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Currently 'tox -epy27' emits 318 FutureWarnings from oslo.versionedobjects
about invalid uuids.
When invalid uuids are used in the test cases, tox gives FutureWarnings.
Steps to reproduce:
Run tox -epy27 command.
Sample Output:
{3}nova.tests.unit.api.openstack.compute.legacy_v2.test_servers.ServersControllerCreateTest.test_create_instance_with_disk_config_disabled
[0.266687s] ... ok
{1}nova.tests.unit.api.openstack.compute.test_server_groups.ServerGroupTestV2.test_create_server_group_with_duplicate_policies
[0.059925s] ... ok
{0}
nova.tests.unit.api.openstack.compute.test_server_group_quotas.ServerGroupQuotasTestV2.test_delete_server_group_by_id
[0.128866s] ... ok
Captured stderr:
/opt/stack/nova/.tox/py27/local/lib/python2.7/site-packages/oslo_versionedobjects/fields.py:325:
FutureWarning: fake-uuid is an invalid UUID. Using UUIDFields with invalid
UUIDs is no longer supported, and will be removed in a future release. Please
update your code to input valid UUIDs or accept ValueErrors for invalid UUIDs.
See
http://docs.openstack.org/developer/oslo.versionedobjects/api/fields.html#oslo_versionedobjects.fields.UUIDField
for further details
"for further details" % value, FutureWarning)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1557378/+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 1582663] [NEW] Node should not exposed to nova if no port associated with it
You have been subscribed to a public bug: We should check whether there are ports associated with the node during verifying process, then we can enroll a node without any port, but it can't be available to nova. ** Affects: nova Importance: Undecided Assignee: Zhenguo Niu (niu-zglinux) Status: New -- Node should not exposed to nova if no port associated with it https://bugs.launchpad.net/bugs/1582663 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). -- 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 1583499] [NEW] ironic instance_info does not update when nova instance has been changed
You have been subscribed to a public bug:
like this :
[root@controller1 ironic]# ironic node-show
7f63ec59-d791-43fd-933d-16c05490a8ee | grep instance_info
| instance_info | {u'root_gb': u'100', u'display_name': u'test',
u'image_source': |
[root@controller1 ironic]#
[root@controller1 ironic]# nova list
+--+--+++-+---+
| ID | Name | Status | Task State | Power
State | Networks |
+--+--+++-+---+
| 1e5149f4-4923-4e21-ad1b-c418edfb0479 | test | ACTIVE | - |
Running | ironic=192.168.189.37 |
+--+--+++-+---+
[root@controller1 ironic]#
this display_name is different, ironic does not update the instance_info
from time to time
** Affects: nova
Importance: Undecided
Status: New
--
ironic instance_info does not update when nova instance has been changed
https://bugs.launchpad.net/bugs/1583499
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
--
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 1583611] [NEW] Compiled .mo files are not included in keystone builds
Public bug reported: When I create compiled .mo files using command: # python setup.py compile_catalog The .mo created files are not included when i build with # python setyp.py build ** Affects: keystone Importance: Undecided Assignee: Alfredo Moralejo (amoralej) Status: 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/1583611 Title: Compiled .mo files are not included in keystone builds Status in OpenStack Identity (keystone): In Progress Bug description: When I create compiled .mo files using command: # python setup.py compile_catalog The .mo created files are not included when i build with # python setyp.py build To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1583611/+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 1583601] [NEW] Duplicated sg rules could be created with diff description
Public bug reported: I can create multiple security group rules with same content, but different descriptions. For example, [fedora@normal2 ~]$ neutron security-group-rule-create test --protocol tcp --remote-group-id 1b8c08e5-728d-48ef-a24b-e4ebc20808a3 Created a new security_group_rule: +---+--+ | Field | Value| +---+--+ | description | | | direction | ingress | | ethertype | IPv4 | | id| 09eaa983-7884-4c27-bffb-81064d164688 | | port_range_max| | | port_range_min| | | protocol | tcp | | remote_group_id | 1b8c08e5-728d-48ef-a24b-e4ebc20808a3 | | remote_ip_prefix | | | security_group_id | db8d1386-0b2e-4f0c-b4c2-16c10b30fd92 | | tenant_id | 02178a7c126a4066ab5c3fae571d89c8 | +---+--+ [fedora@normal2 ~]$ neutron security-group-rule-create test --protocol tcp --remote-group-id 1b8c08e5-728d-48ef-a24b-e4ebc20808a3 --description "123" Created a new security_group_rule: +---+--+ | Field | Value| +---+--+ | description | 123 | | direction | ingress | | ethertype | IPv4 | | id| 5282599c-4262-4c48-b999-052a0ce5cff7 | | port_range_max| | | port_range_min| | | protocol | tcp | | remote_group_id | 1b8c08e5-728d-48ef-a24b-e4ebc20808a3 | | remote_ip_prefix | | | security_group_id | db8d1386-0b2e-4f0c-b4c2-16c10b30fd92 | | tenant_id | 02178a7c126a4066ab5c3fae571d89c8 | +---+--+ This should be prevented. ** Affects: neutron Importance: Undecided Assignee: Hong Hui Xiao (xiaohhui) Status: New ** Tags: sg-fw ** Changed in: neutron Assignee: (unassigned) => Hong Hui Xiao (xiaohhui) ** Tags added: sg-fw -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1583601 Title: Duplicated sg rules could be created with diff description Status in neutron: New Bug description: I can create multiple security group rules with same content, but different descriptions. For example, [fedora@normal2 ~]$ neutron security-group-rule-create test --protocol tcp --remote-group-id 1b8c08e5-728d-48ef-a24b-e4ebc20808a3 Created a new security_group_rule: +---+--+ | Field | Value| +---+--+ | description | | | direction | ingress | | ethertype | IPv4 | | id| 09eaa983-7884-4c27-bffb-81064d164688 | | port_range_max| | | port_range_min| | | protocol | tcp | | remote_group_id | 1b8c08e5-728d-48ef-a24b-e4ebc20808a3 | | remote_ip_prefix | | | security_group_id | db8d1386-0b2e-4f0c-b4c2-16c10b30fd92 | | tenant_id | 02178a7c126a4066ab5c3fae571d89c8 | +---+--+ [fedora@normal2 ~]$ neutron security-group-rule-create test --protocol tcp --remote-group-id 1b8c08e5-728d-48ef-a24b-e4ebc20808a3 --description "123" Created a new security_group_rule: +---+--+ | Field | Value| +---+--+ | description | 123 | | direction | ingress | | ethertype | IPv4 | | id| 5282599c-4262-4c48-b999-052a0ce5cff7 | | port_range_max| | | port_range_min| | | protocol | tcp | | remote_group_id | 1b8c08e5-728d-48ef-a24b-e4ebc20808a3 | | remote_ip_prefix |
[Yahoo-eng-team] [Bug 1558939] Re: Truncated hint text due to the limited length set in the field
** Changed in: horizon Status: In Progress => Fix Released ** Changed in: magnum-ui 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/1558939 Title: Truncated hint text due to the limited length set in the field Status in OpenStack Dashboard (Horizon): Fix Released Status in Magnum UI: Invalid Bug description: Project > Instances > Launch Instance > Source Japanese version of input hint text "Click here for filters" is truncated and it seems that there is a limit on the length of the text to be visible in the field. English text fits in perfectly but there should be a number of languages in which translation is longer than the English text. It is better if it is not restricated to such short length, so that the entire message can be shown to the users. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1558939/+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 1583503] Re: keepalived fails to start when PID file is empty
** Also affects: keepalived (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: keepalived (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: keepalived (Ubuntu Trusty) Status: New => Triaged ** Changed in: keepalived (Ubuntu Xenial) Status: New => Triaged ** Changed in: keepalived (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: keepalived (Ubuntu Xenial) Importance: Undecided => Medium ** Tags added: bitesize -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1583503 Title: keepalived fails to start when PID file is empty Status in neutron: New Status in keepalived package in Ubuntu: Fix Released Status in keepalived source package in Trusty: Triaged Status in keepalived source package in Xenial: Triaged Bug description: After a crash of a network node, we were left with empty PID files for some keepalived processes: root@network-node14:~# ls -l /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid -rw-r--r-- 1 root root 0 May 19 08:41 /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid This causes the L3 agent to log the following errors repeating every minute: 2016-05-19 08:46:44.525 13554 ERROR neutron.agent.linux.utils [-] Unable to convert value in /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid 2016-05-19 08:46:44.526 13554 ERROR neutron.agent.linux.external_process [-] keepalived for router with uuid 0ab5f647-1e04-4345-ae9b-ee66c6f08882 not found. The process should not have died 2016-05-19 08:46:44.526 13554 WARNING neutron.agent.linux.external_process [-] Respawning keepalived for uuid 0ab5f647-1e04-4345-ae9b-ee66c6f08882 2016-05-19 08:46:44.526 13554 ERROR neutron.agent.linux.utils [-] Unable to convert value in /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid 2016-05-19 08:46:44.526 13554 ERROR neutron.agent.linux.utils [-] Unable to convert value in /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid-vrrp and the keepalived process fails to start. As a result, the routers hosted by this agent are non-functional. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583503/+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 1583562] [NEW] neutronclient should update tempest_lib to tempest.lib
Public bug reported: As tempest_lib had been moved to tempest.lib Per http://specs.openstack.org/openstack/qa-specs/specs/tempest /reintegrate-tempest-lib.html the tempest-lib project is going to live in the tempest repo. So neutronclient should update them in tempest tests. ** Affects: neutron Importance: Undecided Assignee: zhaobo (zhaobo6) Status: New ** Changed in: neutron Assignee: (unassigned) => zhaobo (zhaobo6) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1583562 Title: neutronclient should update tempest_lib to tempest.lib Status in neutron: New Bug description: As tempest_lib had been moved to tempest.lib Per http://specs.openstack.org/openstack/qa-specs/specs/tempest /reintegrate-tempest-lib.html the tempest-lib project is going to live in the tempest repo. So neutronclient should update them in tempest tests. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583562/+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 1583545] [NEW] can't create "ping" rule in security groups
Public bug reported: As you can see here: https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol Allowing pings requires setting a custom ICMP rule of Type 8 and code 0 In stable/mitaka and on master it is now not possible, the form will not validate and gives this error: The ICMP code is invalid. Not a valid port number as if "0" was a port number (but is not, it's the icmp code). ** Affects: horizon Importance: Undecided Status: New ** Attachment added: "Displayed form validation error" https://bugs.launchpad.net/bugs/1583545/+attachment/4666149/+files/ping.png -- 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/1583545 Title: can't create "ping" rule in security groups Status in OpenStack Dashboard (Horizon): New Bug description: As you can see here: https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol Allowing pings requires setting a custom ICMP rule of Type 8 and code 0 In stable/mitaka and on master it is now not possible, the form will not validate and gives this error: The ICMP code is invalid. Not a valid port number as if "0" was a port number (but is not, it's the icmp code). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1583545/+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 1583024] Re: neutron-heat: ERROR: HEAT-E99001
** No longer affects: neutron ** Also affects: heat 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/1583024 Title: neutron-heat: ERROR: HEAT-E99001 Status in heat: New Status in Magnum: New Status in puppet-magnum: New Bug description: Hi, I am using Mitaka release on RDO (CentOS 7.2). I am using Puppet to deploy OpenStack. As magnum interacts with heat,neutron I am addressing this bug here, sorry if this is a wrong place. I have the following error while creating swarm bay in magnum: ERROR: HEAT-E99001 Service neutron is not available for resource type OS::Neutron::HealthMonitor, reason: Service endpoint not in service catalog. I can create lb, it's working, etc. AFAIK magnum supports only lbaasv1. More info inside this thread: http://lists.openstack.org/pipermail/openstack- dev/2016-May/094714.html Question: does lbaas v1 plugin work in Mitaka? I did enabled lbaasv2 for Mitaka as apparently this is the only supported version according to the docs: http://docs.openstack.org/mitaka/networking-guide/adv-config- lbaas.html To manage notifications about this bug go to: https://bugs.launchpad.net/heat/+bug/1583024/+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 1583503] Re: keepalived fails to start when PID file is empty
Thank you for taking the time to report this bug and helping to make Ubuntu better. Yakkety has 1.2.20, so this is Fix Released. You asked for a backport but you haven't said what package version you're using, what release you want the fix backported to or in which releases you have confirmed the bug to exist. Is it Trusty, Xenial, both or other? For each one, please can you state whether you have confirmed the bug to exist? ** Changed in: keepalived (Ubuntu) Status: New => 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/1583503 Title: keepalived fails to start when PID file is empty Status in neutron: New Status in keepalived package in Ubuntu: Fix Released Bug description: After a crash of a network node, we were left with empty PID files for some keepalived processes: root@network-node14:~# ls -l /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid -rw-r--r-- 1 root root 0 May 19 08:41 /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid This causes the L3 agent to log the following errors repeating every minute: 2016-05-19 08:46:44.525 13554 ERROR neutron.agent.linux.utils [-] Unable to convert value in /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid 2016-05-19 08:46:44.526 13554 ERROR neutron.agent.linux.external_process [-] keepalived for router with uuid 0ab5f647-1e04-4345-ae9b-ee66c6f08882 not found. The process should not have died 2016-05-19 08:46:44.526 13554 WARNING neutron.agent.linux.external_process [-] Respawning keepalived for uuid 0ab5f647-1e04-4345-ae9b-ee66c6f08882 2016-05-19 08:46:44.526 13554 ERROR neutron.agent.linux.utils [-] Unable to convert value in /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid 2016-05-19 08:46:44.526 13554 ERROR neutron.agent.linux.utils [-] Unable to convert value in /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid-vrrp and the keepalived process fails to start. As a result, the routers hosted by this agent are non-functional. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583503/+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 1583024] Re: neutron-heat: ERROR: HEAT-E99001
It seems heat's error. Heat's CI has neutron integration tests and now I cannot see error of these tests in CI job. I guess that it's issue about magnum or deploy. ** Changed in: neutron Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1583024 Title: neutron-heat: ERROR: HEAT-E99001 Status in Magnum: New Status in neutron: Invalid Status in puppet-magnum: New Bug description: Hi, I am using Mitaka release on RDO (CentOS 7.2). I am using Puppet to deploy OpenStack. As magnum interacts with heat,neutron I am addressing this bug here, sorry if this is a wrong place. I have the following error while creating swarm bay in magnum: ERROR: HEAT-E99001 Service neutron is not available for resource type OS::Neutron::HealthMonitor, reason: Service endpoint not in service catalog. I can create lb, it's working, etc. AFAIK magnum supports only lbaasv1. More info inside this thread: http://lists.openstack.org/pipermail/openstack- dev/2016-May/094714.html Question: does lbaas v1 plugin work in Mitaka? I did enabled lbaasv2 for Mitaka as apparently this is the only supported version according to the docs: http://docs.openstack.org/mitaka/networking-guide/adv-config- lbaas.html To manage notifications about this bug go to: https://bugs.launchpad.net/magnum/+bug/1583024/+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 1583508] Re: Create Router fails for VDX(networking-brocade) when done with subnet option
** Changed in: neutron
Status: New => 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/1583508
Title:
Create Router fails for VDX(networking-brocade) when done with subnet
option
Status in neutron:
Fix Released
Bug description:
1. When VRRP is enabled, the router interface deletion using
subnet id , is failing to remove the router-port-list associated with
the subnet entirely and hence router deletion fails.
OUTPUT:
VRRP : Enabled
neutron router-interface-add Router_test red-sub
Added interface 59963328-8174-4d50-ab5b-fd796e47d63f to router Router_test.
root@Ubu14-42-18:~# neutron router-port-list Router_test
+--+--+---+-+
| id | name | mac_address | fixed_ips
|
+--+--+---+-+
| 59963328-8174-4d50-ab5b-fd796e47d63f | | fa:16:3e:fb:23:ef |
{"subnet_id": "cc64f073-ffe5-4a2c-89f5-6415264c9ea6", "ip_address": "16.0.0.1"}
|
| | | |
{"subnet_id": "cc64f073-ffe5-4a2c-89f5-6415264c9ea6", "ip_address": "16.0.0.3"}
|
| | | |
{"subnet_id": "cc64f073-ffe5-4a2c-89f5-6415264c9ea6", "ip_address": "16.0.0.4"}
|
+--+--+---+-+
root@Ubu14-42-18:~# neutron router-interface-delete Router_test red-sub
Removed interface from router Router_test.
root@Ubu14-42-18:~# neutron router-port-list Router_test
+--+--+---+---+
| id | name | mac_address | fixed_ips
|
+--+--+---+---+
| 59963328-8174-4d50-ab5b-fd796e47d63f | | fa:16:3e:fb:23:ef |
|
+--+--+---+---+
root@Ubu14-42-18:~# neutron router-delete Router_test
Router 13c9c988-f415-4c12-804d-a3e495c6f0b3 still has ports
Neutron server returns request_ids:
['req-083e1c92-06af-4c2d-862a-bcbad7e6ed3a']
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1583508/+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 1583519] [NEW] Add tempest to test-requirements.txt
Public bug reported: Neutron is updated to use tempest instead of tempest-lib with the below commit https://github.com/openstack/neutron/commit/e3210bc880c1cda8a883cb5da05b279cd87aecd4 With this, neutron's tempest tests depend on "tempest" package, but this package is not added to test-requirements.txt Need to add tempest to test-requirements.txt ** Affects: neutron Importance: Undecided Assignee: venkata anil (anil-venkata) Status: New ** 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/1583519 Title: Add tempest to test-requirements.txt Status in neutron: New Bug description: Neutron is updated to use tempest instead of tempest-lib with the below commit https://github.com/openstack/neutron/commit/e3210bc880c1cda8a883cb5da05b279cd87aecd4 With this, neutron's tempest tests depend on "tempest" package, but this package is not added to test-requirements.txt Need to add tempest to test-requirements.txt To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583519/+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 1582086] Re: Add negative API tests that try to remove the resources in use.
Reviewed: https://review.openstack.org/316592 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=18d16cfb4327fd76cd11986c6552c48a0e85833f Submitter: Jenkins Branch:master commit 18d16cfb4327fd76cd11986c6552c48a0e85833f Author: Maho Koshiya Date: Sun May 15 13:23:44 2016 +0900 Add negative API tests that try to remove the resources in use. The tests that remove resources in use are not covered enough in api tests. This patch include test case of network, subnet and router delete in use. Change-Id: Id9d04f071e5a4b3553e97a5eee4431fb601a9c7f Closes-bug: #1582086 ** 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/1582086 Title: Add negative API tests that try to remove the resources in use. Status in neutron: Fix Released Bug description: The tests that remove resources in use are not covered enough in api tests. E.g.: The test that try to delete the router in which interface has been added, without running router_remove_interface API. These tests are necessary for it avoid that the user can delete resources in use by mistake. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1582086/+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 1583512] [NEW] DBDeadlock: (_mysql_exceptions.OperationalError) while deleting user
Public bug reported: The error happened at the end of Rally test when Rally started to remove users Found on MOS 9.0 build 308 Environment: 1 controller 2 compute 1 cinder Steps to reproduce: Run Sahara Rally test create_and_list_nodegroup_templates.yaml Wait until iterations passed and users context started to remove users Expected result: Keystone removed user by Rally request without errors Actual result: Keystone API raised 500 error >From Keystone admin log: 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi [req-23d801cf-baa4-410d-9d46-6eb6ca7dfa34 21fe895155b54960b09290ef179ce15e 56b54d0fb50e40b5bb7ccdb46c8d21a7 - default default] (_mysql_exceptions.OperationalError) (1213, 'Deadlock found when trying to get lock; try restarting transaction') [SQL: u'DELETE FROM revocation_event WHERE revocation_event.revoked_at < %s'] [parameters: (datetime.datetime(2016, 5, 19, 6, 57, 44, 270231),)] 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi Traceback (most recent call last): 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/keystone/common/wsgi.py", line 249, in __call__ 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi result = method(context, **params) 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/oslo_log/versionutils.py", line 165, in wrapped 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi return func_or_cls(*args, **kwargs) 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/keystone/identity/controllers.py", line 174, in delete_user 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi self.identity_api.delete_user(user_id, initiator) 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/keystone/common/manager.py", line 124, in wrapped 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi __ret_val = __f(*args, **kwargs) 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/keystone/identity/core.py", line 433, in wrapper 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi return f(self, *args, **kwargs) 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/keystone/identity/core.py", line 443, in wrapper 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi return f(self, *args, **kwargs) 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/keystone/identity/core.py", line 986, in delete_user 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi notifications.Audit.deleted(self._USER, user_id, initiator) 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/keystone/notifications.py", line 166, in deleted 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi public) 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/keystone/notifications.py", line 137, in _emit 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi public=public) 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/keystone/notifications.py", line 421, in _send_notification 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi notify_event_callbacks(SERVICE, resource_type, operation, payload) 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/keystone/notifications.py", line 316, in notify_event_callbacks 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi cb(service, resource_type, operation, payload) 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/keystone/revoke/core.py", line 84, in _user_callback 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi self.revoke_by_user(payload['resource_info']) 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/keystone/common/manager.py", line 124, in wrapped 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi __ret_val = __f(*args, **kwargs) 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/keystone/revoke/core.py", line 151, in revoke_by_user 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi return self.revoke(revoke_model.RevokeEvent(user_id=user_id)) 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/keystone/common/manager.py", line 124, in wrapped 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi __ret_val = __f(*args, **kwargs) 2016-05-19 08:27:44.302 21563 ERROR keystone.common.wsgi File "/usr/lib/python2.7/dist-packages/keystone/revoke/core.py", line 229, in revoke 2016-05-19 08:27:44.302
[Yahoo-eng-team] [Bug 1583503] Re: L3 HA broken after network node crash
It seems that this is mainly a bug in how keepalived handles an empty or otherwise broken pid file. According to the upstream change log, the issue has been fixed in 1.2.20. @Ubuntu: Can you look into updating the package or backporting the fix? ** Also affects: keepalived (Ubuntu) Importance: Undecided Status: New ** Summary changed: - L3 HA broken after network node crash + keepalived fails to start when PID file is empty -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1583503 Title: keepalived fails to start when PID file is empty Status in neutron: New Status in keepalived package in Ubuntu: New Bug description: After a crash of a network node, we were left with empty PID files for some keepalived processes: root@network-node14:~# ls -l /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid -rw-r--r-- 1 root root 0 May 19 08:41 /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid This causes the L3 agent to log the following errors repeating every minute: 2016-05-19 08:46:44.525 13554 ERROR neutron.agent.linux.utils [-] Unable to convert value in /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid 2016-05-19 08:46:44.526 13554 ERROR neutron.agent.linux.external_process [-] keepalived for router with uuid 0ab5f647-1e04-4345-ae9b-ee66c6f08882 not found. The process should not have died 2016-05-19 08:46:44.526 13554 WARNING neutron.agent.linux.external_process [-] Respawning keepalived for uuid 0ab5f647-1e04-4345-ae9b-ee66c6f08882 2016-05-19 08:46:44.526 13554 ERROR neutron.agent.linux.utils [-] Unable to convert value in /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid 2016-05-19 08:46:44.526 13554 ERROR neutron.agent.linux.utils [-] Unable to convert value in /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid-vrrp and the keepalived process fails to start. As a result, the routers hosted by this agent are non-functional. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583503/+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 1583508] [NEW] Create Router fails for VDX(networking-brocade) when done with subnet option
Public bug reported:
1. When VRRP is enabled, the router interface deletion using subnet
id , is failing to remove the router-port-list associated with the
subnet entirely and hence router deletion fails.
OUTPUT:
VRRP : Enabled
neutron router-interface-add Router_test red-sub
Added interface 59963328-8174-4d50-ab5b-fd796e47d63f to router Router_test.
root@Ubu14-42-18:~# neutron router-port-list Router_test
+--+--+---+-+
| id | name | mac_address | fixed_ips
|
+--+--+---+-+
| 59963328-8174-4d50-ab5b-fd796e47d63f | | fa:16:3e:fb:23:ef |
{"subnet_id": "cc64f073-ffe5-4a2c-89f5-6415264c9ea6", "ip_address": "16.0.0.1"}
|
| | | |
{"subnet_id": "cc64f073-ffe5-4a2c-89f5-6415264c9ea6", "ip_address": "16.0.0.3"}
|
| | | |
{"subnet_id": "cc64f073-ffe5-4a2c-89f5-6415264c9ea6", "ip_address": "16.0.0.4"}
|
+--+--+---+-+
root@Ubu14-42-18:~# neutron router-interface-delete Router_test red-sub
Removed interface from router Router_test.
root@Ubu14-42-18:~# neutron router-port-list Router_test
+--+--+---+---+
| id | name | mac_address | fixed_ips |
+--+--+---+---+
| 59963328-8174-4d50-ab5b-fd796e47d63f | | fa:16:3e:fb:23:ef | |
+--+--+---+---+
root@Ubu14-42-18:~# neutron router-delete Router_test
Router 13c9c988-f415-4c12-804d-a3e495c6f0b3 still has ports
Neutron server returns request_ids: ['req-083e1c92-06af-4c2d-862a-bcbad7e6ed3a']
** Affects: neutron
Importance: Undecided
Assignee: Ritesh Madapurath (rmadapur)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Ritesh Madapurath (rmadapur)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1583508
Title:
Create Router fails for VDX(networking-brocade) when done with subnet
option
Status in neutron:
New
Bug description:
1. When VRRP is enabled, the router interface deletion using
subnet id , is failing to remove the router-port-list associated with
the subnet entirely and hence router deletion fails.
OUTPUT:
VRRP : Enabled
neutron router-interface-add Router_test red-sub
Added interface 59963328-8174-4d50-ab5b-fd796e47d63f to router Router_test.
root@Ubu14-42-18:~# neutron router-port-list Router_test
+--+--+---+-+
| id | name | mac_address | fixed_ips
|
+--+--+---+-+
| 59963328-8174-4d50-ab5b-fd796e47d63f | | fa:16:3e:fb:23:ef |
{"subnet_id": "cc64f073-ffe5-4a2c-89f5-6415264c9ea6", "ip_address": "16.0.0.1"}
|
| | | |
{"subnet_id": "cc64f073-ffe5-4a2c-89f5-6415264c9ea6", "ip_address": "16.0.0.3"}
|
| | | |
{"subnet_id": "cc64f073-ffe5-4a2c-89f5-6415264c9ea6", "ip_address": "16.0.0.4"}
|
+--+--+---+-+
root@Ubu14-42-18:~# neutron router-interface-delete Router_test red-sub
Removed interface from router Router_test.
root@Ubu14-42-18:~# neutron router-port-list Router_test
+--+--+---+---+
| id | name | mac_address | fixed_ips
|
+--+--+---+---+
| 59963328-8174-4d50-ab5b-fd796e47d63f | | fa:16:3e:fb:23:ef |
|
+--+--+---+---+
root@Ubu14-42-18:~# neutron router-delete Router_test
Router 13c9c988-f415-4c12-804d-a3e495c6f0b3 still has ports
Neutron server returns request_ids:
['req-083e1c
[Yahoo-eng-team] [Bug 1583503] [NEW] L3 HA broken after network node crash
Public bug reported: After a crash of a network node, we were left with empty PID files for some keepalived processes: root@network-node14:~# ls -l /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid -rw-r--r-- 1 root root 0 May 19 08:41 /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid This causes the L3 agent to log the following errors repeating every minute: 2016-05-19 08:46:44.525 13554 ERROR neutron.agent.linux.utils [-] Unable to convert value in /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid 2016-05-19 08:46:44.526 13554 ERROR neutron.agent.linux.external_process [-] keepalived for router with uuid 0ab5f647-1e04-4345-ae9b-ee66c6f08882 not found. The process should not have died 2016-05-19 08:46:44.526 13554 WARNING neutron.agent.linux.external_process [-] Respawning keepalived for uuid 0ab5f647-1e04-4345-ae9b-ee66c6f08882 2016-05-19 08:46:44.526 13554 ERROR neutron.agent.linux.utils [-] Unable to convert value in /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid 2016-05-19 08:46:44.526 13554 ERROR neutron.agent.linux.utils [-] Unable to convert value in /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid-vrrp and the keepalived process fails to start. As a result, the routers hosted by this agent are non-functional. ** Affects: neutron Importance: Undecided Status: New ** Affects: keepalived (Ubuntu) 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/1583503 Title: L3 HA broken after network node crash Status in neutron: New Status in keepalived package in Ubuntu: New Bug description: After a crash of a network node, we were left with empty PID files for some keepalived processes: root@network-node14:~# ls -l /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid -rw-r--r-- 1 root root 0 May 19 08:41 /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid This causes the L3 agent to log the following errors repeating every minute: 2016-05-19 08:46:44.525 13554 ERROR neutron.agent.linux.utils [-] Unable to convert value in /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid 2016-05-19 08:46:44.526 13554 ERROR neutron.agent.linux.external_process [-] keepalived for router with uuid 0ab5f647-1e04-4345-ae9b-ee66c6f08882 not found. The process should not have died 2016-05-19 08:46:44.526 13554 WARNING neutron.agent.linux.external_process [-] Respawning keepalived for uuid 0ab5f647-1e04-4345-ae9b-ee66c6f08882 2016-05-19 08:46:44.526 13554 ERROR neutron.agent.linux.utils [-] Unable to convert value in /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid 2016-05-19 08:46:44.526 13554 ERROR neutron.agent.linux.utils [-] Unable to convert value in /var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid-vrrp and the keepalived process fails to start. As a result, the routers hosted by this agent are non-functional. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1583503/+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 1583504] [NEW] The instances which didn't be evacuated will be destroyed when the nova-compute service is restarted.
Public bug reported: Description === Normally, if you finished evacuating instance, nova-compute will destroy the existed instances whose state are "done" or "accept" in the migration table from the fault host after the nova-compute service is restarted. However, if the nova-scheduler failed to schedule the hosts, e.g. no valid host, nova-scheduler won't update the migration state of the instance to "failed", so that the nova-compute will destroy this instance after restarting by mistake. Steps to reproduce == 1. Create some instances in the the specific host. 2. Make this host to fault state. 3. Disable nova-compute service in other hosts, aim to mock that nova-scheduler fail to schedule. 4. Recover the fault host and restart nova-compute. 5. Check all instances are still existed in the kvm. Expected result === All instances should be still existed in the kvm. Actual result = All instances are destroyed by nova-compute unfortunately. ** Affects: nova Importance: Undecided Assignee: alex (chinabjalex) Status: New ** Changed in: nova Assignee: (unassigned) => alex (chinabjalex) -- 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/1583504 Title: The instances which didn't be evacuated will be destroyed when the nova-compute service is restarted. Status in OpenStack Compute (nova): New Bug description: Description === Normally, if you finished evacuating instance, nova-compute will destroy the existed instances whose state are "done" or "accept" in the migration table from the fault host after the nova-compute service is restarted. However, if the nova-scheduler failed to schedule the hosts, e.g. no valid host, nova-scheduler won't update the migration state of the instance to "failed", so that the nova-compute will destroy this instance after restarting by mistake. Steps to reproduce == 1. Create some instances in the the specific host. 2. Make this host to fault state. 3. Disable nova-compute service in other hosts, aim to mock that nova-scheduler fail to schedule. 4. Recover the fault host and restart nova-compute. 5. Check all instances are still existed in the kvm. Expected result === All instances should be still existed in the kvm. Actual result = All instances are destroyed by nova-compute unfortunately. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1583504/+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 1529012] Re: Miss policy checks in image panels
Reviewed: https://review.openstack.org/261967 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=340e67c17acf5957890c5ae3ec5f5c7216c20587 Submitter: Jenkins Branch:master commit 340e67c17acf5957890c5ae3ec5f5c7216c20587 Author: Bo Wang Date: Tue Apr 12 14:16:11 2016 +0800 Add policy checks in images panels check policy of getting images in: project/images project/ngimages admin/images Only block listing images but not whole panel if failed on policy check. Create, Delete and other actions are controlled by according policys. give a message "Insufficient privilege level to get images." to user if polciy checks failed. Closes-Bug: #1529012 Change-Id: I97ab081425dd56fa7c3208efb58ba8b041eaba24 ** 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/1529012 Title: Miss policy checks in image panels Status in OpenStack Dashboard (Horizon): Fix Released Bug description: There is no policy checking code in image panels: project/images, project/ngimages, admin/images. As ngusers code: https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/identity/static/dashboard/identity/users/table/table.controller.js#L54. We should add policy checks of "get_images" in image panels To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1529012/+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 1582541] Re: Segments: atrributes deprcation warning
Reviewed: https://review.openstack.org/317273
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=f0d99d54999f1cac75fc1b1280fa332798c9d175
Submitter: Jenkins
Branch:master
commit f0d99d54999f1cac75fc1b1280fa332798c9d175
Author: Gary Kotton
Date: Mon May 16 23:36:18 2016 -0700
Segment: remove deprecation warning for converters
Remove warning:
neutron.api.v2.attributes.convert_to_int()' has moved to
'neutron_lib.api.converters.convert_to_int()' in version
'mitaka' and will be removed in version 'ocata': moved to
neutron_lib
Change-Id: I0f6622b685a6b9ab030a13113badbefb729be013
Closes-bug: #1582541
** 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/1582541
Title:
Segments: atrributes deprcation warning
Status in neutron:
Fix Released
Bug description:
{2}
neutron.tests.unit.extensions.test_segment.TestSegment.test_create_segment_no_phys_net
[0.313844s] ... ok
Captured stderr:
neutron/api/v2/attributes.py:428: DeprecationWarning: Function
'neutron.api.v2.attributes.convert_to_int()' has moved to
'neutron_lib.api.converters.convert_to_int()' in version 'mitaka' and will be
removed in version 'ocata': moved to neutron_lib
res_dict[attr] = attr_vals['convert_to'](res_dict[attr])
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1582541/+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 1580056] Re: Default sort doesn't work in flavor table in ng-instance modal
*** This bug is a duplicate of bug 1433317 *** https://bugs.launchpad.net/bugs/1433317 Reviewed: https://review.openstack.org/314449 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=334f9d33f67ccde85470e62f3c80e40afb9ef2d8 Submitter: Jenkins Branch:master commit 334f9d33f67ccde85470e62f3c80e40afb9ef2d8 Author: Kenji Ishii Date: Tue May 10 16:44:31 2016 +0900 Modify default sort in flavor table in ng-instance Default sort on the flavor table is specified as RAM (only the case of available table). But at the moment, it doesn't work. It is caused by undefined variables (isAvailableTable). This variables seems to be a flag wheather a table is Allocated table or Available table. However, these tables are implemented separately. Thus, it doesn't need to use this variable. Therefore, this patch will remove the condition using this variable. Change-Id: I912850d352e547082bb25c5fced938d8cdc50dc9 Closes-Bug: #1580056 ** 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/1580056 Title: Default sort doesn't work in flavor table in ng-instance modal Status in OpenStack Dashboard (Horizon): Fix Released Bug description: In implementation, in ng-instance modal, default sort on the flavor table is specified as RAM (only the case of available table). But, at the moment, it doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1580056/+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 1583025] Re: Warning in extract_messages tox environment
Reviewed: https://review.openstack.org/317896 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=1d7e3885b2951b153746aec0b40517bf4b96f6b5 Submitter: Jenkins Branch:master commit 1d7e3885b2951b153746aec0b40517bf4b96f6b5 Author: Zhenguo Niu Date: Wed May 18 16:13:48 2016 +0800 Whitelist 'rm' in pep8 tox environment Running the pep8 environment currently warns that 'rm' is not installed in testenv. This patch removes the warning by whitelisting the rm command. Change-Id: I822195990d345ddd08237f9696651c71ad59b9d2 Closes-Bug: #1583025 ** 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/1583025 Title: Warning in extract_messages tox environment Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When running the pep8 tox environment the following warning is issued: WARNING:test command found but not installed in testenv cmd: /bin/rm env: /home/jenkins/workspace/gate-horizon-pep8/.tox/pep8 Maybe you forgot to specify a dependency? See also the whitelist_externals envconfig setting. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1583025/+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 1520321] Re: keystone-manage token_flush command fails
I also added keystone to this bug report. Running token_flush shouldn't fail like that, regardless if fernet is the token provider. At minimum, I think we could make keystone-manage catch the NotImplemented exception and log a warning message. ** Also affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1520321 Title: keystone-manage token_flush command fails Status in Fuel for OpenStack: Fix Released Status in OpenStack Identity (keystone): New Bug description: Description: === The token flush command fails on MOS 8.0 build #207 (launch by the crontab /etc/cron.hourly/keystone) To reproduce: = run this command on a controller node: su -c '/usr/bin/keystone-manage token_flush' keystone No handlers could be found for logger "oslo_config.cfg" Log: /var/log/keystone/keystone-manage.log 2015-11-26 17:13:39.145 670 WARNING oslo_log.versionutils [-] Deprecated: direct import of driver is deprecated as of Liberty in favor of entrypoints and may be removed in N. 2015-11-26 17:13:39.153 670 INFO keystone.common.kvs.core [-] Using default dogpile sha1_mangle_key as KVS region token-driver key_mangler 2015-11-26 17:13:39.156 670 CRITICAL keystone [-] NotImplemented: The action you have requested has not been implemented. 2015-11-26 17:13:39.156 670 ERROR keystone Traceback (most recent call last): 2015-11-26 17:13:39.156 670 ERROR keystone File "/usr/bin/keystone-manage", line 10, in 2015-11-26 17:13:39.156 670 ERROR keystone sys.exit(main()) 2015-11-26 17:13:39.156 670 ERROR keystone File "/usr/lib/python2.7/dist-packages/keystone/cmd/manage.py", line 47, in main 2015-11-26 17:13:39.156 670 ERROR keystone cli.main(argv=sys.argv, config_files=config_files) 2015-11-26 17:13:39.156 670 ERROR keystone File "/usr/lib/python2.7/dist-packages/keystone/cmd/cli.py", line 685, in main 2015-11-26 17:13:39.156 670 ERROR keystone CONF.command.cmd_class.main() 2015-11-26 17:13:39.156 670 ERROR keystone File "/usr/lib/python2.7/dist-packages/keystone/cmd/cli.py", line 244, in main 2015-11-26 17:13:39.156 670 ERROR keystone token_manager.flush_expired_tokens() 2015-11-26 17:13:39.156 670 ERROR keystone File "/usr/lib/python2.7/dist-packages/keystone/token/persistence/backends/kvs.py", line 356, in flush_expired_tokens 2015-11-26 17:13:39.156 670 ERROR keystone raise exception.NotImplemented() 2015-11-26 17:13:39.156 670 ERROR keystone NotImplemented: The action you have requested has not been implemented. 2015-11-26 17:13:39.156 670 ERROR keyston Expected result: no error To manage notifications about this bug go to: https://bugs.launchpad.net/fuel/+bug/1520321/+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 1550671] Re: The limit of injected file conetent length is incorrect
fix the docs, not the code, As discussion in the nova-api meeting [1]. That's why I'm setting the status to "invalid". [1] http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-03-08-12.00.log.html ** Changed in: nova Status: In Progress => Invalid ** Changed in: nova Assignee: kevin shen (kevin.shen) => (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/1550671 Title: The limit of injected file conetent length is incorrect Status in OpenStack Compute (nova): Invalid Bug description: According to http://developer.openstack.org/api-ref-compute-v2.1.html#createServer , the perameter personality has limits about path length and content length. And it is pointed out that the content should be base64 encoded string and the content length limit is the limit of base64 decoded raw data, not the base64 encoded data. But in the current implementation: https://github.com/openstack/nova/blob/master/nova/compute/api.py#L266-L277 we are checking the base64 encoded data. That is, for example, the quota limit for content length is 256, and user provided a file with the length of 256, exception.OnsetFileContentLimitExceeded error will rasie as after base64 encoding, the file length will grow. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1550671/+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
