From ae9542eb7da22ad6bcd59145c56b2781aa7b507a Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Tue, 3 Oct 2017 16:34:26 -0400 Subject: [PATCH] api-ref: add note about rebuild not replacing volume-backed root disk We've had several bugs about this over the years, and until we actually decide to fix it (or not), we should point out the known limitation that volume-backed root disks are not replaced during a rebuild. Like, if you have a volume-backed instance and rebuild with a new image, the root disk is still the volume with the original image. Change-Id: I145cab88f782e4b1e630cc432322bc8436413e71 Related-Bug: #1482040 --- api-ref/source/servers-actions.inc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/api-ref/source/servers-actions.inc b/api-ref/source/servers-actions.inc index 1265bac6b6db..6254ad8d4080 100644 --- a/api-ref/source/servers-actions.inc +++ b/api-ref/source/servers-actions.inc @@ -458,6 +458,11 @@ Rebuilds a server. Specify the ``rebuild`` action in the request body. +.. note:: There is a `known limitation`_ where the root disk is not + replaced for volume-backed instances during a rebuild. + +.. _known limitation: https://bugs.launchpad.net/nova/+bug/1482040 + Normal response codes: 202 Error response codes: badRequest(400), unauthorized(401), forbidden(403),