I deploy openstack-base-78,but nova-compute service is not running

1

Hi,all.

I deploy openstack-base-78

But when juju status:

nova-compute/0               blocked   idle   0        10.0.0.159                         Services not running that should be: nova-compute, nova-api-metadata
  ntp/2                      active    idle            10.0.0.159      123/udp            chrony: Ready
  ovn-chassis/2              active    idle            10.0.0.159                         Unit is ready
nova-compute/1               blocked   idle   1        10.0.0.157                         Services not running that should be: nova-compute, nova-api-metadata
  ntp/1                      active    idle            10.0.0.157      123/udp            chrony: Ready
  ovn-chassis/1              active    idle            10.0.0.157                         Unit is ready
nova-compute/2*              blocked   idle   2        10.0.0.158                         Services not running that should be: nova-compute, nova-api-metadata
  ntp/0*                     active    idle            10.0.0.158      123/udp            chrony: Ready
  ovn-chassis/0*             active    idle            10.0.0.158                         Unit is ready

the log is:

 juju show-status-log nova-compute/0
Time                        Type       Status     Message
06 Nov 2021 10:02:47+08:00  workload   blocked    Services not running that should be: nova-api-metadata, nova-compute
06 Nov 2021 10:18:55+08:00  workload   blocked    Services not running that should be: nova-compute, nova-api-metadata
06 Nov 2021 10:19:57+08:00  juju-unit  executing  running image-service-relation-changed hook for glance/0
06 Nov 2021 10:20:17+08:00  workload   active     Unit is ready
06 Nov 2021 10:20:18+08:00  juju-unit  executing  running cloud-compute-relation-changed hook for nova-cloud-controller/0
06 Nov 2021 10:20:37+08:00  workload   blocked    Services not running that should be: nova-api-metadata, nova-compute
06 Nov 2021 10:21:08+08:00  juju-unit  idle
06 Nov 2021 10:22:36+08:00  juju-unit  executing  running cloud-compute-relation-changed hook for nova-cloud-controller/0
06 Nov 2021 10:22:51+08:00  workload   active     Unit is ready
06 Nov 2021 10:23:10+08:00  workload   blocked    Services not running that should be: nova-compute, nova-api-metadata
06 Nov 2021 10:23:11+08:00  juju-unit  idle
06 Nov 2021 10:24:37+08:00  juju-unit  executing  running cloud-compute-relation-changed hook for nova-cloud-controller/0
06 Nov 2021 10:24:54+08:00  workload   active     Unit is ready
06 Nov 2021 10:24:55+08:00  juju-unit  idle
06 Nov 2021 10:53:39+08:00  workload   blocked    Services not running that should be: nova-compute, nova-api-metadata
06 Nov 2021 11:12:42+08:00  workload   blocked    Services not running that should be: nova-api-metadata, nova-compute
06 Nov 2021 11:24:25+08:00  juju-unit  executing  running start hook
06 Nov 2021 11:25:49+08:00  juju-unit  executing  running leader-settings-changed hook
06 Nov 2021 11:25:49+08:00  juju-unit  idle
06 Nov 2021 11:28:26+08:00  workload   blocked    Services not running that should be: nova-compute, nova-api-metadata

Why it is happend ?thank you!

2

I would suggest checking the following logs on those nova-compute units:

systemctl status nova-compute
systemctl status nova-api-metadata
less /var/log/nova/nova-compute.log
less /var/log/nova/nova-api-metadata.log

Sometimes things race and you have to start the services, sometimes there may be a missing relation or a bad binding (lack of connectivity) between two applications based on bindings in your bundle.

3

Hi@ afreiberger.Thank you!

I fellow your said ,and output is :

nova-api-metadata.service: Scheduled restart job, restart counter is at 5.

The log is pasted here

The juju status compute --relations is pasted here.

Thank you again!

1 Like
4

It appears that your hostnames of the metals that you’re deploying the bundle to are named 157, 158, and 159.

The ovn metadata agent log shows that it’s not properly processing this because it’s expecting an alphabetical character in the starting position if it’s a hostname, and a full dotted quad IP address if it’s an IPv4 address.

This article explains that while RFC 1123 relaxes a constraint of RFC 952 that hostnames must begin with an alphabetical character, however, it was provided in RFC 1178 guidelines to choose a valid hostname because of implementations issues

      Don't use digits at the beginning of the name.

         Many programs accept a numerical internet address as well as a
         name.  Unfortunately, some programs do not correctly
         distinguish between the two and may be fooled, for example, by
         a string beginning with a decimal digit.

         Names consisting entirely of hexadecimal digits, such as
         "beef", are also problematic, since they can be interpreted
         entirely as hexadecimal numbers as well as alphabetic strings.

I would suggest renaming your hosts starting with an character between A and Z to be in accordance with hostname RFC 952 and then re-deploying the bundle.

-Drew

1 Like
5

Thank you @ afreiberger.

It worked.So awesome！

 juju status nova-compute
Model      Controller       Cloud/Region    Version  SLA          Timestamp
openstack  maas-controller  mymaas/default  2.9.18   unsupported  13:09:22+08:00

App           Version  Status  Scale  Charm         Store       Channel  Rev  OS      Message
ceph-osd      16.2.6   active      3  ceph-osd      charmstore  stable   315  ubuntu  Unit is ready (1 OSD)
nova-compute  24.0.0   active      3  nova-compute  charmstore  stable   337  ubuntu  Unit is ready
ntp           3.5      active      3  ntp           charmstore  stable    47  ubuntu  chrony: Ready
ovn-chassis   21.09.0  active      3  ovn-chassis   charmstore  stable    21  ubuntu  Unit is ready

Unit              Workload  Agent  Machine  Public address  Ports    Message
ceph-osd/0        active    idle   0        10.0.0.157               Unit is ready (1 OSD)
ceph-osd/1*       active    idle   1        10.0.0.158               Unit is ready (1 OSD)
ceph-osd/2        active    idle   2        10.0.0.159               Unit is ready (1 OSD)
nova-compute/0    active    idle   0        10.0.0.157               Unit is ready
  ntp/1           active    idle            10.0.0.157      123/udp  chrony: Ready
  ovn-chassis/1   active    idle            10.0.0.157               Unit is ready
nova-compute/1*   active    idle   1        10.0.0.158               Unit is ready
  ntp/0*          active    idle            10.0.0.158      123/udp  chrony: Ready
  ovn-chassis/0*  active    idle            10.0.0.158               Unit is ready
nova-compute/2    active    idle   2        10.0.0.159               Unit is ready
  ntp/2           active    idle            10.0.0.159      123/udp  chrony: Ready
  ovn-chassis/2   active    idle            10.0.0.159               Unit is ready

Machine  State    DNS         Inst id  Series  AZ       Message
0        started  10.0.0.157  node157  focal   default  Deployed
1        started  10.0.0.158  node158  focal   default  Deployed
2        started  10.0.0.159  node159  focal   default  Deployed

Thank you again！

1 Like