kolla-ansible stop ignores service placement, which may cause it to fail
Bug #1868596 reported by
Mark Goddard
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
Medium
|
Mark Goddard | ||
Stein |
Triaged
|
Medium
|
Unassigned | ||
Train |
Fix Released
|
Medium
|
Mark Goddard | ||
Ussuri |
Fix Released
|
Medium
|
Mark Goddard |
Bug Description
The 'kolla-ansible stop' command can be used to stop the services running on hosts. However, if you run this command in an environment with heterogeneous nodes (most real world scenarios have at least control/compute), then it fails. This is because it only checks whether a container is enabled, and not whether the host is in the correct group. For example, it fails with nova-libvirt:
No such container: nova_libvirt to stop.
Changed in kolla-ansible: | |
status: | New → Triaged |
importance: | Undecided → Medium |
description: | updated |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/714496
Review: https:/