Director failed to deploy a overcloud node with "No valid host was found"

Solution Verified - Updated -

Issue

  • openstack overcloud deploy fails with "No valid host was found", and director does not deploy the required baremetal instance.
  • We see the following log from nova-scheduler in our director node, which shows that nova failed to pick up a baremetal node to deploy the instance becaise pf DiskFilter
INFO nova.filters ... Filtering removed all hosts for the request with instance ID '49df134e-7203-4634-9a35-d7a03dd78876'. Filter results: ['RetryFilter: (start: 1, end: 1)', 'TripleOCapabilitiesFilter: (start: 1, end: 1)', 'ComputeCapabilitiesFilter: (start: 1, end: 1)', 'AvailabilityZoneFilter: (start: 1, end: 1)', 'RamFilter: (start: 1, end: 1)', 'DiskFilter: (start: 1, end: 0)']

Environment

  • Red Hat OpneStack Platform 13

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