agent.service doesn't start and ironic-agent shows error messages when booting with Discovery ISO

Solution Verified - Updated -

Issue

  • It succeeds to add baremetal hosts and build a cluster by creating BareMetalHost resources.
  • When adding new node via Discovery ISO to a cluster that was created using BareMetalHost objects, the agent.service doesn't start automatically on the to-be-added node. When checking checking journalctl logs, ironic-agent repeatedly shows the following error warning message.

    Jan 01 00:00:00 localhost.localdomain podman[12345]: 2024-01-01 00:00:00.000 1 WARNING ironic_python_agent.ironic_api_client [-] Failed looking up node with addresses 'aa:aa:aa:aa:aa:aa,bb:bb:bb:bb:bb:bb,cc:cc:cc:cc:cc:cc' at https://10.0.0.1:6385. Check if inspection has completed? Error 404: Resource could not be found.
    
  • Agents resource is not created automatically on ACM

    $ oc get agents
    (empty)
    

Environment

  • Red Hat Advanced Cluster Management for Kubernetes 2.x
  • Clusters deployed using BareMetalHost resources

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content