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

Dell nodes are not provisioned because ironic agent can't create partitions properly

XMLWordPrintable

    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • None
    • HardProv Sprint 4
    • 1
    • Important

      To Reproduce Steps to reproduce the behavior:
      A customer with RHOSP 17.1.4 deployment tries to add extra compute nodes to the cloud and is unable to do so for majority of nodes in batch (9 out of 10). From Ironic Conductor's perspective Ironic Python Agent doesn't come up on some problematic nodes, while others log the following error :

      May 19 11:30:06 host-10-163-188-41 ironic-python-agent[5996]: 2025-05-19 11:30:05.985 5996 ERROR root [-] Failed to detect efi system partition uuid: oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command.
      May 19 11:30:06 host-10-163-188-41 systemd-udevd[6268]: sda3: Failed to create/update device symlink '/dev/disk/by-partuuid/ab2d0100-3ffe-4719-b33f-81f8a78cdf3b', ignoring: No such file or directory
      May 19 11:30:06 host-10-163-188-41 ironic-python-agent[5996]: 2025-05-19 11:30:06.034 5996 ERROR root [-] Command failed: prepare_image, error: Error writing image to device: Writing image to device /dev/sda failed with exit code 32. stdout: . stderr: lsblk: /dev/sda1: not a block device
      

      The following errors logged by Ironic Conductor for nodes where Ironic Python Agent was unable to establish communications with Conductor :

      2025-05-19 15:58:25.665 7 ERROR ironic.conductor.task_manager [req-5a4affd1-90d8-44e3-8ce7-47c806a61edc - - - - -] Node 72565cb9-0198-48ab-a158-8cfba6167429 moved to provision state "deploy failed" from state "wait call-back"; target provision state is "active"
      2025-05-19 15:58:25.668 7 ERROR ironic.conductor.utils [req-5a4affd1-90d8-44e3-8ce7-47c806a61edc - - - - -] Timeout reached while waiting for callback for node 72565cb9-0198-48ab-a158-8cfba6167429
      

      From Ironic Conductor's perspective, a constant flood of complaints about agent token is logged

      Expected behavior
      Normal provisioning is expected

      Bug impact
      Scale-out is blocked

      Known workaround
      None

      Additional context
      Information about collected data will be provided privately

              jkreger@redhat.com Julia Kreger
              rhn-support-astupnik Alex Stupnikov
              rhos-dfg-hardprov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: