Bug 1919200

Description of problem:

A customer has reported an issue with "openstack baremetal node provide <id>".
The deployment has clean_nodes enabled thus ironic first tries to clean the baremetal node,
however the cleaning process fails and the baremetal node becomes clean failed status.

While debugging the issue, we found that http request is sent from ironic-conductor
to overcloud nodes during node cleaning process and the request was directed to http proxy.
This makes ironic get the wrong response from http proxy which results in json decode error
in Ironic.

In the deployment the http proxy settings are applied in /etc/environments according
to our current guide.
 https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/director_installation_and_usage/installing-the-undercloud#considerations-when-running-the-undercloud-with-a-proxy
These setting were baked into Env parameter of podman containers, thus all processs
inside containers refer that environment variables.

We would be able to avoid the problem by adding these ips to no_proxy, but it is not very feasible option
in large deployment since we need to put all ips in dhcp range of provisioning networks.

IMO http proxy settings should be filtered for ironic-conductor container (and some other containers
if needed) which sends http requests not only to endpoint url but also to other ips.

# AFAIK we don't need http proxy except for mistral containers which would execute container image prepare
# thus we might be able to filter out http_proxy and the other options for most of containers.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Set http proxy in /etc/environment
2. Install undercloud with clean_nodes=True
3. Import baremetal nodes
4. Run "openstack overcloud node introspect --all-manageable"
5. Run "openstack baremetal node provide <id>"

Actual results:
The baremetal node becomes clean failed status

Expected results:
The baremetal node becomes available status

Additional info: