Failed to restart nova-compute.service: Unit var-lib-nova-instances.mount not found
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Compute Charm |
Triaged
|
Undecided
|
Unassigned |
Bug Description
channel: 2023.2/stable
ubuntu: jammy
after scaling back a nova-compute unit according to https:/
so after running juju add-unit nova-compute --to x and I noticed into the juju log:
WARNING unit.nova-
SO I ssh into the host and executed:
# systemctl status nova-compute.
○ nova-compute.
Loaded: loaded (/lib/systemd/
Drop-In: /etc/systemd/
Active: inactive (dead)
and then:
systemctl start nova-compute.
Failed to start nova-compute.
from the juju client:
juju status nova-compute
Model Controller Cloud/Region Version SLA Timestamp
openstack maas-controller1 maas-cloud/default 3.2.4 unsupported 18:04:41Z
App Version Status Scale Charm Channel Rev Exposed Message
nova-compute 28.0.1 blocked 1 nova-compute 2023.2/stable 718 no Services not running that should be: nova-compute
ovn-chassis-gw active 0 ovn-dedicated-
Unit Workload Agent Machine Public address Ports Message
nova-compute/40* blocked idle 8 192.168.6.110 Services not running that should be: nova-compute
Machine State Address Inst id Base AZ Message
8 started 192.168.6.110 op1 ubuntu@22.04 default Deployed
I suspect that there's something not being cleaned up properly, as part of the scale back of the nova-compute unit.
It's fairly unusual to scale back from a machine and then try to scale out using the same machine, which is probably why this bug hasn't surfaced before. Please could you let us know the use case for this? i.e. are you trying to solve some other issue and scaling back was a proposed solution? Thanks.