I think I found a workaround. I have downgraded one of my node to 5.5.0 build 3029944
So from the 5.0 host I migrated the affected machine to this host, and from here I could move to the to 5.5u3b host.
This would mean that the bug have been introduced somewhere between 3029944 and 3343343