Loadbalancer IPs not added to no_proxy
Bug #2063424 reported by
Guillaume Boutry
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Snap |
Triaged
|
High
|
Unassigned |
Bug Description
root@sunbeam:~# snap logs openstack-
2024-04-
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?
To post a comment you must log in.