Loadbalancer IPs not added to no_proxy

Bug #2063424 reported by Guillaume Boutry
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Snap
Triaged
High
Unassigned

Bug Description

root@sunbeam:~# snap logs openstack-hypervisor
2024-04-24T09:54:37Z nova-compute[516904]: 2024-04-24 09:54:37.518 516904 WARNING keystoneauth.identity.generic.base [None req-7b5a8aab-d612-448e-9282-6e688f664c4c - - - - - -] Failed to discover available identity versions when contacting http://10.20.21.13/openstack-keystone/v3. Attempting to parse version from URL.: keystoneauth1.exceptions.http.ServiceUnavailable: Service Unavailable (HTTP 503)

That is the internal keystone IP, but I'm able to run other openstack commands against the public IP after I updated 'sunbeam proxy set ...', adding 10.20.21.0/24 to no-proxy. But how can I tell the hypervisor to update its no-proxy settings?

Tags: proxy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.