[Yahoo-eng-team] [Bug 1558306] [NEW] VPNaaS returns 500 INTERNAL on long names
Public bug reported: Current VPNaaS returns a 500 INTERNAL SERVER error when given long names or descriptions. Instead should give a 400 BAD REQUEST explaining user given value exceeds maximum threshold, like: neutron vpn-service-create router1 --name 012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789 Invalid input for name. Reason: '012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789' exceeds maximum length of 255. Applies to both names and descriptions. ** Affects: neutron Importance: Undecided Assignee: James Arendt (james-arendt-7) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => James Arendt (james-arendt-7) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1558306 Title: VPNaaS returns 500 INTERNAL on long names Status in neutron: In Progress Bug description: Current VPNaaS returns a 500 INTERNAL SERVER error when given long names or descriptions. Instead should give a 400 BAD REQUEST explaining user given value exceeds maximum threshold, like: neutron vpn-service-create router1 --name 012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789 Invalid input for name. Reason: '012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789' exceeds maximum length of 255. Applies to both names and descriptions. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1558306/+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 1546793] [NEW] Fix neutron-fwaas cover tests
Public bug reported: The tox.ini command for 'tox -e cover' breaks with error: cover runtests: commands[0] | python setup.py testr --coverage --coverage-package-name=neutron_fwaas --testr-args= usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: option --coverage-package-name not recognized ERROR: InvocationError: '/opt/stack/neutron-fwaas/.tox/cover/bin/python setup.py testr --coverage --coverage-package-name=neutron_fwaas --testr-args=' ___ summary ERROR: cover: commands failed Appears to be same issue as found in neutron-vpnaas and fixed there under https://review.openstack.org/#/c/217847/ ** Affects: neutron Importance: Undecided Assignee: James Arendt (james-arendt-7) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => James Arendt (james-arendt-7) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1546793 Title: Fix neutron-fwaas cover tests Status in neutron: In Progress Bug description: The tox.ini command for 'tox -e cover' breaks with error: cover runtests: commands[0] | python setup.py testr --coverage --coverage-package-name=neutron_fwaas --testr-args= usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: option --coverage-package-name not recognized ERROR: InvocationError: '/opt/stack/neutron-fwaas/.tox/cover/bin/python setup.py testr --coverage --coverage-package-name=neutron_fwaas --testr-args=' ___ summary ERROR: cover: commands failed Appears to be same issue as found in neutron-vpnaas and fixed there under https://review.openstack.org/#/c/217847/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1546793/+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 1546786] [NEW] Removed vpn tempest mappings breaks vpnaas tests
Public bug reported: The 'tox -e api' tests for neutron-vpnaas fail. The code relies on the neutron tempest network client and the relevant service_resource_prefix_map, and the mappings for resources like: 'vpnservices': 'vpn', were removed. This causes the tests to fail with 404 errors using an incorrect uri. ** Affects: neutron Importance: Undecided Assignee: James Arendt (james-arendt-7) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => James Arendt (james-arendt-7) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1546786 Title: Removed vpn tempest mappings breaks vpnaas tests Status in neutron: In Progress Bug description: The 'tox -e api' tests for neutron-vpnaas fail. The code relies on the neutron tempest network client and the relevant service_resource_prefix_map, and the mappings for resources like: 'vpnservices': 'vpn', were removed. This causes the tests to fail with 404 errors using an incorrect uri. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1546786/+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 1546237] [NEW] Typo in alembic_migrations.rst
Public bug reported: "Indepedent" should be "Independent" in header "1. Indepedent Sub- Project Tables" Externally visible at http://docs.openstack.org/developer/neutron/devref/alembic_migrations.html. ** Affects: neutron Importance: Undecided Assignee: James Arendt (james-arendt-7) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => James Arendt (james-arendt-7) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1546237 Title: Typo in alembic_migrations.rst Status in neutron: In Progress Bug description: "Indepedent" should be "Independent" in header "1. Indepedent Sub- Project Tables" Externally visible at http://docs.openstack.org/developer/neutron/devref/alembic_migrations.html. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1546237/+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 1526108] [NEW] Octavia devstack install fails behind proxy
Public bug reported:
The octavia devstack/plugin.sh script does a sudo pip install without
passing the user environment, meaning settings like
http_proxy/https_proxy are not passed and keeping the devstack from
working behind a proxy that needs those settings for pip installs if set
for the user only.
function octavia_install {
setup_develop $OCTAVIA_DIR
if ! [ "$DISABLE_AMP_IMAGE_BUILD" == 'True' ]; then
install_package qemu kpartx
git_clone https://git.openstack.org/openstack/diskimage-builder.git $DE\
ST/diskimage-builder master
git_clone https://git.openstack.org/openstack/tripleo-image-elements.gi\
t $DEST/tripleo-image-elements master
sudo pip install -r $DEST/diskimage-builder/requirements.txt
fi
The user could explicitly set http_proxy/https_proxy settings for root
as well to avoid the issue. But this error takes a long time to come to
when using client only proxy settings until octavia diskimage build sudo
fails.
Other services such as devstack/install_pip.sh do pass the user
enviornment to sudo with the -E flag. Suggested fix is to pass the '-E'
flag in this situation as well.
** Affects: neutron
Importance: Undecided
Assignee: James Arendt (james-arendt-7)
Status: New
** Changed in: neutron
Assignee: (unassigned) => James Arendt (james-arendt-7)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1526108
Title:
Octavia devstack install fails behind proxy
Status in neutron:
New
Bug description:
The octavia devstack/plugin.sh script does a sudo pip install without
passing the user environment, meaning settings like
http_proxy/https_proxy are not passed and keeping the devstack from
working behind a proxy that needs those settings for pip installs if
set for the user only.
function octavia_install {
setup_develop $OCTAVIA_DIR
if ! [ "$DISABLE_AMP_IMAGE_BUILD" == 'True' ]; then
install_package qemu kpartx
git_clone https://git.openstack.org/openstack/diskimage-builder.git
$DE\
ST/diskimage-builder master
git_clone
https://git.openstack.org/openstack/tripleo-image-elements.gi\
t $DEST/tripleo-image-elements master
sudo pip install -r $DEST/diskimage-builder/requirements.txt
fi
The user could explicitly set http_proxy/https_proxy settings for root
as well to avoid the issue. But this error takes a long time to come
to when using client only proxy settings until octavia diskimage build
sudo fails.
Other services such as devstack/install_pip.sh do pass the user
enviornment to sudo with the -E flag. Suggested fix is to pass the
'-E' flag in this situation as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1526108/+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 1525430] [NEW] neutron-lbaas tempest v2 api tests not passing config to serviceclient
Public bug reported: Current lbaas tempest v2 api tests do not pass on certain configuration information to the underlyiing ServiceClient used to make a connection, so tests do not work if values like the endpoint_type or region for the network are changed in the tempest.conf. Similarly cannot change control values like the build_timeout. For example, run tempest tests from the neuton_lbaas tree via OS_TEST_PATH with TEMPEST_CONFIG_DIR set to a tempest.conf that has modified network values: endpoint_type = internalURL The existing code will not honor this endpoint_type for the client. Fix is to pass on the info. I.e. instead of the current code: client_args = [auth_provider, 'network', 'regionOne'] cls.load_balancers_client = ( load_balancers_client.LoadBalancersClientJSON(*client_args)) Read configuration and pass on the parameters if they exist thru to the ServiceClient base class underling the client connection with method signature: def __init__(self, auth_provider, service, region, endpoint_type=None, build_interval=None, build_timeout=None, disable_ssl_certificate_validation=None, ca_certs=None, trace_requests=None): ** Affects: neutron Importance: Undecided Assignee: James Arendt (james-arendt-7) Status: New ** Changed in: neutron Assignee: (unassigned) => James Arendt (james-arendt-7) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1525430 Title: neutron-lbaas tempest v2 api tests not passing config to serviceclient Status in neutron: New Bug description: Current lbaas tempest v2 api tests do not pass on certain configuration information to the underlyiing ServiceClient used to make a connection, so tests do not work if values like the endpoint_type or region for the network are changed in the tempest.conf. Similarly cannot change control values like the build_timeout. For example, run tempest tests from the neuton_lbaas tree via OS_TEST_PATH with TEMPEST_CONFIG_DIR set to a tempest.conf that has modified network values: endpoint_type = internalURL The existing code will not honor this endpoint_type for the client. Fix is to pass on the info. I.e. instead of the current code: client_args = [auth_provider, 'network', 'regionOne'] cls.load_balancers_client = ( load_balancers_client.LoadBalancersClientJSON(*client_args)) Read configuration and pass on the parameters if they exist thru to the ServiceClient base class underling the client connection with method signature: def __init__(self, auth_provider, service, region, endpoint_type=None, build_interval=None, build_timeout=None, disable_ssl_certificate_validation=None, ca_certs=None, trace_requests=None): To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1525430/+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 1509045] [NEW] FWaaS typos in comments
Public bug reported: Fix minor set of comment typos in FWaaS files: "interfacesr" -> "interfaces" "dictionry" -> "dictionary" "protacal" -> "protocol" "implmentation" -> "implementation" "libary" -> "library" ** Affects: neutron Importance: Undecided Assignee: James Arendt (james-arendt-7) Status: New ** Changed in: neutron Assignee: (unassigned) => James Arendt (james-arendt-7) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1509045 Title: FWaaS typos in comments Status in neutron: New Bug description: Fix minor set of comment typos in FWaaS files: "interfacesr" -> "interfaces" "dictionry" -> "dictionary" "protacal" -> "protocol" "implmentation" -> "implementation" "libary" -> "library" To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1509045/+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 1503642] Re: Firewall-Update command help content does not display "admin_state_up" argument
The CLI help is in the python-neutronclient, not on the neutron server
side, so moved bug there. Fix is in review
https://review.openstack.org/#/c/234916/
** Project changed: neutron => python-neutronclient
** Changed in: python-neutronclient
Milestone: mitaka-1 => None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1503642
Title:
Firewall-Update command help content does not display "admin_state_up"
argument
Status in python-neutronclient:
In Progress
Bug description:
Get the help contents of the firewall-update command
stack@stevens-creek:~/firewall$ neutron help firewall-update
usage: neutron firewall-update [-h] [--request-format {json,xml}]
[--policy POLICY]
[--router ROUTER | --no-routers]
FIREWALL
Update a given firewall.
positional arguments:
FIREWALL ID or name of firewall to update.
optional arguments:
-h, --helpshow this help message and exit
--request-format {json,xml}
The XML or JSON request format.
--policy POLICY Firewall policy name or ID.
--router ROUTER Firewall associated router names or IDs (requires
FWaaS router insertion extension, this option can be
repeated)
--no-routers Associate no routers with the firewall (requires FWaaS
router insertion extension)
stack@stevens-creek:~/firewall$
Issue :
--admin_state_up argument does not display in the contents
Expected:
Help contents should have --admin_state_up argumment since we are
able to make firewall UP and DOWN by updating the --admin_state_up
toTrue/False
To manage notifications about this bug go to:
https://bugs.launchpad.net/python-neutronclient/+bug/1503642/+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 1498614] [NEW] VPNaaS minor typos in comments
Public bug reported: Fix a small set of comment typos in VPNaaS tree: 'valdiator' 'retreive' 'verison' 'ipser_site_connection' ** Affects: neutron Importance: Undecided Assignee: James Arendt (james-arendt-7) Status: New ** Changed in: neutron Assignee: (unassigned) => James Arendt (james-arendt-7) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1498614 Title: VPNaaS minor typos in comments Status in neutron: New Bug description: Fix a small set of comment typos in VPNaaS tree: 'valdiator' 'retreive' 'verison' 'ipser_site_connection' To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1498614/+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 1490063] [NEW] Neutron flavor framework not saving service_type
Public bug reported: Service type for a created flavor is not being persisted nor returned in the resource dictionary. The Neutron service flavor framework has a database field for the flavor resource to persist the service_type associated with the flavor and the service_type attribute exists in the creation call, but the value was not part of the dictionary used to create the flavor nor is value being returned. ** Affects: neutron Importance: Undecided Assignee: James Arendt (james-arendt-7) Status: New ** Changed in: neutron Assignee: (unassigned) = James Arendt (james-arendt-7) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1490063 Title: Neutron flavor framework not saving service_type Status in neutron: New Bug description: Service type for a created flavor is not being persisted nor returned in the resource dictionary. The Neutron service flavor framework has a database field for the flavor resource to persist the service_type associated with the flavor and the service_type attribute exists in the creation call, but the value was not part of the dictionary used to create the flavor nor is value being returned. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1490063/+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 1489125] [NEW] FWaaS Long name or description causes 500
Public bug reported: The FWaaS REST interface is not checking string lengths, so a name greater than 255 characters or a description greater than 1024 will cause creations to fail with a 500 INTERNAL SERVER error due to a Data too long for column DB error internally. $ neutron firewall-create --name NameLongerThan255Characters01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789 testpolicy Request Failed: internal server error while processing your request. Too long names are a user issue, so with validation would receive a better user-focused response: neutron firewall-create --name NameLongerThan255Characters01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789 testpolicy Invalid input for name. Reason: 'NameLongerThan255Characters01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789' exceeds maximum length of 255. ** Affects: neutron Importance: Undecided Assignee: James Arendt (james-arendt-7) Status: New ** Changed in: neutron Assignee: (unassigned) = James Arendt (james-arendt-7) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1489125 Title: FWaaS Long name or description causes 500 Status in neutron: New Bug description: The FWaaS REST interface is not checking string lengths, so a name greater than 255 characters or a description greater than 1024 will cause creations to fail with a 500 INTERNAL SERVER error due to a Data too long for column DB error internally. $ neutron firewall-create --name NameLongerThan255Characters01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789 testpolicy Request Failed: internal server error while processing your request. Too long names are a user issue, so with validation would receive a better user-focused response: neutron firewall-create --name NameLongerThan255Characters01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789 testpolicy Invalid input for name. Reason: 'NameLongerThan255Characters01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789' exceeds maximum length of 255. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1489125/+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 1489197] [NEW] Flavor service profiles map lacks tenant_id
Public bug reported:
The neutron v2 base.py auto populates a 'tenant_id' attribute on calls
if the attribute is not passed, pulling from the context.
This causes a POST to create a flavor service binding to fail when verifying
attributes, as currently the tenant_id is not
part of the expected attribute map.
curl -g -i -X POST http://192.168.181.169:9696/v2.0/flavors/e38b4b6d-
872e-4656-b7bc-70e15455ee46/service_profiles.json -H User-Agent:
python-neutronclient -H Content-Type: application/json -H Accept:
application/json -H X-Auth-Token: AnAuthToken -d
'{service_profile: {id: 7fd54b73-6bf6-4fc8--0045a808eec2}}'
RESP BODY: {NeutronError: {message: Unrecognized attribute(s)
'tenant_id', type: HTTPBadRequest, detail: }}
The solution, used by folks like QOS, is to add the tenant_id as a
common field to the attribute map.
** Affects: neutron
Importance: Undecided
Assignee: James Arendt (james-arendt-7)
Status: New
** Changed in: neutron
Assignee: (unassigned) = James Arendt (james-arendt-7)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1489197
Title:
Flavor service profiles map lacks tenant_id
Status in neutron:
New
Bug description:
The neutron v2 base.py auto populates a 'tenant_id' attribute on calls
if the attribute is not passed, pulling from the context.
This causes a POST to create a flavor service binding to fail when verifying
attributes, as currently the tenant_id is not
part of the expected attribute map.
curl -g -i -X POST http://192.168.181.169:9696/v2.0/flavors/e38b4b6d-
872e-4656-b7bc-70e15455ee46/service_profiles.json -H User-Agent:
python-neutronclient -H Content-Type: application/json -H Accept:
application/json -H X-Auth-Token: AnAuthToken -d
'{service_profile: {id: 7fd54b73-6bf6-4fc8--0045a808eec2}}'
RESP BODY: {NeutronError: {message: Unrecognized attribute(s)
'tenant_id', type: HTTPBadRequest, detail: }}
The solution, used by folks like QOS, is to add the tenant_id as a
common field to the attribute map.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1489197/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1486136] [NEW] Neutron create_flavor_service_profile returns list not dict
Public bug reported: The Neutron flavor framework routine create_flavor_service_profile incorrectly returns a list instead of the expected dictionary. For example, this causes an internal server error in _exclude_attributes_by_policy when using curl to create a Neutron flavor service profile: File /opt/stack/neutron/neutron/api/v2/base.py, line 143, in _exclude_attributes_by_policy for attr_name in data.keys(): AttributeError: 'list' object has no attribute 'keys' ** Affects: neutron Importance: Undecided Assignee: James Arendt (james-arendt-7) Status: New ** Changed in: neutron Assignee: (unassigned) = James Arendt (james-arendt-7) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1486136 Title: Neutron create_flavor_service_profile returns list not dict Status in neutron: New Bug description: The Neutron flavor framework routine create_flavor_service_profile incorrectly returns a list instead of the expected dictionary. For example, this causes an internal server error in _exclude_attributes_by_policy when using curl to create a Neutron flavor service profile: File /opt/stack/neutron/neutron/api/v2/base.py, line 143, in _exclude_attributes_by_policy for attr_name in data.keys(): AttributeError: 'list' object has no attribute 'keys' To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1486136/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
