For what it's worth we encountered this issue on 6.7 and a rollback of the agents to 6.6 has resolved the issue for us. While we're all waiting for a fix, this is better than nothing.
↧
For what it's worth we encountered this issue on 6.7 and a rollback of the agents to 6.6 has resolved the issue for us. While we're all waiting for a fix, this is better than nothing.