[Yahoo-eng-team] [Bug 1328157] [NEW] ports not being deleted
Public bug reported: I have a /24 for my floating ips and a revolving set of users. I delete unused floating ips and clear router gatways regularly, but my ports don't clear and I start to get ip allocation errors for setting the gateway: Error: Failed to set gateway No more IP addresses available on network b418a23d-39fb-4d09-82ee-4a2768ea508b. Shouldn't these ports either be deleted when the associated resource is cleaned up or maybe be reuse to avoid this allocation error? [root@host3 ~]# neutron floatingip-list | wc -l 33 [root@host3 ~]# neutron router-list| grep -v null | wc -l 17 [root@host3 ~]# neutron port-list | grep | wc -l 223 [root@host4 ~]# rpm -qa | grep neutron python-neutronclient-2.3.4-1.el6.noarch openstack-neutron-2014.1-18.el6.noarch openstack-neutron-openvswitch-2014.1-18.el6.noarch python-neutron-2014.1-18.el6.noarch ** 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/1328157 Title: ports not being deleted Status in OpenStack Neutron (virtual network service): New Bug description: I have a /24 for my floating ips and a revolving set of users. I delete unused floating ips and clear router gatways regularly, but my ports don't clear and I start to get ip allocation errors for setting the gateway: Error: Failed to set gateway No more IP addresses available on network b418a23d-39fb-4d09-82ee-4a2768ea508b. Shouldn't these ports either be deleted when the associated resource is cleaned up or maybe be reuse to avoid this allocation error? [root@host3 ~]# neutron floatingip-list | wc -l 33 [root@host3 ~]# neutron router-list| grep -v null | wc -l 17 [root@host3 ~]# neutron port-list | grep | wc -l 223 [root@host4 ~]# rpm -qa | grep neutron python-neutronclient-2.3.4-1.el6.noarch openstack-neutron-2014.1-18.el6.noarch openstack-neutron-openvswitch-2014.1-18.el6.noarch python-neutron-2014.1-18.el6.noarch To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1328157/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1313720] [NEW] ipallocations not cleaned after floating ip delete
Public bug reported:
I have a limited floatingip pool for revolving set of users.
I have a script that will run a neutron floatingip-delete on IPs that are not
associated with an instance and a neutron router-gateway-clear on routers that
don't have any floatingips associated with them.
I was still getting the message "Error: Failed to set gateway No more IP
addresses available on network " when new users were trying to set the
gateway on their router.
My current workaround is to run a database query that selects the ips
from my floatingip pool that do not have an associated port and delete
the record.
delete from ipallocations where ip_address in (
select * from (
select ip_address from ipallocations left join ports on
ipallocations.port_id = ports.id
where ports.id is NULL and ip_address like '{3-octets-of-fip-pool}%'
) as p);
This restores capability to set gateways and allocate floating ips.
I'm running the RDO build of 2014.1
** 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/1313720
Title:
ipallocations not cleaned after floating ip delete
Status in OpenStack Neutron (virtual network service):
New
Bug description:
I have a limited floatingip pool for revolving set of users.
I have a script that will run a neutron floatingip-delete on IPs that are not
associated with an instance and a neutron router-gateway-clear on routers that
don't have any floatingips associated with them.
I was still getting the message "Error: Failed to set gateway No more
IP addresses available on network " when new users were trying to set
the gateway on their router.
My current workaround is to run a database query that selects the ips
from my floatingip pool that do not have an associated port and delete
the record.
delete from ipallocations where ip_address in (
select * from (
select ip_address from ipallocations left join ports on
ipallocations.port_id = ports.id
where ports.id is NULL and ip_address like '{3-octets-of-fip-pool}%'
) as p);
This restores capability to set gateways and allocate floating ips.
I'm running the RDO build of 2014.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1313720/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1319526] [NEW] Error: Unable to add user to primary project.
Public bug reported: when creating a new user and a new project through the create user dialog. the user and tenant is created successfuly but I also get the error "Error: Unable to add user to primary project." in the ui in the keystone logs I get an error like this: 2014-05-14 14:45:24.535 783 WARNING keystone.common.wsgi [-] Conflict occurred attempting to store role grant. User 617c72311afb445495a77030cdc84533 already has role 9fe2ff9ee4384b1894a90878d3e92bab in tenant fcfe0c2970224441b3319c98e6c07d5f 2014-05-14 14:45:24.535 783 INFO eventlet.wsgi.server [-] 192.168.123.101 - - [14/May/2014 14:45:24] "PUT /v2.0/tenants/fcfe0c2970224441b3319c98e6c07d5f/users/617c72311afb445495a77030cdc84533/roles/OS-KSADM/9fe2ff9ee4384b1894a90878d3e92bab HTTP/1.1" 409 375 0.011336 this doesn't block my use case. I am able to continue forward with using the user and the user has the proper role in it's tenant. Maybe just trying to add the user's role multiple times? ** 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/1319526 Title: Error: Unable to add user to primary project. Status in OpenStack Dashboard (Horizon): New Bug description: when creating a new user and a new project through the create user dialog. the user and tenant is created successfuly but I also get the error "Error: Unable to add user to primary project." in the ui in the keystone logs I get an error like this: 2014-05-14 14:45:24.535 783 WARNING keystone.common.wsgi [-] Conflict occurred attempting to store role grant. User 617c72311afb445495a77030cdc84533 already has role 9fe2ff9ee4384b1894a90878d3e92bab in tenant fcfe0c2970224441b3319c98e6c07d5f 2014-05-14 14:45:24.535 783 INFO eventlet.wsgi.server [-] 192.168.123.101 - - [14/May/2014 14:45:24] "PUT /v2.0/tenants/fcfe0c2970224441b3319c98e6c07d5f/users/617c72311afb445495a77030cdc84533/roles/OS-KSADM/9fe2ff9ee4384b1894a90878d3e92bab HTTP/1.1" 409 375 0.011336 this doesn't block my use case. I am able to continue forward with using the user and the user has the proper role in it's tenant. Maybe just trying to add the user's role multiple times? To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1319526/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1887815] [NEW] Neutron API - problem parsing semi-colon in Accept header
Public bug reported:
when GET is sent with “Accept: application/json; charset=utf-8”, we
receive the following Neutron error:
$ curl -s -H "Accept: application/json; charset=utf-8" -H "X-Auth-Token:
$OS_TOKEN" "http://10.240.50.25:9696/v2.0/networks"; | python -mjson.tool
{
"NeutronError": {
"detail": "",
"message": "The server could not comply with the request since
it is either malformed or otherwise incorrect.",
"type": "HTTPNotAcceptable"
}
}
This happens on core resources and not extension resources.
** Affects: neutron
Importance: Undecided
Assignee: Dan Radez (dradez)
Status: In Progress
** Changed in: neutron
Assignee: (unassigned) => Dan Radez (dradez)
** Changed in: neutron
Status: New => In Progress
** Bug watch added: github.com/Pylons/webob/issues #403
https://github.com/Pylons/webob/issues/403
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1887815
Title:
Neutron API - problem parsing semi-colon in Accept header
Status in neutron:
In Progress
Bug description:
when GET is sent with “Accept: application/json; charset=utf-8”, we
receive the following Neutron error:
$ curl -s -H "Accept: application/json; charset=utf-8" -H "X-Auth-Token:
$OS_TOKEN" "http://10.240.50.25:9696/v2.0/networks"; | python -mjson.tool
{
"NeutronError": {
"detail": "",
"message": "The server could not comply with the request since
it is either malformed or otherwise incorrect.",
"type": "HTTPNotAcceptable"
}
}
This happens on core resources and not extension resources.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1887815/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1683301] Re: python 3.5 support
We test with 3.6 and 3.8 now. This bug is no longer valid. ** 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/1683301 Title: python 3.5 support Status in neutron: Invalid Bug description: Bug to track support for python 3.5. From PTG etherpad (https://etherpad.openstack.org/p/neutron-ptg-pike- final): Support Python 3.5 - https://etherpad.openstack.org/p/ptg-pike- python35 - https://governance.openstack.org/tc/goals/pike/python35.html The goal suggests all unit/functional/integration jobs to pass on py35 and gate on it. How do we keep the job list stable and manageable? Do we duplicate each job, or start deprovisioning some py27 jobs? choose some jobs - tempest job, functional for some reason, on my machine, the fullstack tests were running under Python 3.5 nice! for tempest, we will need to pick a single existing full job (at least) and switch it to py3, preferrably -nv so that it's safer to switch without lockstep changes in project-config look into project-config for job definitions for stadium py35 jobs To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1683301/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1775758] Re: Deprecated auth_url entries in Neutron Queen's install guide
Review has merged ** 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/1775758 Title: Deprecated auth_url entries in Neutron Queen's install guide Status in neutron: Fix Released Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: The Neutron installation guides use old auth_uri / auth_url values pointing at two different keystone endpoints for authentication of the network service and the compute service. This occurs within the controller node and compute node parts of the installation guide. Following the current guide then fails at the Verify step with error "Failed to retrieve extensions list from Network API" - [x] I have a fix to the document that I can paste below including example: input and output. input 1 (neutron.conf): auth_uri = http://controller:5000 auth_url = http://controller:35357 input 2 (nova.conf): auth_url = http://controller:35357 output: auth_url = http://controller:5000 I changed the values to the above output and the Verify step succeeded. --- Release: 12.0.3.dev24 on 2018-06-07 22:47 SHA: 2206636feca043a9ab958010a00641f92957e8a5 Source: https://git.openstack.org/cgit/openstack/neutron/tree/doc/source/install/controller-install-ubuntu.rst URL: https://docs.openstack.org/neutron/queens/install/controller-install-ubuntu.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1775758/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1813938] Re: When try to install oslo.log in CygWin 64bits failed pyinotify dependency
** 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/1813938 Title: When try to install oslo.log in CygWin 64bits failed pyinotify dependency Status in neutron: Invalid Status in oslo.log: New Bug description: Hi, When I install in CygWin 64 bits a package that has dependency for oslo.log, then failed: pip install -v --upgrade python-neutronclient Exist a workaroud for this, or howto fix it? Fails with the following error: ... Collecting pyinotify>=0.9.6; sys_platform != "win32" and sys_platform != "darwin" and sys_platform != "sunos5" (from oslo.log>=3.36.0->python-neutronclient) 1 location(s) to search for versions of pyinotify: * https://pypi.org/simple/pyinotify/ Getting page https://pypi.org/simple/pyinotify/ Looking up "https://pypi.org/simple/pyinotify/"; in the cache Request header has "max_age" as 0, cache bypassed https://pypi.org:443 "GET /simple/pyinotify/ HTTP/1.1" 304 0 Analyzing links from page https://pypi.org/simple/pyinotify/ Found link https://files.pythonhosted.org/packages/40/54/6a5c5dee4f4393098cc56329fbc724c1c39389f8164a1b14c031d59937f3/pyinotify-0.9.0.tar.gz#sha256=af1f7d22067010cf29dd35fe17f8715f816f026c4ed769f7383fd419d4af9fd6 (from https://pypi.org/simple/pyinotify/), version: 0.9.0 Found link https://files.pythonhosted.org/packages/c0/05/f0da2dc60f1aa61fc65cd5b0cca8befeef3f0622b193fcf9a90e018a552a/pyinotify-0.9.1.tar.gz#sha256=dd0eac2bd0172502ca35e976cbefa34359d0d795f29572993611dc1b98554838 (from https://pypi.org/simple/pyinotify/), version: 0.9.1 Found link https://files.pythonhosted.org/packages/45/7b/4c72ff5282ceb9ef658579529081a859b71cef7170ce613cb01fc391dd0f/pyinotify-0.9.2.tar.gz#sha256=61f382e2b4cd04e05b8bf871393a3697dbf0e3934129c377c05b959038d26fb4 (from https://pypi.org/simple/pyinotify/), version: 0.9.2 Found link https://files.pythonhosted.org/packages/48/01/988afd71e5fca5a7303a8e1dafce0cf4659c1b593c4a76e788e4e76fc7de/pyinotify-0.9.3.tar.gz#sha256=447b01feaf25a2ad36e4101b583a8212bd701d5c34e330dd62dd9f32ba149aa6 (from https://pypi.org/simple/pyinotify/), version: 0.9.3 Found link https://files.pythonhosted.org/packages/69/bd/a55a13103b6672eeff7919932c3caf573b6c97ffa1ef69a02064760eb08d/pyinotify-0.9.4.tar.gz#sha256=a09767e4e0610e2e1e9f9dc89483b0ee4a53764e700f5866a570bec51d003fec (from https://pypi.org/simple/pyinotify/), version: 0.9.4 Found link https://files.pythonhosted.org/packages/89/34/8574ec4c7d3a9fa74e7bd6b55c4d2c182cc91861f99516dab650e43992cc/pyinotify-0.9.5.tar.gz#sha256=e7c52a9f36cee27c5d0931ecf92959cd022317b00901bd34ef05ece4a2a5cb1b (from https://pypi.org/simple/pyinotify/), version: 0.9.5 Found link https://files.pythonhosted.org/packages/e3/c0/fd5b18dde17c1249658521f69598f3252f11d9d7a980c5be8619970646e1/pyinotify-0.9.6.tar.gz#sha256=9c998a5d7606ca835065cdabc013ae6c66eb9ea76a00a1e3bc6e0cfe2b4f71f4 (from https://pypi.org/simple/pyinotify/), version: 0.9.6 Using version 0.9.6 (newest of versions: 0.9.6) Created temporary directory: /tmp/pip-unpack-0rKHMk Looking up "https://files.pythonhosted.org/packages/e3/c0/fd5b18dde17c1249658521f69598f3252f11d9d7a980c5be8619970646e1/pyinotify-0.9.6.tar.gz"; in the cache Current age based on date: 8466 Ignoring unknown cache-control directive: immutable Freshness lifetime from max-age: 36500 The response is "fresh", returning cached response 36500 > 8466 Using cached https://files.pythonhosted.org/packages/e3/c0/fd5b18dde17c1249658521f69598f3252f11d9d7a980c5be8619970646e1/pyinotify-0.9.6.tar.gz Downloading from URL https://files.pythonhosted.org/packages/e3/c0/fd5b18dde17c1249658521f69598f3252f11d9d7a980c5be8619970646e1/pyinotify-0.9.6.tar.gz#sha256=9c998a5d7606ca835065cdabc013ae6c66eb9ea76a00a1e3bc6e0cfe2b4f71f4 (from https://pypi.org/simple/pyinotify/) Added pyinotify>=0.9.6; sys_platform != "win32" and sys_platform != "darwin" and sys_platform != "sunos5" from https://files.pythonhosted.org/packages/e3/c0/fd5b18dde17c1249658521f69598f3252f11d9d7a980c5be8619970646e1/pyinotify-0.9.6.tar.gz#sha256=9c998a5d7606ca835065cdabc013ae6c66eb9ea76a00a1e3bc6e0cfe2b4f71f4 (from oslo.log>=3.36.0->python-neutronclient) to build tracker '/tmp/pip-req-tracker-aPlTWG' Running setup.py (path:/tmp/pip-install-R1uixM/pyinotify/setup.py) egg_info for package pyinotify Running command python setup.py egg_info inotify is not available on cygwin-2.11.2-x86_64 Cleaning up... Removing source in /tmp/pip-install-R1uixM/pyinotify Removed pyinotify>=0.9.6; sys_platform != "win32" and sys_platform != "darwin" and sys_platform != "sunos5" from https://files.pythonhosted.org/packages/e3/c0/fd5b18dde17c1249658521f69598f3252f11d9d7a980c5be8619970646e1/pyinotify-0.9.6.tar.gz#sha256=9c998a
