Have you tried running the OSM diagnostic script as @DavidGoldwasser describes in this post? If that script does not currently address this case it should, you could add a feature request to add this if it does not already work.