[Yahoo-eng-team] [Bug 1719259] [NEW] Networking API v2.0 in Networking API Reference
Public bug reported: 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. - [x] 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: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: 1.8.1.dev40 on 'Tue Jul 18 18:01:21 2017, commit 7581af4' SHA: Source: Can't derive source file URL URL: https://developer.openstack.org/api-ref/networking/v2/ ** Affects: neutron Importance: Undecided Status: New ** Tags: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1719259 Title: Networking API v2.0 in Networking API Reference Status in neutron: New 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: __ - [ ] This is a doc addition request. - [x] 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: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: 1.8.1.dev40 on 'Tue Jul 18 18:01:21 2017, commit 7581af4' SHA: Source: Can't derive source file URL URL: https://developer.openstack.org/api-ref/networking/v2/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1719259/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1686877] [NEW] ml2 physical network using Chinese characters fails to save to postgresql
Public bug reported: Steps to produce this bug: 1. configure ml2_conf.ini,and then dispatch the configuration, restart neutron-server service [ml2_type_vlan] network_vlan_ranges = physnet1:100:120,中文:121:125 expected result: configuration data correctly saves into postgresql real result: pass 2. reconfigure ml2_conf.ini,and then dispatch the configuration, restart neutron-server service [ml2_type_vlan] network_vlan_ranges = physnet1:100:120,中文:121:124 expected result: configuration data correctly saves into postgresql real result: fail neutron-server error:UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 143: ordinal not in range(128) ** 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/1686877 Title: ml2 physical network using Chinese characters fails to save to postgresql Status in neutron: New Bug description: Steps to produce this bug: 1. configure ml2_conf.ini,and then dispatch the configuration, restart neutron-server service [ml2_type_vlan] network_vlan_ranges = physnet1:100:120,中文:121:125 expected result: configuration data correctly saves into postgresql real result: pass 2. reconfigure ml2_conf.ini,and then dispatch the configuration, restart neutron-server service [ml2_type_vlan] network_vlan_ranges = physnet1:100:120,中文:121:124 expected result: configuration data correctly saves into postgresql real result: fail neutron-server error:UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 143: ordinal not in range(128) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1686877/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1656735] Re: Fwaas - insert_rule and remove_rule always set audited to False
** 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/1656735 Title: Fwaas - insert_rule and remove_rule always set audited to False Status in neutron: New Status in openstack-api-site: New Bug description: when people use "insert_rule" or "remove_rule" on a firewall policy, the "audited" attribute of the firewall policy is always set to be "false" in function _process_rule_for_policy().I think it's not right and can bring users problems. First, It's not logical when the firewall policy was created with "audited" to be "true" and both "insert_rule" and "remove_rule" don't intend to modify "audited" attribute. Second, after bug https://bugs.launchpad.net/neutron/+bug/1438615 is resolved, operation of "update_firewall_policy" will not change "audited" attribute, it only sets "audited" to be "false" when people haven't set this attribute explicitly. Above is the error in fwaas code. There is alse an error in fwaas v1.0 api as to the description about "audited" attribute.The api document says "Each time that the firewall policy or its associated rules are changed, the API sets this attribute to false. To audit the policy, explicitly set this attribute to true.". But why user needs to explicitly set it again after insert_rule or remove_rule ? And in fact ,"update_firewall_policy" doesn't need to do so. So I think we should correct this error both in code and api document. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1656735/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1656735] [NEW] Fwaas - insert_rule and remove_rule always set audited to False
Public bug reported: when people use "insert_rule" or "remove_rule" on a firewall policy, the "audited" attribute of the firewall policy is always set to be "false" in function _process_rule_for_policy().I think it's not right and can bring users problems. First, It's not logical when the firewall policy was created with "audited" to be "true" and both "insert_rule" and "remove_rule" don't intend to modify "audited" attribute. Second, after bug https://bugs.launchpad.net/neutron/+bug/1438615 is resolved, operation of "update_firewall_policy" will not change "audited" attribute, it only sets "audited" to be "false" when people haven't set this attribute explicitly. Above is the error in fwaas code. There is alse an error in fwaas v1.0 api as to the description about "audited" attribute.The api document says "Each time that the firewall policy or its associated rules are changed, the API sets this attribute to false. To audit the policy, explicitly set this attribute to true.". But why user needs to explicitly set it again after insert_rule or remove_rule ? And in fact ,"update_firewall_policy" doesn't need to do so. So I think we should correct this error both in code and api document. ** 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/1656735 Title: Fwaas - insert_rule and remove_rule always set audited to False Status in neutron: New Bug description: when people use "insert_rule" or "remove_rule" on a firewall policy, the "audited" attribute of the firewall policy is always set to be "false" in function _process_rule_for_policy().I think it's not right and can bring users problems. First, It's not logical when the firewall policy was created with "audited" to be "true" and both "insert_rule" and "remove_rule" don't intend to modify "audited" attribute. Second, after bug https://bugs.launchpad.net/neutron/+bug/1438615 is resolved, operation of "update_firewall_policy" will not change "audited" attribute, it only sets "audited" to be "false" when people haven't set this attribute explicitly. Above is the error in fwaas code. There is alse an error in fwaas v1.0 api as to the description about "audited" attribute.The api document says "Each time that the firewall policy or its associated rules are changed, the API sets this attribute to false. To audit the policy, explicitly set this attribute to true.". But why user needs to explicitly set it again after insert_rule or remove_rule ? And in fact ,"update_firewall_policy" doesn't need to do so. So I think we should correct this error both in code and api document. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1656735/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1616793] [NEW] neutron availability-zone-list got a db error using postgresql
xt 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource context) 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py", line 450, in do_execute 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource cursor.execute(statement, parameters) 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource DBError: (psycopg2.ProgrammingError) column "agents.id" must appear in the GROUP BY clause or be used in an aggregate function ** Affects: neutron Importance: Undecided Assignee: brenda (tian-mingming) Status: New ** Changed in: neutron Assignee: (unassigned) => brenda (tian-mingming) ** Description changed: when use cli command "neutron availability-zone-list" with postgresql db backend,I got a server error,like below: - 1f2ce05c6ff342eca06920525ab11923 - - -] DBAPIError exception wrapped from (psycopg2.ProgrammingError) column "agents.id" must appear in the GROUP BY clause or be used in an aggregate function - LINE 1: SELECT agents.id AS agents_id, agents.agent_type AS agents_a... -^ - [SQL: 'SELECT agents.id AS agents_id, agents.agent_type AS agents_agent_type, agents."binary" AS agents_binary, agents.topic AS agents_topic, agents.host AS agents_host, agents.availability_zone AS agents_availability_zone, agents.admin_state_up AS agents_admin_state_up, agents.created_at AS agents_created_at, agents.started_at AS agents_started_at, agents.heartbeat_timestamp AS agents_heartbeat_timestamp, agents.description AS agents_description, agents.configurations AS agents_configurations, agents.resource_versions AS agents_resource_versions, agents.load AS agents_load \nFROM agents GROUP BY agents.admin_state_up, agents.availability_zone, agents.agent_type'] - 2016-08-25 13:41:17.785 29748 ERROR oslo_db.sqlalchemy.exc_filters Traceback (most recent call last): - 2016-08-25 13:41:17.785 29748 ERROR oslo_db.sqlalchemy.exc_filters File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1139, in _execute_context - 2016-08-25 13:41:17.785 29748 ERROR oslo_db.sqlalchemy.exc_filters context) - 2016-08-25 13:41:17.785 29748 ERROR oslo_db.sqlalchemy.exc_filters File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py", line 450, in do_execute - 2016-08-25 13:41:17.785 29748 ERROR oslo_db.sqlalchemy.exc_filters cursor.execute(statement, parameters) - 2016-08-25 13:41:17.785 29748 ERROR oslo_db.sqlalchemy.exc_filters ProgrammingError: column "agents.id" must appear in the GROUP BY clause or be used in an aggregate function - 2016-08-25 13:41:17.785 29748 ERROR oslo_db.sqlalchemy.exc_filters LINE 1: SELECT agents.id AS agents_id, agents.agent_type AS agents_a... - 2016-08-25 13:41:17.785 29748 ERROR oslo_db.sqlalchemy.exc_filters ^ - 2016-08-25 13:41:17.785 29748 ERROR oslo_db.sqlalchemy.exc_filters - 2016-08-25 13:41:17.785 29748 ERROR oslo_db.sqlalchemy.exc_filters - 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource [req-8506cf81-aa42-4cc0-9f7c-9a6f1743c46c d97366d8aeb449edb9a91949a9d213e3 1f2ce05c6ff342eca06920525ab11923 - - -] index failed 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource Traceback (most recent call last): 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/site-packages/neutron/api/v2/resource.py", line 84, in resource 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource result = method(request=request, **args) 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/site-packages/oslo_db/api.py", line 148, in wrapper 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource ectxt.value = e.inner_exc 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource self.force_reraise() 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource six.reraise(self.type_, self.value, self.tb) 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/site-packages/oslo_db/api.py", line 138, in wrapper 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource return f(*args, **kwargs) 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/site-packages/neutron/api/v2/base.py", line 341, in index 2016-08-25 13:41:17.808 29748 ERROR neutron.api.v2.resource return self._items(request, True, parent_id) 2016-08-25 13:41:17.808 29748 ERROR neutr
[Yahoo-eng-team] [Bug 1616713] [NEW] neutron provider network type shouldn't include "vxlan" and "gre"
Public bug reported:
I think there is a mistake on "Networking API v2.0" document at
http://developer.openstack.org/api-ref/networking/v2/?expanded=update-network-provider-network-detail.
The api points that "provider:network_type" is the type of physical network
that maps to this network resource. For example, flat, vlan, vxlan, or gre. But
"vxlan" and "gre" network types are both overlay network types, they should not
be included in provider network types.
** Affects: neutron
Importance: Undecided
Assignee: brenda (tian-mingming)
Status: New
** Changed in: neutron
Assignee: (unassigned) => brenda (tian-mingming)
** Description changed:
- I think there is a mistake on "Networking API v2.0" document
athttp://developer.openstack.org/api-ref/networking/v2/?expanded=update-network-provider-network-detail.
+ I think there is a mistake on "Networking API v2.0" document at
http://developer.openstack.org/api-ref/networking/v2/?expanded=update-network-provider-network-detail.
The api points that "provider:network_type" is the type of physical network
that maps to this network resource. For example, flat, vlan, vxlan, or gre. But
"vxlan" and "gre" network types are both overlay network types, they should not
be included in provider network types.
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1616713
Title:
neutron provider network type shouldn't include "vxlan" and "gre"
Status in neutron:
New
Bug description:
I think there is a mistake on "Networking API v2.0" document at
http://developer.openstack.org/api-ref/networking/v2/?expanded=update-network-provider-network-detail.
The api points that "provider:network_type" is the type of physical network
that maps to this network resource. For example, flat, vlan, vxlan, or gre. But
"vxlan" and "gre" network types are both overlay network types, they should not
be included in provider network types.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1616713/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1596158] [NEW] firewall rule add "rejet" action db upgrade script doesn't work for postgresql
Public bug reported: >From Liberty, firewall rule add a "reject" action, but migration script "4b47ea298795_add_reject_rule.py" doesn't work for postgrepsql ** Affects: neutron Importance: Undecided Assignee: brenda (tian-mingming) Status: New ** Changed in: neutron Assignee: (unassigned) => brenda (tian-mingming) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1596158 Title: firewall rule add "rejet" action db upgrade script doesn't work for postgresql Status in neutron: New Bug description: From Liberty, firewall rule add a "reject" action, but migration script "4b47ea298795_add_reject_rule.py" doesn't work for postgrepsql To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1596158/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1458115] [NEW] creating a router with gateway set doesn't notify l3 agent
Public bug reported: In horizon, when creating a router, user can't set gateway at the moment. But the API guide of Networking API v2.0 extensions allows users to create a router with a gateway set in request body, and I have checked the codes in file neutron/db/l3_db.py, the function create_router hasn't send a notification to l3 agent when a gateway is set, so l3 agent couldn't create namespace for that router at right time. ** Affects: neutron Importance: Undecided Assignee: brenda (tian-mingming) Status: New ** Changed in: neutron Assignee: (unassigned) = brenda (tian-mingming) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1458115 Title: creating a router with gateway set doesn't notify l3 agent Status in OpenStack Neutron (virtual network service): New Bug description: In horizon, when creating a router, user can't set gateway at the moment. But the API guide of Networking API v2.0 extensions allows users to create a router with a gateway set in request body, and I have checked the codes in file neutron/db/l3_db.py, the function create_router hasn't send a notification to l3 agent when a gateway is set, so l3 agent couldn't create namespace for that router at right time. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1458115/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1454041] [NEW] misunderstanding caused by uuid token and pki token in install guide
Public bug reported: In released install guide, we can see the step to set token provider to uuid, as following: [token] provider = keystone.token.providers.uuid.Provider but there are further steps to set pki token, as following: # keystone-manage pki_setup --keystone-user keystone --keystone-group keystone # chown -R keystone:keystone /var/log/keystone # chown -R keystone:keystone /etc/keystone/ssl # chmod -R o-rwx /etc/keystone/ssl I think pki token has been brought in from Grizzly，and the installation guide should be use pki token provier, like below: [token] provider = keystone.token.providers.pki.Provider ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1454041 Title: misunderstanding caused by uuid token and pki token in install guide Status in OpenStack Identity (Keystone): New Bug description: In released install guide, we can see the step to set token provider to uuid, as following: [token] provider = keystone.token.providers.uuid.Provider but there are further steps to set pki token, as following: # keystone-manage pki_setup --keystone-user keystone --keystone-group keystone # chown -R keystone:keystone /var/log/keystone # chown -R keystone:keystone /etc/keystone/ssl # chmod -R o-rwx /etc/keystone/ssl I think pki token has been brought in from Grizzly，and the installation guide should be use pki token provier, like below: [token] provider = keystone.token.providers.pki.Provider To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1454041/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
