Description of problem: When we backport a change from master to any other release branch, commit message of the change in master has "fixes : bz#n" and we also add another "fixes: bz#n" for referring to the BZ raised against that specific version. Smoke test is taking the first "fixes: bz#n" and checking whether the BZ is raised for the correct version and product. As the version is different and it finds another field "fixes: bz#n", the smoke is failing. Version-Release number of selected component (if applicable): How reproducible: always during backport.
I've added a tweak to the python scripts to handle this: https://github.com/gluster/glusterfs-patch-acceptance-tests/pull/168
Great, so it appears all our scripts actually break around this - SO when you do backports, things will break. People work around it by changing Fixes/Updates -> Bug for the old bug.
*** This bug has been marked as a duplicate of bug 1618407 ***