This issues re-occurred on already running (ie it's not freshly provisioned servers) CentOS 6.6, and also on CentOS 7.2.1511. What I observed is that
↧