Multiple unused heat-engine are left after the deployment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat Charm |
Triaged
|
Low
|
Unassigned |
Bug Description
With multiple Heat units, a lot of unused (down) heat-engine will be shown up in `openstack orchestration service list`. It would be nice if Heat charm cleans up after a deployment or as an charm action like cinder charm action of `remove-services`.
$ openstack orchestration service list | grep -w up -c
42
openstack orchestration service list | grep -w down -c
42
$ openstack orchestration service list | grep juju-8ce0c5-0-lxd-8
| juju-8ce0c5-0-lxd-8 | heat-engine | 4b1c2bb7-
| juju-8ce0c5-0-lxd-8 | heat-engine | b1ef9cb6-
| juju-8ce0c5-0-lxd-8 | heat-engine | 3ef8f77f-
| juju-8ce0c5-0-lxd-8 | heat-engine | f2464220-
| juju-8ce0c5-0-lxd-8 | heat-engine | e43b7633-
| juju-8ce0c5-0-lxd-8 | heat-engine | c3041f40-
| juju-8ce0c5-0-lxd-8 | heat-engine | a30edcad-
| juju-8ce0c5-0-lxd-8 | heat-engine | a354d66b-
| juju-8ce0c5-0-lxd-8 | heat-engine | d8ef67e0-
| juju-8ce0c5-0-lxd-8 | heat-engine | d640d2d0-
| juju-8ce0c5-0-lxd-8 | heat-engine | 2d9b121c-
| juju-8ce0c5-0-lxd-8 | heat-engine | 5d836128-
| juju-8ce0c5-0-lxd-8 | heat-engine | d506aff5-
| juju-8ce0c5-0-lxd-8 | heat-engine | 3dcc8381-
| juju-8ce0c5-0-lxd-8 | heat-engine | 5a7d94ca-
| juju-8ce0c5-0-lxd-8 | heat-engine | 11051e40-
| juju-8ce0c5-0-lxd-8 | heat-engine | 2f3712b4-
| juju-8ce0c5-0-lxd-8 | heat-engine | 31f4584b-
| juju-8ce0c5-0-lxd-8 | heat-engine | c86567af-
| juju-8ce0c5-0-lxd-8 | heat-engine | b6732b72-
| juju-8ce0c5-0-lxd-8 | heat-engine | 8ff3805b-
| juju-8ce0c5-0-lxd-8 | heat-engine | 2df84cb4-
| juju-8ce0c5-0-lxd-8 | heat-engine | a54cad28-
| juju-8ce0c5-0-lxd-8 | heat-engine | 553e5757-
| juju-8ce0c5-0-lxd-8 | heat-engine | 3c8a8b09-
| juju-8ce0c5-0-lxd-8 | heat-engine | 32553bae-
| juju-8ce0c5-0-lxd-8 | heat-engine | 1f1c52ff-
| juju-8ce0c5-0-lxd-8 | heat-engine | 64b011ef-
tags: | added: cpe-onsite |
I can confirm that I see the same behaviour - however I'd like to understand why we end up with crufty worker entries.