Loadbalancer IPs not added to no_proxy

Bug #2063424 reported by Guillaume Boutry

This bug report will be marked for expiration in 50 days if no further activity occurs. (find out why)

8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Snap
Incomplete
Undecided
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: added: open-2195
Revision history for this message
Hemanth Nakkina (hemanth-n) wrote :
Download full text (9.5 KiB)

I tried to reproduce the above scenario and in my case nova-compute gets restarted showing the logs mentioned in the bug description.

After running command 'sunbeam proxy set ...', the proxies get updated on all the machines (/etc/environment file to be specific) and due to the restart of nova-compute, the service picks the proxies and started properly.

nova-compute logs for reference:
2024-07-05T13:34:29Z nova-compute[520756]: 2024-07-05 13:34:29.555 520756 INFO os_vif [-] Loaded VIF plugins: linux_bridge, noop, ovs
2024-07-05T13:34:30Z nova-compute[520756]: 2024-07-05 13:34:30.101 520756 WARNING keystoneauth.identity.generic.base [None req-4654da67-7b41-4c0b-901c-54d406814d97 - - - - - -] Failed to discover available identity versions when contacting http://10.20.21.12/openstack-keystone/v3. Attempting to parse version from URL.: keystoneauth1.exceptions.http.Forbidden: Forbidden (HTTP 403)
2024-07-05T13:34:30Z nova-compute[520756]: - (error decoding original message: message key "MESSAGE" truncated)
2024-07-05T13:34:31Z systemd[1]: snap.openstack-hypervisor.nova-compute.service: Main process exited, code=exited, status=1/FAILURE
2024-07-05T13:34:31Z systemd[1]: snap.openstack-hypervisor.nova-compute.service: Failed with result 'exit-code'.
2024-07-05T13:34:31Z systemd[1]: snap.openstack-hypervisor.nova-compute.service: Consumed 6.192s CPU time.
2024-07-05T13:34:31Z systemd[1]: snap.openstack-hypervisor.nova-compute.service: Scheduled restart job, restart counter is at 58.
2024-07-05T13:34:31Z systemd[1]: Stopped Service for snap application openstack-hypervisor.nova-compute.
2024-07-05T13:34:31Z systemd[1]: snap.openstack-hypervisor.nova-compute.service: Consumed 6.192s CPU time.
2024-07-05T13:34:31Z systemd[1]: Started Service for snap application openstack-hypervisor.nova-compute.
2024-07-05T13:34:37Z nova-compute[521181]: 2024-07-05 13:34:37.538 521181 WARNING pyroute2.netlink.rtnl.tcmsg.common [-] tcmsg: [Errno 2] No such file or directory: '/proc/net/psched': FileNotFoundError: [Errno 2] No such file or directory: '/proc/net/psched'
2024-07-05T13:34:37Z nova-compute[521181]: 2024-07-05 13:34:37.539 521181 WARNING pyroute2.netlink.rtnl.tcmsg.common [-] the tc subsystem functionality is limited: FileNotFoundError: [Errno 2] No such file or directory: '/proc/net/psched'
2024-07-05T13:34:37Z nova-compute[521181]: 2024-07-05 13:34:37.715 521181 INFO os_vif [-] Loaded VIF plugins: linux_bridge, noop, ovs
2024-07-05T13:34:38Z nova-compute[521181]: 2024-07-05 13:34:38.224 521181 WARNING keystoneauth.identity.generic.base [None req-71c839fc-06f6-4c15-af5d-208ec5b16a5d - - - - - -] Failed to discover available identity versions when contacting http://10.20.21.12/openstack-keystone/v3. Attempting to parse version from URL.: keystoneauth1.exceptions.http.Forbidden: Forbidden (HTTP 403)
2024-07-05T13:34:38Z nova-compute[521181]: - (error decoding original message: message key "MESSAGE" truncated)
2024-07-05T13:34:39Z systemd[1]: snap.openstack-hypervisor.nova-compute.service: Main process exited, code=exited, status=1/FAILURE
2024-07-05T13:34:39Z systemd[1]: snap.openstack-hypervisor.nova-compute.service: Failed with result 'exit-code'.
2024-07-...

Read more...

Revision history for this message
Hemanth Nakkina (hemanth-n) wrote :

Marked as incomplete as not able to reproduce with snap openstack 2024.1/edge rev 554

Changed in snap-openstack:
status: Triaged → Incomplete
importance: High → Undecided
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.