Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-26373

When adding compute nodes, they are discovered but not in hypervisor list

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Undefined Undefined
    • None
    • None
    • nova-operator
    • None
    • Important

      When adding compute nodes, initially they are not discovered with

      oc rsh nova-cell1-conductor-0 nova-manage cell_v2 discover_hosts

      and they are discovered with the workaround in this article :

       

      $ oc rsh nova-cell0-conductor-0 nova-manage cell_v2 discover_hosts --by-service
      Modules with known eventlet monkey patching issues were imported prior to eventlet monkey patching: urllib3. This warning can usually be ignored if the caller is only importing and not executing nova code.
      2026-02-05 16:02:46.978 374589 WARNING oslo_policy.policy [None req-b5264f8e-9dbc-44f7-9d40-6217e5a96707 - - - - - -] JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html.
      2026-02-05 16:02:46.979 374589 WARNING oslo_policy.policy [None req-b5264f8e-9dbc-44f7-9d40-6217e5a96707 - - - - - -] JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html.
      $ oc rsh nova-cell1-conductor-0 nova-manage cell_v2 list_hosts
      Modules with known eventlet monkey patching issues were imported prior to eventlet monkey patching: urllib3. This warning can usually be ignored if the caller is only importing and not executing nova code.
      +-----------+--------------------------------------+---------------------------------------------+
      | Cell Name |              Cell UUID               |                   Hostname                  |
      +-----------+--------------------------------------+---------------------------------------------+
      |   cell1   | 0f75f421-d81b-433b-9122-48d604e6967f |    ******s03354.ctlplane.n46-rhoso.local    |
      |   cell1   | 0f75f421-d81b-433b-9122-48d604e6967f |    ******s03357.ctlplane.n46-rhoso.local    |
      |   cell1   | 0f75f421-d81b-433b-9122-48d604e6967f |    ******s03364.ctlplane.n46-rhoso.local    |
      |   cell1   | 0f75f421-d81b-433b-9122-48d604e6967f | ******s03382-ht-04.ctlplane.n46-rhoso.local |
      +-----------+--------------------------------------+---------------------------------------------+
      $ 

      However, only one host appears in the hypevisor list of openstack:

       

       

      oc rsh -n openstack openstackclient openstack hypervisor list
      +--------------------------------------+---------------------------------------------+-----------------+----------------+-------+
      | ID                                   | Hypervisor Hostname                         | Hypervisor Type | Host IP        | State |
      +--------------------------------------+---------------------------------------------+-----------------+----------------+-------+
      | 743c40e9-e153-4d48-ab05-0489fb5a5656 | *****s03382-ht-04.ctlplane.n46-rhoso.local | QEMU            | 192.168.18.164 | up    |
      +--------------------------------------+---------------------------------------------+-----------------+----------------+-------+
       

       

       

      The output of must-gather:

       

      oc adm must-gather  --image-stream=openshift/must-gather  --image=registry.redhat.io/rhoso-operators/openstack-must-gather-rhel9:1.0
      ...
      Reprinting Cluster State:
      When opening a support case, bugzilla, or issue please include the following summary data along with any other requested information:
      ClusterID: d2b8****-712e-****-****-****27ec2623
      ClientVersion: 4.18.32
      ClusterVersion: Stable at "4.18.32"
      ClusterOperators:
              All healthy and stable

       

       

       

      Expected behavior

      • The hypervisor list should be populated with all hosts in the nodelists that have been discovered

      Bug impact

      • RHOSO 18 compute nodes not available for workload

      Known workaround

      • Applied this article computes discovered but hypervisors not available

       

              mwitt@redhat.com melanie witt
              ixgnick.tca.pc Nikos Karandreas
              rhos-workloads-compute
              Ericsson Confidential Group
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: