nova-live-migration job fails during evacuate negative test
Bug #1903979 reported by
Balazs Gibizer
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Lee Yarwood |
Bug Description
2020-11-12 08:55:30.829939 | controller | + /opt/stack/
2020-11-12 08:55:30.829994 | controller | Timed out waiting for server evacuate-test to go to ERROR status
2020-11-12 08:55:30.831833 | controller | + /opt/stack/
Example run:
https:/
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → High |
tags: | added: evacuate gate-failure testing |
Changed in nova: | |
assignee: | nobody → Lee Yarwood (lyarwood) |
Changed in nova: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Looks like libvirtd restarted allowing the negative evacuation test to result in an ACTIVE instance on the controller. The current task stops the following service and associated sockets:
roles/run- evacuate- hook/tasks/ main.yaml
34 - name: Stop libvirtd on "{{ inventory_hostname }}" admin.socket
35 become: true
36 systemd:
37 ¦ name: "{{ item }}"
38 ¦ state: stopped
39 with_items:
40 ¦ - libvirtd.service
41 ¦ - libvirtd.socket
42 ¦ - libvirtd-
43 ¦ - libvirtd-ro.socket
I guess I'm missing something here?