- Infra - oVirt List Archives

[ OST Failure Report ] [ oVirt Master ] [ 23-06-2018 ] [ 001_initialize_engine.initialize_engine ]
by Dafna Ron 23 Jan '18

23 Jan '18

Hi, We are failing test "001_initialize_engine.initialize_engine" in basic suite. Can you please check this issue? *Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/85809/ <https://gerrit.ovirt.org/#/c/85809/> - * *packaging: raise if network provider name is duplicatedLink to Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5047/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5047/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5047/art… <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5047/artifact/>(Relevant) error snippet from the log: <error>[ INFO ] Stage: Setup validation[ ERROR ] Failed to execute stage 'Setup validation': could not connect to server: Connection refused Is the server running on host "localhost" (::1) and accepting TCP/IP connections on port 5432? could not connect to server: Connection refused Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432? [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20180123025743-gngssk.log[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20180123025751-setup.conf'[ INFO ] Stage: Pre-termination[ INFO ] Stage: Termination[ ERROR ] Execution of setup failed('FATAL Internal error (main): could not connect to server: Connection refused\n\tIs the server running on host "localhost" (::1) and accepting\n\tTCP/IP connections on port 5432?\ncould not connect to server: Connection refused\n\tIs the server running on host "localhost" (127.0.0.1) and accepting\n\tTCP/IP connections on port 5432?\n',)2018-01-23 07:57:51,174::ssh.py::ssh::96::lago.ssh::DEBUG::Command 178de848 on lago-basic-suite-master-engine errors: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/__main__.py", line 88, in main installer.execute() File "/usr/lib/python2.7/site-packages/otopi/main.py", line 157, in execute self.context.runSequence() File "/usr/lib/python2.7/site-packages/otopi/context.py", line 765, in runSequence util.raiseExceptionInformation(infos[0]) File "/usr/lib/python2.7/site-packages/otopi/util.py", line 81, in raiseExceptionInformation exec('raise info[1], None, info[2]') 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/network/ovirtproviderovn.py", line 894, in _validate_provider_uniqueness existing_provider_id = self._check_provider_exists() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/network/ovirtproviderovn.py", line 138, in _check_provider_exists ownConnection=True, File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py", line 238, in execute database=database, File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py", line 172, in connect sslmode=sslmode, File "/usr/lib64/python2.7/site-packages/psycopg2/__init__.py", line 164, in connect conn = _connect(dsn, connection_factory=connection_factory, async=async)OperationalError: could not connect to server: Connection refused Is the server running on host "localhost" (::1) and accepting TCP/IP connections on port 5432?could not connect to server: Connection refused Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432?</error>*

1 0

[vdsm][tag][master] Vdsm tagged: v4.20.15
by Francesco Romani 23 Jan '18

23 Jan '18

Hi infra, Hi infra, we have a new Vdsm tag on branch master for oVirt 4.2: tag v4.20.15 Tagger: Francesco Romani <fromani(a)redhat.com> Date: Tue Jan 23 11:16:41 2018 +0100 Vdsm 4.20.15 for oVirt 4.2.1 RC 4 commit b5b771f2152225b2c262c5ed3148acd53ee5f17b +++ NOTE ABOUT BRANCHING: * We are merging again patches targeted for 4.2.1 on master * We don't yet have plans to branch out ovirt-4.2 from master. Following the usual Vdsm habit, we will branch out late, *after* Engine does. Bests, -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh

1 0

[oVirt Jenkins] standard-enqueue - Build #9158 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 Jan '18

23 Jan '18

------=_Part_257_1141798880.1516697727396 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/9158/ Build Name: #9158 Build Description: Gerrit: 86664 - ovirt-engine (3.6.13) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/86664 - title: build: ovirt-engine-3.6.13 - project: ovirt-engine - branch: ovirt-engine-3.6-els - author: Sandro Bonazzola <sbonazzo(a)redhat.com> ------=_Part_257_1141798880.1516697727396--

1 1

[CQ]: 85809,14 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 23 Jan '18

23 Jan '18

Change 85809,14 (ovirt-engine) 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://gerrit.ovirt.org/#/c/85809/14 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5047/

1 0

[CQ]: 86662, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jan '18

23 Jan '18

A system test invoked by the "ovirt-4.2" change queue including change 86662,1 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86648,1 (cockpit-ovirt) 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 86648,1 (cockpit-ovirt) 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/86662/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86648/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/325/

1 0

[CQ]: 86677, 1 (ovirt-log-collector) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jan '18

23 Jan '18

A system test invoked by the "ovirt-4.2" change queue including change 86677,1 (ovirt-log-collector) failed. However, this change seems not to be the root cause for this failure. Change 86671,1 (ovirt-log-collector) 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 86671,1 (ovirt-log-collector) 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/86677/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86671/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/324/

1 0

[CQ]: 86677, 1 (ovirt-log-collector) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jan '18

23 Jan '18

A system test invoked by the "ovirt-4.2" change queue including change 86677,1 (ovirt-log-collector) failed. However, this change seems not to be the root cause for this failure. Change 86671,1 (ovirt-log-collector) 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 86671,1 (ovirt-log-collector) 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/86677/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86671/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/322/

1 0

[CQ]: 86671,1 (ovirt-log-collector) failed "ovirt-4.2" system tests
by oVirt Jenkins 23 Jan '18

23 Jan '18

Change 86671,1 (ovirt-log-collector) is probably the reason behind recent system test failures in the "ovirt-4.2" 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://gerrit.ovirt.org/#/c/86671/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/321/

1 0

[CQ]: 86662, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jan '18

23 Jan '18

A system test invoked by the "ovirt-4.2" change queue including change 86662,1 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86648,1 (cockpit-ovirt) 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 86648,1 (cockpit-ovirt) 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/86662/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86648/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/319/

1 0

[CQ]: 86661, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jan '18

23 Jan '18

A system test invoked by the "ovirt-4.2" change queue including change 86661,1 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86648,1 (cockpit-ovirt) 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 86648,1 (cockpit-ovirt) 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/86661/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86648/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/317/

1 0