Changing NFS IPs in Chefs messes up /etc/fstab

When changing the IP addresses of NFS clients they seem to be appended to /etc/fstab instead of overwriting the existing ones. I ran into this when changing a DB host for staging. In this case Chef decided it was a great idea to change the IPs to the incorrect one in my commit. Not thinking much of it (after all the data is pulled from the Chef server, thus it should be in use) I just applied it. I then later reverted it when I found out what was going on.

At the moment worker1.staging as a result is refusing to mount the NFS drives as far as I can tell, despite the IP being correct (at least it matches the nfs staging host).