2 ms·
The same issue occurs on 4.4.4 (and other versions), so it's not specific to 5.0.1.
by joesmo 12y ago
The same issue occurs on 4.4.4 (and other versions), so it's not specific to 5.0.1.
- ansible 12y agoThe same issue occurs on 4.4.4 (and other versions), so it's not specific to 5.0.1. Well... I'd never seen it happen at all in the previous releases. And with 5.0.1, I saw it happen twice in three days.