[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
This bug was fixed in the package neutron - 2:10.0.7-0ubuntu1~cloud3 --- neutron (2:10.0.7-0ubuntu1~cloud3) xenial-ocata; urgency=medium . * Revert backport of ingress bandwidth limits fix (LP: #1841700). The following patches are dropped. - d/p/0001-Change-duplicate-OVS-bridge-datapath-ids.patch - d/p/0002-Add-QoS-bandwidth-limit-for-instance-ingress-traffic.patch - d/p/0003-Add-support-for-ingress-bandwidth-limit-rules-in-ovs.patch - d/p/0004-Ingress-bandwidth-limit-rule-in-Linuxbridge-agent.patch - d/p/0005-Extend-QoS-L2-drivers-interface-to-handle-ingress-ru.patch - d/p/0006-add-missing-migration.patch ** Changed in: cloud-archive/ocata Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841700 Title: instance ingress bandwidth limiting doesn't works in ocata. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1841700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
neutron 2:10.0.7-0ubuntu1~cloud3 has been promoted to ocata-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841700 Title: instance ingress bandwidth limiting doesn't works in ocata. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1841700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
The reverted package has passed regression testing: == Totals == Ran: 94 tests in 895.3082 sec. - Passed: 89 - Skipped: 5 - Expected Fail: 0 - Unexpected Success: 0 - Failed: 0 Sum of execute time for each test: 517.6046 sec. I'm going to move this bug to Incomplete for now, since the fix has been reverted. ** Changed in: cloud-archive/ocata Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841700 Title: instance ingress bandwidth limiting doesn't works in ocata. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1841700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
Switching back to verification-ocata-failed since it did in fact fail. We'll leave it in that state. ** Tags removed: verification-ocata-needed ** Tags added: verification-ocata-failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841700 Title: instance ingress bandwidth limiting doesn't works in ocata. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1841700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
@jorge, thanks. I've uploaded neutron 2:10.0.7-0ubuntu1~cloud3 which will revert them. ** Changed in: cloud-archive/ocata Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841700 Title: instance ingress bandwidth limiting doesn't works in ocata. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1841700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
@corey.bryant, Yes corey, please go ahead. If this issue re-surfaces again, i'll provide you a new proposal that fixes the case mentioned before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841700 Title: instance ingress bandwidth limiting doesn't works in ocata. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1841700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
@jorge, can I revert the patches that are in ocata-proposed for this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841700 Title: instance ingress bandwidth limiting doesn't works in ocata. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1841700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
I have tested the different upgrade scenarios outlayed on the spreadsheet linked to this case. I found an error with existing qos policies when upgrading from pike to ocata-patched which might require a further change on the patchset. I will mark this verification as failed and re-submit a new patch with the required bits. The results with all other combinations are shared next. Bundle deployed: http://paste.ubuntu.com/p/tMNX577zCk/ Steps executed: juju config neutron-api enable-qos=true ubuntu@niedbalski-bastion:~/stsstack-bundles/openstack$ openstack network qos policy create bw-limit +-+--+ | Field | Value| +-+--+ | description | | | id | 7e6d0652-6cd4-4d5c-b58e-b7664c1c4587 | | is_default | None | | name| bw-limit | | project_id | 2c16c3a423444a43a39e11fcc768ad22 | | rules | [] | | shared | False| +-+--+ openstack network qos rule create --type bandwidth-limit --max-kbps 300 --max-burst-kbits 300 --ingress bw-limit ++--+ | Field | Value| ++--+ | direction | ingress | | id | eda4481f-61d0-4f52-91f7-fe979f776705 | | max_burst_kbps | 300 | | max_kbps | 300 | | name | None | | project_id | | ++--+ openstack network qos rule list bw-limit +--+--+-+--+-+--+---+---+ | ID | QoS Policy ID| Type| Max Kbps | Max Burst Kbits | Min Kbps | DSCP mark | Direction | +--+--+-+--+-+--+---+---+ | eda4481f-61d0-4f52-91f7-fe979f776705 | 7e6d0652-6cd4-4d5c-b58e-b7664c1c4587 | bandwidth_limit | 300 | 300 | | | ingress | +--+--+-+--+-+--+-- ubuntu@niedbalski-bastion:~/stsstack-bundles/openstack$ openstack port list -f value | grep 10.5.150.5 7c010ca8-1e96-4419-a4e9-4c56da05c806 fa:16:3e:a1:38:50 ip_address='10.5.150.5', subnet_id='5bb6de3b-6c72-4ef5-a0c2-821dfafaa822' N/A ubuntu@niedbalski-bastion:~/stsstack-bundles/openstack$ openstack port list -f value | grep 10.5.150.0 8c44909b-a4cf-4c7b-903f-f9f31f4a8045 fa:16:3e:4d:53:4e ip_address='10.5.150.0', subnet_id='5bb6de3b-6c72-4ef5-a0c2-821dfafaa822' N/A ubuntu@niedbalski-bastion:~/stsstack-bundles/openstack$ openstack port set 7c010ca8-1e96-4419-a4e9-4c56da05c806 --qos-policy 7e6d0652-6cd4 -4d5c-b58e-b7664c1c4587 ubuntu@niedbalski-bastion:~/stsstack-bundles/openstack$ openstack port set 8c44909b-a4cf-4c7b-903f-f9f31f4a8045 --qos-policy 7e6d0652-6cd4 -4d5c-b58e-b7664c1c4587 ubuntu@niedbalski-bastion:~/stsstack-bundles/openstack$ for port in $(openstack port list -f value -c ID); do openstack port show $port | grep qos; done | qos_policy_id | 7e6d0652-6cd4-4d5c-b58e-b7664c1c4587 | | qos_policy_id | 7e6d0652-6cd4-4d5c-b58e-b7664c1c4587 | Tempest run: http://paste.ubuntu.com/p/RPgrvvz25J/ Pre-patched version ubuntu@niedbalski-bastion:~/tempest$ openstack network qos policy show 30c09b4b-0c51-4679-99b9-23b62ba247d7 +-+--+ | Field | Value| +-+--+ | description | | | id | 30c09b4b-0c51-4679-99b9-23b62ba247d7 | | is_default | None | | name| bw-limit | | project_id | 2c16c3a423444a43a39e11fcc768ad22 | | rules | [] | | shared | False| +-+--+ 1 ubuntu@niedbalski-bastion:~/tempest$ openstack network qos rule create --type bandwidth-limit --max-kbps 300 --max-burst-kbits 300 30c09b4b-0c51-4679-99b9-23b62ba247d7 ++--+ | Field | Value
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
Test results will be collected through https://docs.google.com/spreadsheets/d/1ajozctmyHAKEBlG2Aet- Zdv7v9uFcRlIRiW5KeOk778/edit#gid=0 , please feel free to add any missing test case on that document. ** Description changed: [Environment] Xenial-Ocata deployment [Description] The instance ingress bandwidth limit implementation was targeted for Ocata [0], but the full implementation ingress/egress was done during the pike [1] cycle. However, isn't reported or explicit that ingress direction isn't supported in ocata, which causes the following exception when --ingress is specified. + It would be desirable for this feature to be available on Ocata for being able to + set ingress/egress bandwidth limits on the ports. + + [Testing] + + Without these patches, trying to set a ingress bandwidth-limit rule + the following exception will be raised. + $ openstack network qos rule create --type bandwidth-limit --max-kbps 300 --max-burst-kbits 300 --ingress bw-limiter Failed to create Network QoS rule: BadRequestException: 400: Client Error for url: https://openstack:9696/v2.0/qos/policies//bandwidth_limit_rules, Unrecognized attribute(s) 'direction' - It would be desirable for this feature to be available on Ocata for being able to - set ingress/egress bandwidth limits on the ports. + A single policy set (without the --ingress parameter) as supported in + Ocata will just create a limiter on the egress side. + + + 1) Check the policy list + + $ openstack network qos policy list + +--+++-+--+ + | ID | Name | Shared | Default | Project | + +--+++-+--+ + | 2c9c85e2-4b65-4146-b7bf-47895379c938 | bw-limiter | False | None | c45b1c0a681d4d9788f911e29166056d | + +--+++-+--+ + + 2) Check that the qoes rule is set to 300 kbps. + + $ openstack network qos rule list 2c9c85e2-4b65-4146-b7bf-47895379c938 + + | 01eb228d-5803-4095-9e8e-f13d4312b2ef | 2c9c85e2-4b65-4146-b7bf- + 47895379c938 | bandwidth_limit | 300 | 300 | | | | + + + 3) Set the Qos policy on any port. + + $ openstack port set 9a74b3c8-9ed8-4670-ad1f-932febfcf059 --qos-policy + 2c9c85e2-4b65-4146-b7bf-47895379c938 + + $ openstack port show 9a74b3c8-9ed8-4670-ad1f-932febfcf059 | grep qos + | qos_policy_id | 2c9c85e2-4b65-4146-b7bf-47895379c938 | + + + 4) Check that the egress traffic rules have been applied + + # iperf3 -c 192.168.21.9 -t 10 + Connecting to host 192.168.21.9, port 5201 + [ 4] local 192.168.21.3 port 34528 connected to 192.168.21.9 port 5201 + [ ID] Interval Transfer Bandwidth Retr Cwnd + [ 4] 0.00-1.00 sec 121 KBytes 988 Kbits/sec 23 2.44 KBytes + [ 4] 7.00-8.00 sec 40.2 KBytes 330 Kbits/sec 14 3.66 KBytes + [ 4] 8.00-9.00 sec 36.6 KBytes 299 Kbits/sec 15 2.44 KBytes + [ 4] 9.00-10.00 sec 39.0 KBytes 320 Kbits/sec 18 3.66 KBytes + - - - - - - - - - - - - - - - - - - - - - - - - - + [ ID] Interval Transfer Bandwidth Retr + [ 4] 0.00-10.00 sec 435 KBytes 356 Kbits/sec 159 sender + [ 4] 0.00-10.00 sec 384 KBytes 314 Kbits/sec receiver + + iperf Done. + + 5) Check that no ingress traffic limit has been applied. + + # iperf3 -c 192.168.21.9 -R -t 10 + Connecting to host 192.168.21.9, port 5201 + Reverse mode, remote host 192.168.21.9 is sending + [ 4] local 192.168.21.3 port 34524 connected to 192.168.21.9 port 5201 + [ ID] Interval Transfer Bandwidth + [ 4] 0.00-1.00 sec 38.1 MBytes 319 Mbits/sec + [ 4] 8.00-9.00 sec 74.6 MBytes 626 Mbits/sec + [ 4] 9.00-10.00 sec 73.2 MBytes 614 Mbits/sec + - - - - - - - - - - - - - - - - - - - - - - - - - + [ ID] Interval Transfer Bandwidth Retr + [ 4] 0.00-10.00 sec 1.07 GBytes 918 Mbits/sec 1045 sender + [ 4] 0.00-10.00 sec 1.07 GBytes 916 Mbits/sec receiver + + + ---> + + 6) With the patches applied from the PPA or proposed, run the migration + steps on the neutron-api node, repeat the previous steps, but make sure + to specify the traffic direction with --ingress as follows: + + $ openstack network qos rule create --type bandwidth-limit --max-kbps 300 --ingress testing-policy + ++--+ + | Field | Value | + ++--+ + | direction | ingress | + | id | 6d01cefa-0042-40cd-ae74-bcb723ca7ca4 | + | max_burst_kbps | 0 | + | max_kbps | 300 | + | name | None | + | project_id | | + ++--+ + + 7) Set the policy into any server port. + + $ openstack port set 50b8f714-3ee4-4260-8359-820420471bdb --qos-policy + fac2be5e-64e0-4308-b477-0f8c0096c0b8 + + 8) Check that the policy has been applied + + $ openstack port show 50b8f714-3ee4-4260-8359-820420471bdb | grep qos + | qos_policy_id |
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
** Changed in: cloud-archive/ocata Status: New => Triaged ** Changed in: cloud-archive/ocata Importance: Undecided => Medium ** Changed in: cloud-archive/ocata Importance: Medium => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841700 Title: instance ingress bandwidth limiting doesn't works in ocata. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1841700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
** Changed in: neutron (Ubuntu Xenial) Status: New => Invalid ** Also affects: cloud-archive/ocata Importance: Undecided Status: New ** Changed in: cloud-archive Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841700 Title: instance ingress bandwidth limiting doesn't works in ocata. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1841700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
** Patch added: "lp1841700-xenial-ocata.debdiff" https://bugs.launchpad.net/neutron/+bug/1841700/+attachment/5287521/+files/lp1841700-xenial-ocata.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841700 Title: instance ingress bandwidth limiting doesn't works in ocata. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1841700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
Waiting on OE approval. * Testing cases comments have been updated, the xenial-ocata debdiff patch is on the previous comment. ** Patch removed: "lp1841700-xenial-ocata.debdiff" https://bugs.launchpad.net/neutron/+bug/1841700/+attachment/5287520/+files/lp1841700-xenial-ocata.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841700 Title: instance ingress bandwidth limiting doesn't works in ocata. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1841700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
** Patch added: "lp1841700-xenial-ocata.debdiff" https://bugs.launchpad.net/neutron/+bug/1841700/+attachment/5287520/+files/lp1841700-xenial-ocata.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841700 Title: instance ingress bandwidth limiting doesn't works in ocata. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1841700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
Hello,
I've tested the PPA on
https://launchpad.net/~niedbalski/+archive/ubuntu/hf-00237904/ with
xenial-ocata deployed cloud.
Please note that it's a requirement to run the migrations steps up to
heads.
ubuntu@niedbalski-bastion:~/octavia/openstack$ juju config neutron-api
enable-qos=True
| 50b8f714-3ee4-4260-8359-820420471bdb | | fa:16:3e:88:c1:a0 |
ip_address='10.5.150.6', subnet_id='7daca73f-31ab-4401-bc6e-
e74dd38b7fc1' | N/A|
ubuntu@niedbalski-bastion:~/octavia/openstack$ openstack network qos policy
create testing-policy --share
+-+--+
| Field | Value|
+-+--+
| description | |
| id | fac2be5e-64e0-4308-b477-0f8c0096c0b8 |
| is_default | None |
| name| testing-policy |
| project_id | d215199a727a4384ad7d43825e86ff69 |
| rules | [] |
| shared | True |
| tags| [] |
+-+--+
ubuntu@niedbalski-bastion:~/octavia/openstack$ openstack network qos rule
create --type bandwidth-limit --max-kbps 300 --ingress testing-policy
Failed to create Network QoS rule: BadRequestException: 400: Client Error for
url:
http://10.5.0.66:9696/v2.0/qos/policies/fac2be5e-64e0-4308-b477-0f8c0096c0b8/bandwidth_limit_rules,
{"NeutronError": {"message": "Unrecognized attribute(s) 'direction'", "type":
"HTTPBadRequest", "detail": ""}}
> With the patch applied
neutron-api
root@juju-cd6736-1841700-4:/home/ubuntu# systemctl status neutron*
● neutron-server.service - OpenStack Neutron Server
Loaded: loaded (/lib/systemd/system/neutron-server.service; enabled; vendor
preset: enabled)
Active: active (running) since Mon 2019-09-09 15:47:00 UTC; 1min 39s ago
Process: 13597 ExecStartPre=/bin/chown neutron:adm /var/log/neutron
(code=exited, status=0/SUCCESS)
ubuntu@juju-cd6736-1841700-4:~$ sudo su
root@juju-cd6736-1841700-4:/home/ubuntu# dpkg -l |grep neutron
ii neutron-common
2:10.0.7-0ubuntu1~cloud1ubuntu1+hf1560961v20190826.13 all Neutron is a
virtual network service for Openstack - common
ii neutron-plugin-ml2
2:10.0.7-0ubuntu1~cloud1ubuntu1+hf1560961v20190826.13 all Neutron is a
virtual network service for Openstack - ML2 plugin
ii neutron-server
2:10.0.7-0ubuntu1~cloud1ubuntu1+hf1560961v20190826.13 all Neutron is a
virtual network service for Openstack - server
ii python-neutron
2:10.0.7-0ubuntu1~cloud1ubuntu1+hf1560961v20190826.13 all Neutron is a
virtual network service for Openstack - Python library
neutron-gateway
root@juju-cd6736-1841700-5:/home/ubuntu# dpkg -l | grep neutron
ii neutron-common
2:10.0.7-0ubuntu1~cloud1ubuntu1+hf1560961v20190826.13 all Neutron is a
virtual network service for Openstack - common
ii neutron-dhcp-agent
2:10.0.7-0ubuntu1~cloud1ubuntu1+hf1560961v20190826.13 all Neutron is a
virtual network service for Openstack - DHCP agent
ii neutron-l3-agent
2:10.0.7-0ubuntu1~cloud1ubuntu1+hf1560961v20190826.13 all Neutron is a
virtual network service for Openstack - l3 agent
ii neutron-lbaas-common 2:10.0.1-0ubuntu1~cloud0
all Neutron is a virtual network service for Openstack -
common
ii neutron-lbaasv2-agent2:10.0.1-0ubuntu1~cloud0
all Neutron is a virtual network service for Openstack -
LBaaSv2 agent
ii neutron-metadata-agent
2:10.0.7-0ubuntu1~cloud1ubuntu1+hf1560961v20190826.13 all Neutron is a
virtual network service for Openstack - metadata agent
ii neutron-metering-agent
2:10.0.7-0ubuntu1~cloud1ubuntu1+hf1560961v20190826.13 all Neutron is a
virtual network service for Openstack - metering agent
ii neutron-openvswitch-agent
2:10.0.7-0ubuntu1~cloud1ubuntu1+hf1560961v20190826.13 all Neutron is a
virtual network service for Openstack - Open vSwitch plugin agent
ii python-neutron
2:10.0.7-0ubuntu1~cloud1ubuntu1+hf1560961v20190826.13 all Neutron is a
virtual network service for Openstack - Python library
root@juju-cd6736-1841700-5:/home/ubuntu# systemctl status
neutron-openvswitch-agent
● neutron-openvswitch-agent.service - Openstack Neutron Open vSwitch Plugin
Agent
Loaded: loaded (/lib/systemd/system/neutron-openvswitch-agent.service;
enabled; vendor preset: enabled)
Active: active (running) since Mon 2019-09-09 15:52:12 UTC; 1min 58s ago
compute-node
root@juju-cd6736-1841700-8:/home/ubuntu# systemctl list-unit-files neutron*
UNIT FILE
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
** Also affects: neutron (Ubuntu) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: neutron (Ubuntu) Status: New => Fix Released ** Also affects: cloud-archive Importance: Undecided Status: New ** Changed in: neutron Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841700 Title: instance ingress bandwidth limiting doesn't works in ocata. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1841700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
