[Yahoo-eng-team] [Bug 1943881] [NEW] Server concepts in Compute API Guide
Public bug reported: Suspend, Resume section has confusing meaning explaining when VCPUs are available. "Suspending a server is similar to placing a device in hibernation; memory and vCPUs become available to create other servers." When VM is shutdown, it stays on a server. Its allocation is hold against an allocation of the server. Placement counts all VCPUs, for active and inactive VMs. 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: __ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - The mailing list: https://lists.openstack.org - IRC: 'openstack' channel on OFTC --- Release: 2.1.0 on 2021-09-10 23:30:23 SHA: dc18853c316e1a7d74b99183b8f06e8d81a8f6c9 Source: https://opendev.org/openstack/nova/src/api-guide/source/server_concepts.rst URL: https://docs.openstack.org/api-guide/compute/server_concepts.html ** Affects: nova Importance: Undecided Status: New ** Tags: api-guide -- 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/1943881 Title: Server concepts in Compute API Guide Status in OpenStack Compute (nova): New Bug description: Suspend, Resume section has confusing meaning explaining when VCPUs are available. "Suspending a server is similar to placing a device in hibernation; memory and vCPUs become available to create other servers." When VM is shutdown, it stays on a server. Its allocation is hold against an allocation of the server. Placement counts all VCPUs, for active and inactive VMs. 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: __ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - The mailing list: https://lists.openstack.org - IRC: 'openstack' channel on OFTC --- Release: 2.1.0 on 2021-09-10 23:30:23 SHA: dc18853c316e1a7d74b99183b8f06e8d81a8f6c9 Source: https://opendev.org/openstack/nova/src/api-guide/source/server_concepts.rst URL: https://docs.openstack.org/api-guide/compute/server_concepts.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1943881/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1681784] Re: neutronclient: incorrect treatment of input parameters
** Also affects: python-neutronclient
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/1681784
Title:
neutronclient: incorrect treatment of input parameters
Status in neutron:
New
Status in python-neutronclient:
New
Bug description:
Hi colleagues,
Neutron 10.0.0 (as part Ocata) on Ubuntu 16.04
Everything is ok when I use Neutron CLI to update port parameters, but
when I'm doing the same using Heat, it fails.
Heat's template for the object is:
e-secgroup:
type: OS::Neutron::SecurityGroup
properties:
name: SSH_ICMP
rules:
- direction: ingress
- protocol: tcp
remote_ip_prefix: 0.0.0.0/0
port_range_min: 22
port_range_max: 22
- protocol: icmp
remote_ip_prefix: 0.0.0.0/0
node1-wan:
type: OS::Neutron::Port
properties:
name: jadm-node1-wan
network: e-net
port_security_enabled: True
security_groups: [ default, { get_resource: e-secgroup } ]
Heat makes a call to Neutron using neutronclient and provides input
parameters in such way:
updating port with {'allowed_address_pairs': [], 'binding:vnic_type':
None, 'device_owner': None, 'mac_address': None, 'security_groups': [u
'53ede63e-b08f-4c95-b5fe-29cd21ed442a', u'0a48c45e-5a6d-
4b80-8226-08d2e8c5bb00'], 'device_id': None} handle_update
/usr/lib/python2.7/dist-
packages/heat/engine/resources/openstack/neutron/port.py:520
In return, I get the following error:
2017-04-11 09:51:31.809 14474 DEBUG neutronclient.v2_0.client [req-
54a51260-8701-4f94-9141-562443a3ad7e - bush - - -] Error message:
{"NeutronError": {"message": "Invalid input for device_owner. Reason:
'None' is not a valid string.", "type": "HTTPBadRequest", "detail":
""}} _handle_fault_response /usr/lib/python2.7/dist-
packages/neutronclient/v2_0/client.py:266
If I explicitly set device_owner='' in Heat template, then
neutronclient accepts this key-value pair and returns error for the
next parameter (e.g. device_id):
2017-04-11 10:45:26.808 14474 DEBUG neutronclient.v2_0.client [req-
3f5c1c53-bec4-418f-bc0e-e04b23474c0e - bush - - -] Error message:
{"NeutronError": {"message": "Invalid input for device_id. Reason:
'None' is not a valid string.", "type": "HTTPBadRequest", "detail":
""}} _handle_fault_response /usr/lib/python2.7/dist-
packages/neutronclient/v2_0/client.py:266
and this affects not only parameters of OS::Neutron::Port object, but
OS::Neutron::SecurityGroup's ones as well:
Resource UPDATE failed: BadRequest: resources.e-secgroup: Invalid
input for description. Reason: 'None' is not a valid string. Neutron
server returns request_ids: ['req-287db7f6-06be-4bc8-a11b-
94be203c67da']
So, the problem is general and it seems that something wrong with
treatment of 'None' in input parameters: all clients should always
treat None values the same as not passing any value, while
neutronclient accepts '' and refuses None.
Severity: this bug blocks using Heat.
Thank you.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1681784/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1680272] Re: several tempest tests failed in gate because of libvirt error
This one rather looks like possible nova issue. ** Project changed: neutron => nova -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1680272 Title: several tempest tests failed in gate because of libvirt error Status in OpenStack Compute (nova): New Bug description: Hope I I got the target project right - could not decide whether it should be nova (as the error is with libvirt and n-cpu) or neutron (as long as it was observed in the gate). tempest.api.compute.servers.test_delete_server.DeleteServersTestJSON.test_delete_server_while_in_pause_state [8.822468s] ... FAILED tempest.api.compute.servers.test_create_server.ServersTestJSON.test_verify_multiple_nics_order [17.369368s] ... FAILED tempest.api.compute.admin.test_volume_swap.TestVolumeSwap.test_volume_swap [410.785118s] ... FAILED Full log - http://logs.openstack.org/55/453355/3/check/gate-tempest- dsvm-neutron-linuxbridge-ubuntu- xenial/5fa5aea/logs/screen-n-cpu.txt.gz Except from n-cpu.log - http://paste.openstack.org/show/605578/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1680272/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1680136] Re: Stable newton gate is broken
** Project changed: networking-midonet => neutron
** Changed in: neutron
Status: New => Confirmed
** Changed in: neutron
Importance: Undecided => Critical
** 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/1680136
Title:
Stable newton gate is broken
Status in neutron:
Confirmed
Bug description:
Stable newton branch is busted.
https://review.openstack.org/#/c/445326/
Py27 and Py35 tests are passing for checks [1] but failing for gate
[2]
[1]
http://logs.openstack.org/26/445326/2/check/gate-networking-midonet-python27-ubuntu-xenial/57c3b39/testr_results.html.gz
[2]
http://logs.openstack.org/26/445326/2/gate/gate-networking-midonet-python27-ubuntu-xenial/5ce12db/testr_results.html.gz
ft21.80:
midonet.neutron.tests.unit.test_midonet_plugin.TestMidonetL3NatDBIntTest.test_floatingip_list_with_pagination_reverse_StringException:
Empty attachments:
stderr
stdout
pythonlogging:'': {{{
WARNING [stevedore.named] Could not load
midonet.neutron.plugin_v1.MidonetPluginV2
WARNING [neutron.api.extensions] Extension address-scope not supported by
any of loaded plugins
WARNING [neutron.api.extensions] Extension allowed-address-pairs not
supported by any of loaded plugins
WARNING [neutron.api.extensions] Extension auto-allocated-topology not
supported by any of loaded plugins
WARNING [neutron.api.extensions] Extension availability_zone not supported
by any of loaded plugins
WARNING [neutron.api.extensions] Extension default-subnetpools not supported
by any of loaded plugins
WARNING [neutron.api.extensions] Extension dns-integration not supported by
any of loaded plugins
WARNING [neutron.api.extensions] Extension dvr not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension extraroute not supported by any
of loaded plugins
WARNING [neutron.api.extensions] Extension flavors not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension ip_allocation not supported by
any of loaded plugins
WARNING [neutron.api.extensions] Extension l2_adjacency not supported by any
of loaded plugins
WARNING [neutron.api.extensions] Extension l3-ha not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension l3-flavors not supported by any
of loaded plugins
WARNING [neutron.api.extensions] Extension l3_agent_scheduler not supported
by any of loaded plugins
WARNING [neutron.api.extensions] Extension metering not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension multi-provider not supported by
any of loaded plugins
WARNING [neutron.api.extensions] Extension net-mtu not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension network_availability_zone not
supported by any of loaded plugins
WARNING [neutron.api.extensions] Extension network-ip-availability not
supported by any of loaded plugins
WARNING [neutron.api.extensions] Extension port-security not supported by
any of loaded plugins
WARNING [neutron.api.extensions] Extension provider not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension qos not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension standard-attr-revisions not
supported by any of loaded plugins
WARNING [neutron.api.extensions] Extension router_availability_zone not
supported by any of loaded plugins
WARNING [neutron.api.extensions] Extension router-service-type not supported
by any of loaded plugins
WARNING [neutron.api.extensions] Extension segment not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension service-type not supported by any
of loaded plugins
WARNING [neutron.api.extensions] Extension subnet-service-types not
supported by any of loaded plugins
WARNING [neutron.api.extensions] Extension tag not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension standard-attr-timestamp not
supported by any of loaded plugins
WARNING [neutron.api.extensions] Extension trunk not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension trunk-details not supported by
any of loaded plugins
WARNING [neutron.api.extensions] Extension vlan-transparent not supported by
any of loaded plugins
ERROR [neutron.api.extensions] Extension path
'neutron/tests/unit/extensions' doesn't exist!
WARNING [neutron.api.extensions] Extension agent-membership not supported by
any of loaded plugins
WARNING [neutron.api.extensions] Extension bgp-speaker-router-insertion not
supported by any of loaded plugins
WARNING [neutron.api.extensions] Extension gateway-device not supported by
any of loaded plugins
WARNING [neutron.api.extensions] Exten
[Yahoo-eng-team] [Bug 1672590] Re: Port idlutils.get_schema_helper from ovsdbapp to neutron
Please continue work on https://bugs.launchpad.net/neutron/+bug/1674889 ** Changed in: neutron Status: In Progress => Invalid ** Changed in: neutron Assignee: Dong Jun (dongj) => (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/1672590 Title: Port idlutils.get_schema_helper from ovsdbapp to neutron Status in neutron: Invalid Bug description: There is a fatal error in networking-ovn in some case[1], so I port the new idlutils.get_schema_helper from ovsdbapp to neutron and add some unit test. [1] https://bugs.launchpad.net/networking-ovn/+bug/1674889 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1672590/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1674889] Re: Fix get_schema_helper bug in some case
** Also affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1674889 Title: Fix get_schema_helper bug in some case Status in networking-ovn: New Status in neutron: New Bug description: When thread of ovn ovsdb-server is not present, then start or restart neutron-server, manager was set to openvswitch. Neutron-server can no longer connect to ovn ovsdb for occupied port 6642 unless delete manager manually. Manager "ptcp:6642:10.157.0.159" Bridge br-int fail_mode: secure This is not a bug that always exists, it's caused by some neutron recent modification. I submit a bug[1] in neutorn a few days ago, then I get from terry wilson that ovsdb native API in neutron with be replaced by ovsapp in this cycle, so I dropped that patch and will fix this bug in networking-ovn by a simple change, using idlutils._get_schema_helper instead of idlutils.get_schema_helper. [1] https://bugs.launchpad.net/neutron/+bug/1672590 To manage notifications about this bug go to: https://bugs.launchpad.net/networking-ovn/+bug/1674889/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1674614] Re: LBaaS v2 lack of migration
** Project changed: neutron => octavia -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1674614 Title: LBaaS v2 lack of migration Status in octavia: New Bug description: = Problem Description = Currently, many users used haproxy driver based LBaaS v2 in real production. LBaaS network traffic will break down if LBaaS v2 agent is dead. So we need migration of LBaaS instance. = How to resolve = We can add create / delete method in LBaaS agent schedule. And we need to record device driver which LBaaS instance used. So, we can migrate LBaaS instance to another LBaaS agent when one of LBaaS agent is dead. To manage notifications about this bug go to: https://bugs.launchpad.net/octavia/+bug/1674614/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1672211] Re: Lbaasv2 - Could not load neutron_lbaas.services.loadbalancer.plugin.LoadBalancerPlugin
** Project changed: neutron => octavia
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1672211
Title:
Lbaasv2 - Could not load
neutron_lbaas.services.loadbalancer.plugin.LoadBalancerPlugin
Status in octavia:
New
Bug description:
Hi,
i'm trying to install lbaas for my openstack. Im on ubuntu16.04 Openstack
Newton with 3 node OVS deploy.
Following this guide for lbaas
https://docs.openstack.org/ocata/networking-guide/config-lbaas.html
controller node
aptitude search neutron-lbaas
p neutron-lbaas-agent
- Neutron is a virtual network service for
Openstack - LBaaS agent
i A neutron-lbaas-common
- Neutron is a virtual network service for
Openstack - common
i neutron-lbaasv2-agent
- Neutron is a virtual network service for
Openstack - LBaaSv2 agent
i A python-neutron-lbaas
- Loadbalancer-as-a-Service driver for
OpenStack Neutron
so neutron-lbaas-common neutron-lbaasv2-agent python-neutron-lbaas are
installed.
/etc/neutron/neutron.conf
[DEFAULT]
debug= true
core_plugin = ml2
service_plugins =
router,neutron_lbaas.services.loadbalancer.plugin.LoadBalancerPluginv2
allow_overlapping_ips = True
dhcp_agents_per_network = 1
transport_url = rabbit://openstack:mjvnzq8@controller
auth_strategy = keystone
notify_nova_on_port_status_changes = True
notify_nova_on_port_data_changes = True
core_plugin = ml2
[agent]
root_helper = sudo /usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf
[cors]
[cors.subdomain]
[database]
connection = mysql+pymysql://neutron:mjvnzq8@controller/neutron
[keystone_authtoken]
auth_uri = http://controller:5000
auth_url = http://controller:35357
memcached_servers = controller:11211
auth_type = password
project_domain_name = default
user_domain_name = default
project_name = service
username = neutron
password = *
[matchmaker_redis]
[nova]
auth_url = http://controller:35357
auth_type = password
project_domain_name = default
user_domain_name = default
region_name = RegionOne
project_name = service
username = nova
password = *
[oslo_concurrency]
[oslo_messaging_amqp]
[oslo_messaging_notifications]
[oslo_messaging_rabbit]
[oslo_messaging_zmq]
[oslo_policy]
[qos]
[quotas]
[ssl]
[service_providers]
service_provider =
LOADBALANCERV2:Haproxy:neutron_lbaas.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default
/etc/neutron/neutron_lbaas.conf
[service_providers]
service_provider =
LOADBALANCERV2:Haproxy:neutron_lbaas.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default
So that is the server side, after i restart it wont work anymore because it
cant load the lbaas driver
/var/log/neutron/neutron-server.log
2017-03-12 20:55:16.464 769 INFO neutron.common.config [-] Logging enabled!
2017-03-12 20:55:16.464 769 INFO neutron.common.config [-]
/usr/bin/neutron-server version 9.0.0
2017-03-12 20:55:16.464 769 INFO neutron.common.config [-] Logging enabled!
2017-03-12 20:55:16.465 769 INFO neutron.common.config [-]
/usr/bin/neutron-server version 9.0.0
2017-03-12 20:55:16.473 769 INFO neutron.manager [-] Loading core plugin: ml2
2017-03-12 20:55:16.669 769 INFO neutron.plugins.ml2.managers [-] Configured
type driver names: ['flat', 'vlan', 'vxlan']
2017-03-12 20:55:16.678 769 INFO neutron.plugins.ml2.drivers.type_flat [-]
Allowable flat physical_network names: ['provider']
2017-03-12 20:55:16.681 769 INFO neutron.plugins.ml2.drivers.type_vlan [-]
Network VLAN ranges: {'provider': []}
2017-03-12 20:55:16.684 769 INFO neutron.plugins.ml2.managers [-] Loaded type
driver names: ['flat', 'vlan', 'vxlan']
2017-03-12 20:55:16.684 769 INFO neutron.plugins.ml2.managers [-] Registered
types: ['flat', 'vlan', 'vxlan']
2017-03-12 20:55:16.685 769 INFO neutron.plugins.ml2.managers [-] Tenant
network_types: ['vxlan']
2017-03-12 20:55:16.685 769 INFO neutron.plugins.ml2.managers [-] Configured
extension driver names: ['port_security']
2017-03-12 20:55:16.689 769 INFO neutron.plugins.ml2.managers [-] Loaded
extension driver names: ['port_security']
2017-03-12 20:55:16.690 769 INFO neutron.plugins.ml2.managers [-] Registered
extension drivers: ['port_security']
2017-03-12 20:55:16.690 769 INFO neutron.plugins.ml2.managers [-] Configured
mechanism driver names:
[Yahoo-eng-team] [Bug 1551583] Re: Updating the segmentation id of network is failed
** Changed in: neutron Status: New => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1551583 Title: Updating the segmentation id of network is failed Status in neutron: Opinion Bug description: The users do not have a way to change the segmentation id when Network which network_type is vlan has been created. When trying to update the segmentation id of network ,such as "neutron net-update --provider:segmentation_id=1020 my_network", there is a prompting to tell us that "Invalid input for operation: Plugin does not support updating provider attributes." That meanings if the user changes the networking scheme,they have to delete all the vm , port and rebuild network with new segmentation id. That is too hard for the user. In some case the user don't allowed to delete the vm when they are using it. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1551583/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1550559] Re: Qos policy RBAC DB setup and migration
** Also affects: openstack-manuals Importance: Undecided Status: New ** Changed in: openstack-manuals 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/1550559 Title: Qos policy RBAC DB setup and migration Status in neutron: Invalid Status in openstack-api-site: Confirmed Status in openstack-manuals: Confirmed Bug description: https://review.openstack.org/250081 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 aeaf77a5295080a3010a2e9c32e24f47c8cc73cc Author: Haim Daniel Date: Wed Nov 25 18:49:45 2015 -0500 Qos policy RBAC DB setup and migration This patch implements a new database model required for the qos-policy RBAC support. In addition it migrates the current qos-policy 'shared' attribute to leverage the new 'qospolicyrbacs' table. 'shared' is no longer a property of the QosPolicy DB model. Its status is based on the tenant ID of the API caller. From an API perspective the logic remains the same - tenants will see qos-policies as 'shared=True' in case the qos-policy is shared with them). However, internal callers (e.g. plugins, drivers, services) must not check for the 'shared' attribute on qos-policy db objects any more. DocImpact APIImpact Blueprint: rbac-qos Related-bug: #1512587 Change-Id: I1c59073daa181005a3e878bc2fe033a0709fbf31 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1550559/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1551368] Re: L7 capability extension implementation for lbaas v2
** Also affects: openstack-api-site Importance: Undecided Status: New ** Changed in: openstack-api-site 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/1551368 Title: L7 capability extension implementation for lbaas v2 Status in neutron: Invalid Status in openstack-api-site: Confirmed Status in openstack-manuals: Confirmed Bug description: https://review.openstack.org/148232 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit 254190b3051453f823dbdf1826f1a6b984c57164 Author: Evgeny Fedoruk Date: Mon Jan 19 03:47:39 2015 -0800 L7 capability extension implementation for lbaas v2 Including extension modifications Including db model modifications Including alembic migration Including new driver managers for l7 rules and policies Inclufing logging_noop driver implementation Including unit testing Including Octavia driver updates DocImpact APIImpact Change-Id: I8f9535ebf28155adf43ebe046d2dbdfa86c4d81b Implements: blueprint lbaas-l7-rules Co-Authored-By: Evgeny Fedoruk Co-Authored-By: Stephen Balukoff To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1551368/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1550559] Re: Qos policy RBAC DB setup and migration
** Also affects: openstack-api-site Importance: Undecided Status: New ** Changed in: neutron Status: New => Invalid ** Changed in: openstack-api-site 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/1550559 Title: Qos policy RBAC DB setup and migration Status in neutron: Invalid Status in openstack-api-site: Confirmed Bug description: https://review.openstack.org/250081 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 aeaf77a5295080a3010a2e9c32e24f47c8cc73cc Author: Haim Daniel Date: Wed Nov 25 18:49:45 2015 -0500 Qos policy RBAC DB setup and migration This patch implements a new database model required for the qos-policy RBAC support. In addition it migrates the current qos-policy 'shared' attribute to leverage the new 'qospolicyrbacs' table. 'shared' is no longer a property of the QosPolicy DB model. Its status is based on the tenant ID of the API caller. From an API perspective the logic remains the same - tenants will see qos-policies as 'shared=True' in case the qos-policy is shared with them). However, internal callers (e.g. plugins, drivers, services) must not check for the 'shared' attribute on qos-policy db objects any more. DocImpact APIImpact Blueprint: rbac-qos Related-bug: #1512587 Change-Id: I1c59073daa181005a3e878bc2fe033a0709fbf31 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1550559/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1538767] Re: Users cannot create extra-routes with nexthop on ext-net
** Changed in: openstack-api-site
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/1538767
Title:
Users cannot create extra-routes with nexthop on ext-net
Status in neutron:
Fix Released
Status in openstack-api-site:
Invalid
Bug description:
Non-admin users cannot create extra-routes on a router with a nexthop
on ext-net subnet:
# With admin user
neutron net-create pub --router-:external
neutron subnet-create pub 192.168.0.0/16
# With non-admin user
neutron router-create router
neutron router-gateway-set router pub
neutron router-update router --routes
nexthop=192.168.0.99,destination=10.10.10.0/24
>> Invalid format for routes: [{u'destination': u'10.10.10.0/24',
u'nexthop': u'192.168.0.99'}], the nexthop is not connected with router
But it succeeds with an admin user.
nexthop validation gets all ports connected to the router to check if
nexthop is on a subnet connected to the router BUT non-admin users are
only allowed to get internal ports!
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1538767/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1538767] Re: Users cannot create extra-routes with nexthop on ext-net
** Also affects: openstack-api-site
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1538767
Title:
Users cannot create extra-routes with nexthop on ext-net
Status in neutron:
Fix Released
Status in openstack-api-site:
New
Bug description:
Non-admin users cannot create extra-routes on a router with a nexthop
on ext-net subnet:
# With admin user
neutron net-create pub --router-:external
neutron subnet-create pub 192.168.0.0/16
# With non-admin user
neutron router-create router
neutron router-gateway-set router pub
neutron router-update router --routes
nexthop=192.168.0.99,destination=10.10.10.0/24
>> Invalid format for routes: [{u'destination': u'10.10.10.0/24',
u'nexthop': u'192.168.0.99'}], the nexthop is not connected with router
But it succeeds with an admin user.
nexthop validation gets all ports connected to the router to check if
nexthop is on a subnet connected to the router BUT non-admin users are
only allowed to get internal ports!
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1538767/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1551368] Re: L7 capability extension implementation for lbaas v2
** 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/1551368 Title: L7 capability extension implementation for lbaas v2 Status in neutron: Invalid Status in openstack-manuals: Confirmed Bug description: https://review.openstack.org/148232 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit 254190b3051453f823dbdf1826f1a6b984c57164 Author: Evgeny Fedoruk Date: Mon Jan 19 03:47:39 2015 -0800 L7 capability extension implementation for lbaas v2 Including extension modifications Including db model modifications Including alembic migration Including new driver managers for l7 rules and policies Inclufing logging_noop driver implementation Including unit testing Including Octavia driver updates DocImpact APIImpact Change-Id: I8f9535ebf28155adf43ebe046d2dbdfa86c4d81b Implements: blueprint lbaas-l7-rules Co-Authored-By: Evgeny Fedoruk Co-Authored-By: Stephen Balukoff To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1551368/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1549078] Re: neutron router static routes ecmp deesn't work
** Changed in: neutron
Status: New => Incomplete
** Changed in: neutron
Status: Incomplete => Won't Fix
** Changed in: neutron
Status: Won't Fix => Confirmed
** 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/1549078
Title:
neutron router static routes ecmp deesn't work
Status in neutron:
Confirmed
Bug description:
Create 1 router and set gateway network, then create 2 static routes with
same prefix.
~/devstack$ neutron router-show R2
+-++
| Field | Value
|
+-++
| admin_state_up | True
|
| availability_zone_hints |
|
| availability_zones | nova
|
| distributed | False
|
| external_gateway_info | {"network_id":
"d5d571b9-c7c2-443f-8591-7da9d40435a7", "enable_snat": true,
"external_fixed_ips": [{"subnet_id": "4d033b6c-9a05-4aee-8462-ac909f86aa86",
"ip_address": "172.16.3.3"}]} |
| ha | False
|
| id | 1b2467b2-3b83-45bb-90e1-4d78c781d275
|
| name| R2
|
| routes | {"destination": "1.1.1.0/24", "nexthop":
"172.16.3.100"}
|
| | {"destination": "1.1.1.0/24", "nexthop":
"172.16.3.101"}
|
| status | ACTIVE
|
| tenant_id | d1694a63f75a422b9c83e0693effa482
|
+-++
~/devstack$ sudo ip netns exec qrouter-1b2467b2-3b83-45bb-90e1-4d78c781d275
ip neighbor show
172.16.3.101 dev qg-4515a36e-77 lladdr 00:00:01:00:00:02 PERMANENT
172.16.3.100 dev qg-4515a36e-77 lladdr 00:00:01:00:00:01 PERMANENT
fe80::f816:3eff:fe8e:a49f dev qg-4515a36e-77 lladdr fa:16:3e:8e:a4:9f STALE
fe80::5863:baff:fefe:c15e dev qg-4515a36e-77 lladdr 5a:63:ba:fe:c1:5e STALE
~/devstack$ sudo ip netns exec qrouter-1b2467b2-3b83-45bb-90e1-4d78c781d275
ip route
default via 172.16.3.1 dev qg-4515a36e-77
1.1.1.0/24 via 172.16.3.101 dev qg-4515a36e-77 ###ONLY 2nd route
is installed.
172.16.3.0/24 dev qg-4515a36e-77 proto kernel scope link src 172.16.3.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1549078/+subscriptions
--
Mailing list:
[Yahoo-eng-team] [Bug 1549886] Re: a bug test
** 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/1549886 Title: a bug test Status in neutron: Invalid Bug description: a bug test To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1549886/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1549634] Re: net-create missing mtu option
*** This bug is a duplicate of bug 1549638 *** https://bugs.launchpad.net/bugs/1549638 @Marcus, added second project to your another bug report. ** Also affects: neutron Importance: Undecided Status: New ** No longer affects: neutron ** This bug has been marked a duplicate of bug 1549638 no option to set network mtu -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1549634 Title: net-create missing mtu option Status in python-neutronclient: New Bug description: This spec has been implemented in kilo, but the neutron client does not yet have the option to set the mtu on network creation: https://specs.openstack.org/openstack/neutron-specs/specs/kilo/mtu- selection-and-advertisement.html It would be good to have the option to do this, as one currently needs to modify the database manually. To manage notifications about this bug go to: https://bugs.launchpad.net/python-neutronclient/+bug/1549634/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1516387] [NEW] Duplicated functions in agent/utils and common/utils
Public bug reported: Both modules have "replace_file" functions. It should be unified and just one method left. ** 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/1516387 Title: Duplicated functions in agent/utils and common/utils Status in neutron: New Bug description: Both modules have "replace_file" functions. It should be unified and just one method left. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1516387/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1516283] [NEW] API extension is an Abstract Class but doesn't use abstractmethod
Public bug reported: ExtensionDescriptor in neutron/api/extensions.py is ABC class but methods are not decorated with abstractmethod. ** Affects: neutron Importance: Undecided Status: New ** Tags: low-hanging-fruit -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1516283 Title: API extension is an Abstract Class but doesn't use abstractmethod Status in neutron: New Bug description: ExtensionDescriptor in neutron/api/extensions.py is ABC class but methods are not decorated with abstractmethod. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1516283/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1323658] Re: Nova resize/restart results in guest ending up in inconsistent state with Neutron
Retested this with latest devstack configuration. Based on description from other bug (duplicate of this: https://bugs.launchpad.net/nova/+bug/1364588) I'm not able to reproduce this problem. Resized about 20 times on running and disabled servers. All the time, everything is OK. There are no problems with "ERROR" state or losing connectivity. Logstash doesn't show any similar problems with this issue. Closing as works-for-me, fix probably was already released. If anyone has another experiences, please reopen with additional info. ** Changed in: neutron Status: Confirmed => Fix Released ** Changed in: nova Assignee: (unassigned) => Dariusz Smigiel (smigiel-dariusz) ** Changed in: nova Status: Confirmed => 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/1323658 Title: Nova resize/restart results in guest ending up in inconsistent state with Neutron Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Bug description: Was looking at this when investigating bug 1310852, so that might be a duplicate of this, but the "Public network connectivity check failed" message doesn't show up in the logs for that bug, so opening a new one. This is also maybe related to or regressions of bug 1194026 and/or bug 1253896. The error in the console log: 2014-05-27 13:34:49.707 | 2014-05-27 13:33:24,369 Creating ssh connection to '172.24.4.110' as 'cirros' with public key authentication 2014-05-27 13:34:49.707 | 2014-05-27 13:33:24,491 Failed to establish authenticated ssh connection to cirros@172.24.4.110 ([Errno 111] Connection refused). Number attempts: 1. Retry after 2 seconds. 2014-05-27 13:34:49.707 | 2014-05-27 13:33:27,162 Failed to establish authenticated ssh connection to cirros@172.24.4.110 ([Errno 111] Connection refused). Number attempts: 2. Retry after 3 seconds. 2014-05-27 13:34:49.707 | 2014-05-27 13:33:32,049 starting thread (client mode): 0x9e9cf10L 2014-05-27 13:34:49.707 | 2014-05-27 13:33:32,050 EOF in transport thread 2014-05-27 13:34:49.707 | 2014-05-27 13:33:32,051 Public network connectivity check failed 2014-05-27 13:34:49.707 | 2014-05-27 13:33:32.051 10354 TRACE tempest.scenario.test_network_advanced_server_ops Traceback (most recent call last): 2014-05-27 13:34:49.707 | 2014-05-27 13:33:32.051 10354 TRACE tempest.scenario.test_network_advanced_server_ops File "tempest/scenario/test_network_advanced_server_ops.py", line 119, in _check_public_network_connectivity 2014-05-27 13:34:49.707 | 2014-05-27 13:33:32.051 10354 TRACE tempest.scenario.test_network_advanced_server_ops should_connect=should_connect) 2014-05-27 13:34:49.708 | 2014-05-27 13:33:32.051 10354 TRACE tempest.scenario.test_network_advanced_server_ops File "tempest/scenario/manager.py", line 779, in _check_vm_connectivity 2014-05-27 13:34:49.708 | 2014-05-27 13:33:32.051 10354 TRACE tempest.scenario.test_network_advanced_server_ops linux_client.validate_authentication() 2014-05-27 13:34:49.708 | 2014-05-27 13:33:32.051 10354 TRACE tempest.scenario.test_network_advanced_server_ops File "tempest/common/utils/linux/remote_client.py", line 53, in validate_authentication 2014-05-27 13:34:49.708 | 2014-05-27 13:33:32.051 10354 TRACE tempest.scenario.test_network_advanced_server_ops self.ssh_client.test_connection_auth() 2014-05-27 13:34:49.708 | 2014-05-27 13:33:32.051 10354 TRACE tempest.scenario.test_network_advanced_server_ops File "tempest/common/ssh.py", line 150, in test_connection_auth 2014-05-27 13:34:49.708 | 2014-05-27 13:33:32.051 10354 TRACE tempest.scenario.test_network_advanced_server_ops connection = self._get_ssh_connection() 2014-05-27 13:34:49.708 | 2014-05-27 13:33:32.051 10354 TRACE tempest.scenario.test_network_advanced_server_ops File "tempest/common/ssh.py", line 75, in _get_ssh_connection 2014-05-27 13:34:49.708 | 2014-05-27 13:33:32.051 10354 TRACE tempest.scenario.test_network_advanced_server_ops timeout=self.channel_timeout, pkey=self.pkey) 2014-05-27 13:34:49.708 | 2014-05-27 13:33:32.051 10354 TRACE tempest.scenario.test_network_advanced_server_ops File "/usr/local/lib/python2.7/dist-packages/paramiko/client.py", line 242, in connect 2014-05-27 13:34:49.709 | 2014-05-27 13:33:32.051 10354 TRACE tempest.scenario.test_network_advanced_server_ops t.start_client() 2014-05-27 13:34:49.709 | 2014-05-27 13:33:32.051 10354 TRACE tempest.scenario.test_network_advanced_server_ops File "/usr/local/lib/python2.7/dist-packages/paramiko/transport.py", line 346, in start_client 2014-05-27 13:34:49.
