Comment 2 for bug 1721068

I have gotten around this issue. I am not sure if there was anything found by developers in the community but I see this issue now has a milestone set.

I'm not sure how I got around this issue, but my theory is something I noticed quite by accident.

The servers I was having these troubles on use 80GB hard drives, but they also have a flash drive in them, for small OS deployments. I stumbled across a /dev/sda6 partition on these flash drives.

On this partition I found 2 files: meta-data and user-data. In those files was the old node name I mentioned in the original post. This partition must have been detected, and these stale files were used by fuel-agent when the newly provisioned node first booted, even though they were booting from the 80GB drive which had its own /dev/sda6 partition.

I suspect the stale/incorrect /dev/sda6 is probably is from Fuel 8 when we tried to deploy on some of these flash drives...

once I deleted the stale/incorrect /dev/sda6 then theprovisioning and deployment went perfectly

thanks