[Bug 1960495] [NEW] Designate DNS (RFE) – “api_export_size”, immediate “413 over_quota” instead of “202”
Public bug reported: ### Scenario ### As admin set the “api_export_size” to X Create a Zone and start adding recordsets to exceed X ### Actual Result ### When the X+1 quota is actually reached, export API (asynchronous) responds with 202. ### Expected Result ### Immediate “413 over_quota” response. Notes: 1) For reproducing: https://review.opendev.org/c/openstack/designate-tempest-plugin/+/827934 test name: test_api_export_size_quota 2) From Michael: The issue here is that the zone export API is an asynchronous API. The test will get back a 202 status that Designate has accepted the request. If you do a followup call to "zone export show" you will see that the export went into ERROR. ** Affects: designate Importance: Undecided Status: New ** Tags: designate ** Tags added: designate ** Package changed: ubuntu-release-upgrader (Ubuntu) => designate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960495 Title: Designate DNS (RFE) – “api_export_size”, immediate “413 over_quota” instead of “202” To manage notifications about this bug go to: https://bugs.launchpad.net/designate/+bug/1960495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904751] Re: Neutron – it’s possible to delete router’s port related to external gateway
** Package changed: linux-hwe-5.4 (Ubuntu) => neutron
** Attachment added: "Logs"
https://bugs.launchpad.net/neutron/+bug/1904751/+attachment/5435706/+files/logs.zip
** Description changed:
### Scenario ###
Create a router, set external gateway and add internal interface.
List router’s ports and try to delete them.
There is a patch you can use in order to reproduce the problem:
https://review.opendev.org/#/c/763198/
-
### Actual result ###
Port related to external gateway is successfully deleted.
### Expected ###
Should fail
+
+
+ ### Test patch output in tempest.log ###
+ It's possible to see that the list containing routers port IDs is changed
from:
+ ['74abfbfa-3e60-4b6f-971c-5224dd74db2f',
'af0a74a0-2b14-499a-a871-96e5d804da15']
+ to:
+ ['74abfbfa-3e60-4b6f-971c-5224dd74db2f']
+ means that the port was deleted.
+
+
+ 2020-11-18 10:41:47.998 95480 INFO tempest.lib.common.rest_client
[req-cca60a65-1ce0-46f4-8d58-b5177f256115 ] Request
(RoutersNegativePolicyTest:test_remove_associated_ports): 200 GET
http://10.0.0.109:9696/v2.0/routers/0e7fbc2d-d42b-43d2-873f-5311af9e5c96 0.446s
+ 2020-11-18 10:41:51.676 95480 INFO tempest.lib.common.rest_client
[req-1ab5e603-95f9-4cc0-9497-11346dae7c51 ] Request
(RoutersNegativePolicyTest:test_remove_associated_ports): 200 PUT
http://10.0.0.109:9696/v2.0/routers/0e7fbc2d-d42b-43d2-873f-5311af9e5c96 3.676s
+ 2020-11-18 10:41:55.970 95480 INFO tempest.lib.common.rest_client
[req-e51bc925-41d3-46f3-81a3-ff80e5735e9f ] Request
(RoutersNegativePolicyTest:test_remove_associated_ports): 200 PUT
http://10.0.0.109:9696/v2.0/routers/0e7fbc2d-d42b-43d2-873f-5311af9e5c96/add_router_interface
4.292s
+ 2020-11-18 10:41:56.046 95480 INFO tempest.lib.common.rest_client
[req-2fa43806-cbcb-4d3a-93cc-019c98ad2b94 ] Request
(RoutersNegativePolicyTest:test_remove_associated_ports): 200 GET
http://10.0.0.109:9696/v2.0/ports?router_id=0e7fbc2d-d42b-43d2-873f-5311af9e5c96
0.075s
+ 2020-11-18 10:41:56.047 95480 INFO
neutron_tempest_plugin.api.test_routers_negative [-]
test_remove_associated_ports ['74abfbfa-3e60-4b6f-971c-5224dd74db2f',
'af0a74a0-2b14-499a-a871-96e5d804da15']
+ 2020-11-18 10:41:56.128 95480 INFO tempest.lib.common.rest_client
[req-fbed6aa9-0d27-47ec-9614-38f72b1ace20 ] Request
(RoutersNegativePolicyTest:test_remove_associated_ports): 200 GET
http://10.0.0.109:9696/v2.0/ports/74abfbfa-3e60-4b6f-971c-5224dd74db2f 0.080s
+ 2020-11-18 10:41:56.129 95480 INFO
neutron_tempest_plugin.api.test_routers_negative [-]
test_remove_associated_portsresponse: {'content-type': 'application/json',
'content-length': '898', 'x-openstack-request-id':
'req-fbed6aa9-0d27-47ec-9614-38f72b1ace20', 'date': 'Wed, 18 Nov 2020 15:41:56
GMT', 'connection': 'close', 'status': '200', 'content-location':
'http://10.0.0.109:9696/v2.0/ports/74abfbfa-3e60-4b6f-971c-5224dd74db2f'}
+ 2020-11-18 10:41:56.424 95480 INFO tempest.lib.common.rest_client
[req-61c2a22a-0db2-4cbb-a934-671e979d6b44 ] Request
(RoutersNegativePolicyTest:test_remove_associated_ports): 409 DELETE
http://10.0.0.109:9696/v2.0/ports/74abfbfa-3e60-4b6f-971c-5224dd74db2f 0.294s
+ 2020-11-18 10:41:56.425 95480 ERROR
neutron_tempest_plugin.api.test_routers_negative [-]
test_remove_associated_portsConflict with state of target resource
+ 2020-11-18 10:41:56.504 95480 INFO tempest.lib.common.rest_client
[req-f14dd173-0c96-470c-8bb5-74fb91be1a90 ] Request
(RoutersNegativePolicyTest:test_remove_associated_ports): 200 GET
http://10.0.0.109:9696/v2.0/ports/af0a74a0-2b14-499a-a871-96e5d804da15 0.078s
+ 2020-11-18 10:41:56.505 95480 INFO
neutron_tempest_plugin.api.test_routers_negative [-]
test_remove_associated_portsresponse: {'content-type': 'application/json',
'content-length': '892', 'x-openstack-request-id':
'req-f14dd173-0c96-470c-8bb5-74fb91be1a90', 'date': 'Wed, 18 Nov 2020 15:41:56
GMT', 'connection': 'close', 'status': '200', 'content-location':
'http://10.0.0.109:9696/v2.0/ports/af0a74a0-2b14-499a-a871-96e5d804da15'}
+ 2020-11-18 10:41:57.552 95480 INFO tempest.lib.common.rest_client
[req-bd795598-b016-4e57-ad95-df53e1fd2fa0 ] Request
(RoutersNegativePolicyTest:test_remove_associated_ports): 204 DELETE
http://10.0.0.109:9696/v2.0/ports/af0a74a0-2b14-499a-a871-96e5d804da15 1.047s
+ 2020-11-18 10:41:57.652 95480 INFO tempest.lib.common.rest_client
[req-2e0dfdeb-5892-40f0-b4a2-ba314ba8fd36 ] Request
(RoutersNegativePolicyTest:test_remove_associated_ports): 200 GET
http://10.0.0.109:9696/v2.0/ports?router_id=0e7fbc2d-d42b-43d2-873f-5311af9e5c96
0.098s
+ 2020-11-18 10:41:57.653 95480 INFO
neutron_tempest_plugin.api.test_routers_negative [-]
test_remove_associated_ports ['74abfbfa-3e60-4b6f-971c-5224dd74db2f']
** Description changed:
### Scenario ###
Create a router, set external gateway and add internal interface.
List router’s ports and try to delete them.
There is a patch you can use in order to reproduce the problem:
https://review.opendev.org/#/c/763198
[Bug 1904751] [NEW] Neutron – it’s possible to delete router’s port related to external gateway
Public bug reported: ### Scenario ### Create a router, set external gateway and add internal interface. List router’s ports and try to delete them. There is a patch you can use in order to reproduce the problem: https://review.opendev.org/#/c/763198/ ### Actual result ### Port related to external gateway is successfully deleted. ### Expected ### Should fail ** Affects: neutron Importance: Undecided Status: New ** Tags: neutron ** Tags added: neutron -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904751 Title: Neutron – it’s possible to delete router’s port related to external gateway To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1904751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778392] [NEW] QoS CLI - “network qos policy delete” command fails and description field is empty (reason unknown)
Public bug reported:
Scenario:
1) Create QoS policy
openstack network qos policy create bw-limiter
Save
2) Create QoS rulem assitiated to pcreated previously policy
openstack network qos rule create --type bandwidth-limit --max-kbps 3000
--max-burst-kbits 2400 --egress bw-limiter
3) Delete Policy
openstack network qos policy delete --debug
Actual Result:
Description field inside the error is empty, therefore the reason for command
failure is unknown.
(overcloud) [stack@undercloud-0 ~]$ openstack network qos policy delete
c2920eed-a25f-4d8d-a8f1-5edcfd8ed778
Failed to delete QoS policy name or ID 'c2920eed-a25f-4d8d-a8f1-5edcfd8ed778':
Unable to delete QoSPolicy for
openstack.network.v2.qos_policy.QoSPolicy(name=bw-limiter, rules=[{u'max_kbps':
1, u'direction': u'egress', u'qos_policy_id':
u'c2920eed-a25f-4d8d-a8f1-5edcfd8ed778', u'type': u'bandwidth_limit', u'id':
u'9fc86255-3149-4957-a926-6280eab761ab', u'max_burst_kbps': 1}],
tenant_id=f3f03848a45746c7bcbe95b625d7e1d8, is_default=False, shared=False,
id=c2920eed-a25f-4d8d-a8f1-5edcfd8ed778, description=)
1 of 1 QoS policies failed to delete.
Expected Result:
Description field shouldn’t be empty and at least must have the same message as
in executed API.
When the same command is executed with “--debug” option (openstack network qos
policy delete --debug c2920eed-a25f-4d8d-a8f1-5edcfd8ed778) it’s possible to
see that HTTP Status Code 409 is received with body, that contains “QoS Policy
c2920eed-a25f-4d8d-a8f1-5edcfd8ed778 is used by port
535da8b9-fbce-4921-9ce7-3fa26ca8a698”
The above message is not forwarded to CLI.
GET call to network for
http://10.0.0.105:9696/v2.0/qos/policies/c2920eed-a25f-4d8d-a8f1-5edcfd8ed778
used request id req-1a31e6c0-d58e-4bae-b992-4f27182e658a
Manager unknown ran task network.GET.qos.c2920eed-a25f-4d8d-a8f1-5edcfd8ed778
in 0.867774009705s
Manager unknown running task
network.DELETE.qos.c2920eed-a25f-4d8d-a8f1-5edcfd8ed778
REQ: curl -g -i -X DELETE
http://10.0.0.105:9696/v2.0/qos/policies/c2920eed-a25f-4d8d-a8f1-5edcfd8ed778
-H "User-Agent: osc-lib/1.9.0 keystoneauth1/3.4.0 python-requests/2.14.2
CPython/2.7.5" -H "Accept: " -H "X-Auth-Token:
{SHA1}1d4e9ce3cf3e5d34b283fd33ee005c1809537cf1"
http://10.0.0.105:9696 "DELETE
/v2.0/qos/policies/c2920eed-a25f-4d8d-a8f1-5edcfd8ed778 HTTP/1.1" 409 174
RESP: [409] Content-Type: application/json Content-Length: 174
X-Openstack-Request-Id: req-b1d2-dc3a-4f90-a7ce-dbfa633c8c6a Date: Sun, 24
Jun 2018 08:37:01 GMT
RESP BODY: {"NeutronError": {"message": "QoS Policy
c2920eed-a25f-4d8d-a8f1-5edcfd8ed778 is used by port
535da8b9-fbce-4921-9ce7-3fa26ca8a698.", "type": "QosPolicyInUse", "detail": ""}}
** Affects: connectome-workbench (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778392
Title:
QoS CLI - “network qos policy delete” command fails and description
field is empty (reason unknown)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/connectome-workbench/+bug/1778392/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
