This bug is no longer as easy to reproduced as it used to be (it's either intermittent now or requires a more complex configuration), so it can't be a release blocker for 4.1.1.
This bug is no longer as easy to reproduced as it used to be (it's either intermittent now or requires a more complex configuration), so it can't be a release blocker for 4.1.1.