Red Hat Bugzilla – Bug 965935
[Runtime_card#296] User bandwidth limits will not take effect any more after move gear to another node
Last modified: 2015-05-14 19:19:29 EDT
Description of problem:
Add bandwidth limit to gear via "service libra-tc throttleuser/highuser <gear_uuid>" command. Then move the gear form the current node to any other nodes.
The issue happens on both in-district move and across-district move.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Setup multi-node env
2. Create app on them
3. Set the app bandwidth limit via libra-tc
#service libra-tc throttleuser <gear_uuid>
4. Move the gear to other node
5. Do some download operation in the gear rhcsh to check the bandwidth limit
The bandwidth limit of this gear will not take effect anymore. Which should be trottleuser in this case.
[app2-bmeng.dev.rhcloud.com repo]\> wget http://ipv4.download.thinkbroadband.com/1GB.zip
--2013-05-21 23:25:49-- http://ipv4.download.thinkbroadband.com/1GB.zip
Resolving ipv4.download.thinkbroadband.com... 126.96.36.199
Connecting to ipv4.download.thinkbroadband.com|188.8.131.52|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1073741824 (1.0G) [application/zip]
Saving to: “1GB.zip.2”
8% [==========> ] 95,346,128 19.2M/s eta 62s
According the bandwidth limit setting, the throttleuser should be limited to small bandwidth. No more than 1M/s.
The limit files can be moved to the target node during move with correct path.
A misunderstanding about the feature was corrected late in the sprint. This bug pertains to a part of the feature which is no longer being shipped.