Comment 2 for bug 1669823

This is a known issue / existing behavior of Nova. In order to change it we'd need to propose a spec upstream.

>>> Impact: Customer also mentioned that the instance hangs when it's in this state, but I haven't been able to reproduce that part just yet.

Yeah, I don't think that's true: the only problem is that regular users are not allowed to read soft-deleted entries.

You can either resize the instances with deleted flavors or just forbid deletion of flavors in policy.json as a workaround for now.

As MOS (as it is) is in maintenance state now, I do not think we should do anything in downstream.