Doing so would confuse nova-scheduler, and may result in attempts
to schedule a new instance on such node. The API version is not
updated, as this behavior is broken already, we're just moving
the breakage to the API level.
Change-Id: I758587d36c927c8eed852170728f6267ae18f001