Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1763794

Summary: [EL8] mom traceback while initializing
Product: [oVirt] mom Reporter: Sandro Bonazzola <sbonazzo>
Component: GeneralAssignee: Andrej Krejcir <akrejcir>
Status: CLOSED CURRENTRELEASE QA Contact: Polina <pagranat>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.5.16CC: ahadas, bugs, rbarry
Target Milestone: ovirt-4.4.1Flags: rbarry: ovirt-4.4?
Target Release: 0.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mom-0.6.0 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-08 08:27:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1722884    

Description Sandro Bonazzola 2019-10-21 15:53:59 UTC
2019-10-21 15:41:24,844 - mom - INFO - MOM starting
2019-10-21 15:41:24,856 - mom.HostMonitor - INFO - Host Monitor starting
2019-10-21 15:41:24,857 - mom - INFO - hypervisor interface vdsmjsonrpcclient
2019-10-21 15:41:24,878 - mom.HostMonitor - INFO - HostMonitor is ready
2019-10-21 15:41:24,907 - mom - ERROR - Failed to initialize MOM threads
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/client.py", line 154, in connect
    outgoing_heartbeat=outgoing_heartbeat, nr_retries=nr_retries)
  File "/usr/lib/python3.6/site-packages/yajsonrpc/stompclient.py", line 427, in SimpleClient
    nr_retries, reconnect_interval)
  File "/usr/lib/python3.6/site-packages/yajsonrpc/stompclient.py", line 449, in StandAloneRpcClient
    client = StompClient(utils.create_connected_socket(host, port, sslctx),
  File "/usr/lib/python3.6/site-packages/vdsm/utils.py", line 379, in create_connected_socket
    sock.connect((host, port))
  File "/usr/lib64/python3.6/ssl.py", line 1065, in connect
    self._real_connect(addr, False)
  File "/usr/lib64/python3.6/ssl.py", line 1052, in _real_connect
    socket.connect(self, addr)
ConnectionRefusedError: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/mom/__init__.py", line 28, in run
    hypervisor_iface = self.get_hypervisor_interface()
  File "/usr/lib/python3.6/site-packages/mom/__init__.py", line 226, in get_hypervisor_interface
    return module.instance(self.config)
  File "/usr/lib/python3.6/site-packages/mom/HypervisorInterfaces/vdsmjsonrpcclientInterface.py", line 104, in instance
    return JsonRpcVdsmClientInterface()
  File "/usr/lib/python3.6/site-packages/mom/HypervisorInterfaces/vdsmjsonrpcclientInterface.py", line 39, in __init__
    self._vdsm_api = client.connect(host="localhost", use_tls=use_tls)
  File "/usr/lib/python3.6/site-packages/vdsm/client.py", line 157, in connect
    raise ConnectionError(host, port, use_tls, timeout, e)
vdsm.client.ConnectionError: Connection to localhost:54321 with use_tls=True, timeout=60 failed: [Errno 111] Connection refused
2019-10-21 15:41:30,131 - mom - INFO - MOM starting


It's probably just failing to connect while vdsm is starting but still, it should behave properly instead of issuing a traceback to logs.

Comment 1 Polina 2020-01-12 14:28:44 UTC
verified on http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-14

now while reconnect to vdsm there is an error:
2020-01-12 09:24:58,740 - mom - ERROR - Cannot connect to VDSM. This can happen when VDSM is starting. Error: Connection to localhost:54321 with use_tls=True, timeout=60 failed: [Errno 111] Connection refused
2020-01-12 09:25:03,986 - mom - INFO - MOM starting
2020-01-12 09:25:04,018 - mom.HostMonitor - INFO - Host Monitor starting
2020-01-12 09:25:04,018 - mom - INFO - hypervisor interface vdsmjsonrpcclient
2020-01-12 09:25:04,038 - mom.HostMonitor - INFO - HostMonitor is ready

Comment 2 Sandro Bonazzola 2020-07-08 08:27:44 UTC
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.