Red Hat Bugzilla – Bug 1518545
[RFE] otopi should log on failure list of network connections
Last modified: 2018-01-28 20:11:35 EST
Description of problem: We had several different cases lately of engine-setup or host-deploy failing to start services due to "Address already in use". It will be helpful if otopi logs e.g. the output of 'ss -anp' on failure. This was already merged in the master branch, as a new debug plugin, always active if 'otopi-debug-plugins' is installed. Opening current bug for consideration for 4.1 (otopi 1.6 branch).
Not enough. Current code does not catch errors outside of otopi's main transaction. See e.g.: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4205/artifact/exported-artifacts/basic-suit-master-el7/test_logs/basic-suite-master/post-002_bootstrap.py/lago-basic-suite-master-engine/_var_log/ovirt-engine/host-deploy/ovirt-host-deploy-20171129055013-lago-basic-suite-master-host-0-3c1c84f7.log
with installed rpm otopi-debug-plugins when engine-setup or host deploy fails, log contains: 2018-01-22 15:14:14 DEBUG otopi.plugins.otopi.debug.debug_failure.debug_failure debug_failure._notification:100 tcp connections: id uid local foreign state pid exe 0: 29 0.0.0.0:40398 0.0.0.0:0 LISTEN 19376 /usr/sbin/rpc.statd ... verified in otopi-1.6.3-1.el7ev.noarch, otopi-debug-plugins-1.6.3-1.el7ev.noarch with ovirt-engine-4.1.9-0.2.el7.noarch
This bugzilla is included in oVirt 4.1.9 release, published on Jan 24th 2018. Since the problem described in this bug report should be resolved in oVirt 4.1.9 release, published on Jan 24th 2018, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.