Comment 5 for bug 2023559

we have had issues with cirros 0.6.1 on the following ovh nodes:
099ba2e09fdc07b1847717a9b605112a16b4c7d4bfd924c9204ac49d
4d0350f888b309b8d2e628a59a85c1905e6dccd534e51049e6a6e0f1
560fe06e257c2ed81871df3104745dc5fc659e07c014dd31ab3a8280
59c448d249b292e509024e00e4e5315a4444dbdf490a12ebfa08c39f
66d00b79b256c1947d6bf74aa6d9bd31fc890c6738ee0ed488eef181
a6224c46f83f86c84653df2192d459c42eecb5dcdcc4965ac30d712b
ad125c505c91c68a706349c615ed32c6fcafcba94ce88dcf4c5daf7b
d20529c2ad1a7b430915b3c684af9be02801b6d085a08a0c2c116f65
df3d8152cdd0cb80521ac739fdbf99c52076bd41d33eecd71d76b87a
eabba74e8469f0162dd549af83cd8cfcdb1b770b9babf6c2e8041a13
f4d8e912dd3fd42e525c9d1f783bb8a07b585c890bf54d12a806e868

when using cirros 0.6.2, it passes on the following nodes (and so far no failures):
099ba2e09fdc07b1847717a9b605112a16b4c7d4bfd924c9204ac49d
3628215d011fcba31a52b321cda4df0b2dc1cc351281446abce79714
420efd617526638d396ed0a71c391db260c7ce2f54808e8f8e506ca7
560fe06e257c2ed81871df3104745dc5fc659e07c014dd31ab3a8280
73966f2818137418add0485e4e59a0b5ad42734cd696393114dd9d77
af9aade2265164308bd1d2c9f09fe87cb5a2c757cd79509c260a8625
d20529c2ad1a7b430915b3c684af9be02801b6d085a08a0c2c116f65
eabba74e8469f0162dd549af83cd8cfcdb1b770b9babf6c2e8041a13

4 nodes that were failing with 0.6.1 are now passing with 0.6.2