Should disable compute / put host in maintenance mode before migrating

Bug #1503724 reported by Dmitry Sutyagin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel Documentation Team
7.0.x
Won't Fix
Medium
Fuel Documentation Team

Bug Description

Current Fuel documentation - https://docs.mirantis.com/openstack/fuel/fuel-7.0/operations.html#adding-redeploying-and-replacing-nodes does not say anything about the need to disable nova-compute service via
`nova service-disable <node> nova-compute`
or put the host into maintenance mode via
`nova host-update --maintenance enable <node>`
(should result in the same thing, but I'm not 100% sure)
Users may end up redeploying a node which still has newly spawned instances.

Changed in fuel:
importance: Undecided → Medium
assignee: nobody → Fuel Documentation Team (fuel-docs)
Changed in fuel:
status: New → Confirmed
Changed in fuel:
milestone: none → 7.0-updates
Revision history for this message
Vitaly Sedelnik (vsedelnik) wrote :

Won't Fix for 7.0-updates because of Medium importance

Changed in fuel:
status: Confirmed → Won't Fix
Changed in fuel:
milestone: 7.0-updates → 8.0
no longer affects: fuel/future
Changed in fuel:
status: Won't Fix → Confirmed
Dmitry Pyzhov (dpyzhov)
no longer affects: fuel/8.0.x
tags: added: area-docs
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.