Description of problem: While running BVT sanity on the nightly rebalance logs shows the message "failed to get trusted.distribute.linkinfo key" error messages. Version-Release number of selected component (if applicable): BVT nightly How reproducible: Steps to Reproduce: 1. Automation run creates a 4x2 distributed-replicate volume 2. created some symlinks on the mount point 3. added a pair of brick and start rebalance gluster v rebalance <vol> start Actual results: [2013-12-03 03:16:23.143652] E [dht-rebalance.c:1272:gf_defrag_migrate_data] 0-hosdu-dht: /51: failed to get trusted.distribute.linkinfo key - Success [2013-12-03 03:16:23.145327] E [dht-rebalance.c:1272:gf_defrag_migrate_data] 0-hosdu-dht: /53: failed to get trusted.distribute.linkinfo key - Success [2013-12-03 03:16:23.146741] E [dht-rebalance.c:1272:gf_defrag_migrate_data] 0-hosdu-dht: /54: failed to get trusted.distribute.linkinfo key - Success [2013-12-03 03:16:23.148289] E [dht-rebalance.c:1272:gf_defrag_migrate_data] 0-hosdu-dht: /58: failed to get trusted.distribute.linkinfo key - Success [2013-12-03 03:16:23.149796] E [dht-rebalance.c:1272:gf_defrag_migrate_data] 0-hosdu-dht: /61: failed to get trusted.distribute.linkinfo key - Success [2013-12-03 03:16:23.151048] E [dht-rebalance.c:1272:gf_defrag_migrate_data] 0-hosdu-dht: /62: failed to get trusted.distribute.linkinfo key - Success [2013-12-03 03:16:23.152323] E [dht-rebalance.c:1272:gf_defrag_migrate_data] 0-hosdu-dht: /64: failed to get trusted.distribute.linkinfo key - Success [2013-12-03 03:16:23.153448] E [dht-rebalance.c:1272:gf_defrag_migrate_data] 0-hosdu-dht: /65: failed to get trusted.distribute.linkinfo key - Success
Bug got introduced from patch : https://code.engineering.redhat.com/gerrit/16455
Created attachment 832062 [details] Rebalance Log Rebalance log during the tests
Please set the priority.
Please set priority.
Verified on 3.4.0.52rhs-1.el6rhs.x86_64. Now upon rebalance no such messages will appear in the rebalance log and no failures are seen in the rebalance
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0208.html