Build tested: 1.4.2-1, 1.4.3-6

Configurations tested: 1um2pm, 3pm combo

After installation, before running any mysql commands, the err.log file in all nodes contains the messages like the following. If these messages are produced by the postConfigure when trying to setup glusterfs, then we need to check why there errors occurred. If they are expected (ie, waiting for columns to be available) , then we should not log them as errors.

Apr 8 15:38:26 localhost ProcessMonitor[14199]: 26.437564 |0|0|0| E 18 CAL0000: glusterUnassign mount failure: dbroot: 2 error: 32
Apr 8 15:38:26 localhost ProcessMonitor[14199]: 26.444320 |0|0|0| E 18 CAL0000: glusterUnassign mount failure: dbroot: 3 error: 32
Apr 8 15:40:52 localhost ProcessMonitor[14199]: 52.127981 |0|0|0| E 18 CAL0000: glusterAssign mount failure: dbroot: 1 error: 255
Apr 8 15:40:52 localhost ProcessMonitor[14199]: 52.172279 |0|0|0| E 18 CAL0000: glusterUnassign mount failure: dbroot: 2 error: 255
Apr 8 15:40:52 localhost ProcessMonitor[14199]: 52.178277 |0|0|0| E 18 CAL0000: glusterUnassign mount failure: dbroot: 3 error: 32
Apr 8 15:41:04 localhost ProcessMonitor[14199]: 04.368413 |0|0|0| E 18 CAL0000: glusterAssign mount failure: dbroot: 1 error: 255
Apr 8 15:41:04 localhost ProcessMonitor[14199]: 04.412123 |0|0|0| E 18 CAL0000: glusterUnassign mount failure: dbroot: 2 error: 32
Apr 8 15:41:04 localhost ProcessMonitor[14199]: 04.419081 |0|0|0| E 18 CAL0000: glusterUnassign mount failure: dbroot: 3 error: 32