Broken proxy configuration on undercloud node affects Redfish-based Ironic calls

Solution Verified - Updated -

Issue

  • Undercloud Ironic operations against overcloud nodes via Redfish protocol are blocked because of broken proxy configuration.
  • Existing baremetal nodes are in maintenance state, their power state is None.
  • It is impossible to introspect or provision baremetal nodes because Ironic is unable to manage them via Redfish protocol because of broken proxy configuration.
  • How to update proxy configuration inside undercloud containers.

Environment

  • Red Hat OpenStack Platform 17

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