- Infra - oVirt List Archives

[CQ]: 97765, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97765,6 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 97775,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97775,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/97765/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97775/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12937/

1 0

Best Practice to Deploy HostedEngine oVirt Environment
by Mohd Hanief Harun 17 Feb '19

17 Feb '19

Hi all, Im new in rhv and oVirt, hope there some space for the noob question :) Let say I have 2 hypervisors and 1 storage server. Where is the best practice to install self-hosted engine? In hypervisors or storage? I have experienced installing self-hosted engine in 2 storages. If something happened to the storage 1, ovirt-engine (ovirt-manager) will automatically migrate to storage 2. But this time is difference. We only have 1 storage. my concern is, if something happened to the storage, I cannot access my ovirt-manager. I'm thinking to deploy self-hosted engine in hypervisors since we have 2 hypervisors. any advise? what is the best practice? If you have any tutorial installing hosted engine in 2 hypervisors would be very appreciate. thanks.

2 1

[CQ]: 66932, 31 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Feb '19

17 Feb '19

A system test invoked by the "ovirt-master" change queue including change 66932,31 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 97775,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97775,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/66932/31 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97775/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12935/

1 0

[CQ]: 7d67266 (ovirt-web-ui) failed "ovirt-master" system tests
by oVirt Jenkins 17 Feb '19

17 Feb '19

Change 7d67266 (ovirt-web-ui) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-web-ui/commit/7d6726676871274417e78139507a96… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12934/

1 0

[CQ]: 96836, 27 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Feb '19

17 Feb '19

A system test invoked by the "ovirt-master" change queue including change 96836,27 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 97775,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97775,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/96836/27 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97775/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12932/

1 0

oVirt infra daily report - unstable production jobs - 739
by jenkins＠jenkins.phx.ovirt.org 17 Feb '19

17 Feb '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/739//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 96835, 27 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Feb '19

17 Feb '19

A system test invoked by the "ovirt-master" change queue including change 96835,27 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 97775,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97775,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/96835/27 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97775/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12930/

1 0

[CQ]: 96829, 28 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Feb '19

17 Feb '19

A system test invoked by the "ovirt-master" change queue including change 96829,28 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 97775,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97775,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/96829/28 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97775/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12927/

1 0

[CQ]: 96554, 34 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Feb '19

17 Feb '19

A system test invoked by the "ovirt-master" change queue including change 96554,34 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97719,3 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97719,3 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/96554/34 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97719/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12925/

1 0

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 17-02-2019 ] [ 001_initialize_engine.test_initialize_engine ]
by Dafna Ron 17 Feb '19

17 Feb '19

Hi, we are failing upgrade from release suite on ovirt-engine master. CQ points below patch as root cause: https://gerrit.ovirt.org/#/c/97719/ - webadmin: don't allow trimming whitespace for the kernel cmdline Unfortunately the process logs are not collected and I have no way of seeing why the processes failed. I can try to debug this further in the morning ERROR: setup log: 2019-02-17 10:17:24,507-0500 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 'rh-postgresql95-postgresql.service') stderr: Job for rh-postgresql95-postgresql.service failed because the control process exited with error code. See "systemctl status rh-postgresql95-postgresql.service" and "journalctl -xe" for details. 2019-02-17 10:17:24,508-0500 DEBUG otopi.transaction transaction.abort:119 aborting 'File transaction for '/var/opt/rh/rh-postgresql95/lib/pgsql/data/pg_hba.conf'' 2019-02-17 10:17:24,509-0500 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/provisioning/postgres.py", line 201, in _misc self._provisioning.provision() File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/postgres.py", line 498, in provision self.restartPG() File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/postgres.py", line 399, in restartPG state=state, File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 141, in state service=name, RuntimeError: Failed to start service 'rh-postgresql95-postgresql' 2019-02-17 10:17:24,511-0500 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Misc configuration': Failed to start service 'rh-postgresql95-postgresql' 2019-02-17 10:17:24,556-0500 DEBUG otopi.plugins.otopi.debug.debug_failure.debug_failure debug_failure._notification:100 tcp connections: id uid local foreign state pid exe 0: 0 0.0.0.0:111 0.0.0.0:0 LISTEN 4191 /usr/sbin/rpcbind 1: 29 0.0.0.0:662 0.0.0.0:0 LISTEN 4225 /usr/sbin/rpc.statd 2: 0 0.0.0.0:22 0.0.0.0:0 LISTEN 3361 /usr/sbin/sshd 3: 0 0.0.0.0:892 0.0.0.0:0 LISTEN 4266 /usr/sbin/rpc.mountd 4: 0 0.0.0.0:2049 0.0.0.0:0 LISTEN UnknownPID UnknownEXE 5: 0 0.0.0.0:32803 0.0.0.0:0 LISTEN UnknownPID UnknownEXE 6: 0 192.168.201.2:22 192.168.201.1:54800 ESTABLISHED 8189 /usr/sbin/sshd 2019-02-17 10:17:24,557-0500 DEBUG otopi.transaction transaction.abort:119 aborting 'Yum Transaction' 2019-02-17 10:17:24,558-0500 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:80 Yum Performing yum transaction rollback Loaded plugins: fastestmirror, versionlock

2 4