applier doesn't consider hypervisor type

Bug #1777691 reported by semen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
watcher
Invalid
Undecided
Unassigned

Bug Description

When we have several different hypervisors running under one Openstack environment, watcher audit can be successfully performed but an action plan can not be fully executed because watcher applier tries to live migrate instances to unsupported hypervisor.

My current hypervisors: KVM, XEN, Hyper-V.
All VMs are running on KVM nodes. Watcher tries to migrate to XEN.

2018-06-19 19:25:20.191 4410 ERROR watcher.applier.workflow_engine.default BadRequest: Unable to migrate instance (e46d04bd-f826-4d1f-b351-a6c5ffa863a2) to current host (ovm2.openstack.local).

We need to have an ability to limit basic cluster model per availability zones or build cluster model considering exact hypervisor type.

Revision history for this message
Alexander Chadin (joker946) wrote :

Semen, you can use scope of audit template to define both host_aggregates or availability_zones scopes. See more here: https://github.com/openstack/python-watcherclient/blob/master/watcherclient/v1/audit_template_shell.py#L165

Changed in watcher:
status: New → Invalid
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.