Bug 1262126 - nova host-update <uuid> --maintenance enable fails
nova host-update <uuid> --maintenance enable fails
Status: CLOSED NOTABUG
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova (Show other bugs)
7.0 (Kilo)
x86_64 Linux
unspecified Severity low
: ---
: 8.0 (Liberty)
Assigned To: Eoghan Glynn
nlevinki
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-10 17:17 EDT by Arthur Enright
Modified: 2015-09-18 10:40 EDT (History)
13 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-09-18 10:40:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Arthur Enright 2015-09-10 17:17:55 EDT
Description of problem:

nova host-update <uuid> --maintenance enable fails when using the kvm compute plugin.

This bug exists upstream here: https://bugs.launchpad.net/nova/+bug/1465176


Version-Release number of selected component (if applicable):

RHEL-OSP 7 GA


How reproducible:

100%


Steps to Reproduce:
1. run the above command
2.
3.

Actual results:

fails, I don't have an environment to run the command on to give the exact output ATM


Expected results:

Put's compute node in maintenance mode


Additional info:

As a workaround you can run the following command from one of the controller nodes (after pulling in the overcloudrc file from the undercloud):

# nova-manage service disable --host <host> --service openstack-nova-compute
Comment 3 Alexander Chuzhoy 2015-09-10 17:22:17 EDT
I get:

ERROR (NotFound): Compute host <UUID> could not be found. (HTTP 404) (Request-ID: req-17bbf512-3a9d-4bab-bd81-507f7297e73a)
Comment 4 Stephen Gordon 2015-09-18 10:40:15 EDT
Host maintenance mode is a Xen specific concept and as such is not implemented by the other drivers. The closest equivalent for Libvirt/KVM today is to disable the service (the stated workaround) and call host-evacuate (or alternatively issue host-servers-migrate or host-evacuate-live before disabling the service).

Note You need to log in before you can comment on or make changes to this bug.