This is a special case of bug 1303714 I think. The only time we should care about the value of force_config_drive is on first boot of the instance. A hard reboot should just give you what you already had, even if the value of this flag has changed in the mean time.
This is a special case of bug 1303714 I think. The only time we should care about the value of force_config_drive is on first boot of the instance. A hard reboot should just give you what you already had, even if the value of this flag has changed in the mean time.