- Infra - oVirt List Archives

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 645 - Failure!
by jenkins＠jenkins.phx.ovirt.org 10 Jul '21

10 Jul '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/64… Build Number: 645 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #645 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.run_vms Error Message: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400. Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/agent/workspace/ovirt-system-tests_basic-suite-4.3_nightly/ovirt-system-tests/basic-suite-4.3/test-scenarios/004_basic_sanity.py", line 694, in run_vms vm0_service.start(use_cloud_init=True, vm=vm_params) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 32520, in start return self._internal_action(action, 'start', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 134, in _check_fault self._raise_error(response, body.fault) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400.

1 1

Build failed in Jenkins: system-sync_mirrors-centos-sclo-rh-release-x86_64 #1977
by jenkins＠jenkins.phx.ovirt.org 10 Jul '21

10 Jul '21

See <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-sclo-rh-release-x8…> Changes: ------------------------------------------ [...truncated 845.05 KB...] + local repo_comps + local sync_newest_only + repo_mp=/var/www/html/repos/yum/centos-sclo-rh-release/base ++ get_modulesmd_path centos-sclo-rh-release ++ local repo_name=centos-sclo-rh-release +++ sed -e 's/xmlns=".*"//g' /home/jenkins/mirrors_cache/centos-sclo-rh-release/repomd.xml +++ xmllint --xpath 'string(/repomd/data[@type="modules"]/location/@href)' - +++ grep -o '[[:alnum:]_.-]*$' ++ filename= ++ [[ -z '' ]] ++ false + '[' -z '' ']' + sync_newest_only=--newest-only ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' + echo 'Syncing yum repo centos-sclo-rh-release for arch: x86_64' Syncing yum repo centos-sclo-rh-release for arch: x86_64 + run_reposync centos-sclo-rh-release x86_64 jenkins/data/mirrors-reposync.conf --downloadcomps --gpgcheck --download-metadata --newest-only + local repo_name=centos-sclo-rh-release + local repo_arch=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + extra_args=("${@:4}") + local extra_args + reposync --config=jenkins/data/mirrors-reposync.conf --repoid=centos-sclo-rh-release --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-sclo-rh-release/base --norepopath --downloadcomps --gpgcheck --download-metadata --newest-only : rh-ruby30-scldevel-3.7-2.el7.x86_64.rpm | 3.5 kB 00:00 devtoolset-10-annobin-9.23-4.el7.x86_64: [Errno 256] No more mirrors to try. devtoolset-10-binutils-devel-2.35-5.el7.x86_64: [Errno 256] No more mirrors to try. Removing devtoolset-10-annobin-9.23-4.el7.x86_64.rpm due to failed signature check. Removing devtoolset-10-binutils-devel-2.35-5.el7.x86_64.rpm due to failed signature check. Build step 'Execute shell' marked build as failure

1 1

oVirt infra daily report - unstable production jobs - 1612
by jenkins＠jenkins.phx.ovirt.org 10 Jul '21

10 Jul '21

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

1 0

[JIRA] (OVIRT-3110) OST failure, bad comment
by Nir Soffer (oVirt JIRA) 10 Jul '21

10 Jul '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3110?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-3110: ----------------------------------- On Sat, Jul 10, 2021 at 12:59 AM Nir Soffer <nsoffer(a)redhat.com> wrote: > > OST failed, and posted unprocessed comment: > > OST Verified -1 > Patch Set 1: Verified-1 > https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313 : > OST https://redir.apps.ovirt.org/dj/job/ds-ost-baremetal_manual/$OST_NUMBER > failed with: $OST_MESSAGE > > https://gerrit.ovirt.org/c/vdsm/+/115642#message-b2993761_adbc1b6a > > Looking at: > https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313 > > It looks like environment issue: > > ERROR: Build step failed with exception > > java.lang.NullPointerException: no workspace from node > hudson.slaves.DumbSlave[hpe-bl280g6-12...] which is computer > hudson.slaves.SlaveComputer@2e2cb321 and has channel null > > So we have 2 issues: > 1. If build fails, error is not handled properly producing bad comment > 2. the actual build failure I started another build manually (8543) and it started normally, so this was probably a temporary issue. > > The first issue should be handled by posting a better comment: > > OST build error: > https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313 > > And OST should not mark the patch as verified -1, since it did not run any test. > > Marking a patch as -1 means some tests have failed, and the author > needs to check > why. A build error means OST or CI maintainers need to check why the > error happened. > OST failure, bad comment > ------------------------ > > Key: OVIRT-3110 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3110 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > OST failed, and posted unprocessed comment: > OST Verified -1 > Patch Set 1: Verified-1 > https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313 : > OST https://redir.apps.ovirt.org/dj/job/ds-ost-baremetal_manual/$OST_NUMBER > failed with: $OST_MESSAGE > https://gerrit.ovirt.org/c/vdsm/+/115642#message-b2993761_adbc1b6a > Looking at: > https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313 > It looks like environment issue: > ERROR: Build step failed with exception > java.lang.NullPointerException: no workspace from node > hudson.slaves.DumbSlave[hpe-bl280g6-12...] which is computer > hudson.slaves.SlaveComputer@2e2cb321 and has channel null > So we have 2 issues: > 1. If build fails, error is not handled properly producing bad comment > 2. the actual build failure > The first issue should be handled by posting a better comment: > OST build error: > https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313 > And OST should not mark the patch as verified -1, since it did not run any test. > Marking a patch as -1 means some tests have failed, and the author > needs to check > why. A build error means OST or CI maintainers need to check why the > error happened. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100168)

1 0

[JIRA] (OVIRT-3110) OST failure, bad comment
by Nir Soffer (oVirt JIRA) 10 Jul '21

10 Jul '21

Nir Soffer created OVIRT-3110: --------------------------------- Summary: OST failure, bad comment Key: OVIRT-3110 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3110 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra OST failed, and posted unprocessed comment: OST Verified -1 Patch Set 1: Verified-1 https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313 : OST https://redir.apps.ovirt.org/dj/job/ds-ost-baremetal_manual/$OST_NUMBER failed with: $OST_MESSAGE https://gerrit.ovirt.org/c/vdsm/+/115642#message-b2993761_adbc1b6a Looking at: https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313 It looks like environment issue: ERROR: Build step failed with exception java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave[hpe-bl280g6-12...] which is computer hudson.slaves.SlaveComputer@2e2cb321 and has channel null So we have 2 issues: 1. If build fails, error is not handled properly producing bad comment 2. the actual build failure The first issue should be handled by posting a better comment: OST build error: https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313 And OST should not mark the patch as verified -1, since it did not run any test. Marking a patch as -1 means some tests have failed, and the author needs to check why. A build error means OST or CI maintainers need to check why the error happened. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100168)

1 0

[CQ]: 115395,2 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 09 Jul '21

09 Jul '21

Change 115395,2 (jenkins) is probably the reason behind recent system test failures in the "dummy-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/jenkins/+/#/c/115395/2 For failed test results see: https://jenkins.ovirt.org/job/dummy-master_change-queue-tester/643/

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 1303 - Failure!
by jenkins＠jenkins.phx.ovirt.org 09 Jul '21

09 Jul '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 1303 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1303 [Eitan Raviv] network: ansible facts per address family ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.test_100_basic_ui_sanity.test_secure_connection_should_fail_without_root_ca[firefox] Error Message: failed on setup with "ost_utils.shell.ShellError: Command failed with rc=125. Stdout: Stderr: Resolving "selenium/video" using unqualified-search registries (/etc/containers/registries.conf) Trying to pull registry.access.redhat.com/selenium/video:ffmpeg-4.3.1-20210618... name unknown: Repo not found Trying to pull registry.redhat.io/selenium/video:ffmpeg-4.3.1-20210618... unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication Trying to pull docker.io/selenium/video:ffmpeg-4.3.1-20210618... unable to retrieve auth token: invalid username/password: unauthorized: incorrect username or password Error: 1 error occurred: * 3 errors occurred while pulling: * Error initializing source docker://registry.access.redhat.com/selenium/video:ffmpeg-4.3.1-20210618: Error reading manifest ffmpeg-4.3.1-20210618 in registry.access.redhat.com/selenium/video: name unknown: Repo not found * Error initializing source docker://registry.redhat.io/selenium/video:ffmpeg-4.3.1-20210618: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication * Error initializing source docker://selenium/video:ffmpeg-4.3.1-20210618: unable to retrieve auth token: invalid username/password: unauthorized: incorrect username or password" Stack Trace: engine_fqdn = 'engine', engine_ip = '192.168.200.2' selenium_artifacts_dir = '/home/jenkins/workspace/ovirt-system-tests_basic-suite-master_nightly/ovirt-system-tests/exported-artifacts/ui_tests_artifacts/' @pytest.fixture(scope="session") def hub_url(engine_fqdn, engine_ip, selenium_artifacts_dir): env_url = _env_hub_url() if env_url is not None: yield env_url else: backend = _grid_backend() if backend == "podman" or backend == "podman-remote": videos_artifacts_dir = selenium_artifacts_dir with podman.grid(engine_fqdn, engine_ip, podman_cmd=backend, > videos_artifacts_dir=videos_artifacts_dir ) as hub_url: ost_utils/ost_utils/pytest/fixtures/selenium/__init__.py:75: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib64/python3.6/contextlib.py:81: in __enter__ return next(self.gen) ost_utils/ost_utils/selenium/grid/podman.py:186: in grid hub_port, podman_cmd, videos_artifacts_dir) as url: /usr/lib64/python3.6/contextlib.py:81: in __enter__ return next(self.gen) ost_utils/ost_utils/selenium/grid/podman.py:164: in _grid videos_artifacts_dir)as videos_names: /usr/lib64/python3.6/contextlib.py:81: in __enter__ return next(self.gen) ost_utils/ost_utils/selenium/grid/podman.py:136: in _video_recorders FFMPEG_CONTAINER_IMAGE, _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ args = ['podman-remote', 'run', '-d', '-v', '/home/jenkins/workspace/ovirt-system-tests_basic-suite-master_nightly/ovirt-system-tests/exported-artifacts/ui_tests_artifacts/:/videos:Z', '-e', ...] bytes_output = False, kwargs = {} process = <subprocess.Popen object at 0x7f9588d1e828>, out = '' err = 'Resolving "selenium/video" using unqualified-search registries (/etc/containers/registries.conf)\nTrying to pull regi...210618: unable to retrieve auth token: invalid username/password: unauthorized: incorrect username or password\n\n\n\n' def shell(args, bytes_output=False, **kwargs): process = subprocess.Popen(args, stdout=subprocess.PIPE, stderr=subprocess.PIPE, **kwargs) out, err = process.communicate() if not bytes_output: out = out.decode("utf-8") err = err.decode("utf-8") if process.returncode: > raise ShellError(process.returncode, out, err) E ost_utils.shell.ShellError: Command failed with rc=125. Stdout: E E Stderr: E Resolving "selenium/video" using unqualified-search registries (/etc/containers/registries.conf) E Trying to pull registry.access.redhat.com/selenium/video:ffmpeg-4.3.1-20210618... E name unknown: Repo not found E Trying to pull registry.redhat.io/selenium/video:ffmpeg-4.3.1-20210618... E unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication E Trying to pull docker.io/selenium/video:ffmpeg-4.3.1-20210618... E unable to retrieve auth token: invalid username/password: unauthorized: incorrect username or password E Error: 1 error occurred: E * 3 errors occurred while pulling: E * Error initializing source docker://registry.access.redhat.com/selenium/video:ffmpeg-4.3.1-20210618: Error reading manifest ffmpeg-4.3.1-20210618 in registry.access.redhat.com/selenium/video: name unknown: Repo not found E * Error initializing source docker://registry.redhat.io/selenium/video:ffmpeg-4.3.1-20210618: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication E * Error initializing source docker://selenium/video:ffmpeg-4.3.1-20210618: unable to retrieve auth token: invalid username/password: unauthorized: incorrect username or password ost_utils/ost_utils/shell.py:49: ShellError

1 1

oVirt infra daily report - unstable production jobs - 1611
by jenkins＠jenkins.phx.ovirt.org 09 Jul '21

09 Jul '21

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

1 0

[JIRA] (OVIRT-2906) ovirt-engine_master_coverity-analysis broken - git proto missing
by Evgheni Dereveanchin (oVirt JIRA) 08 Jul '21

08 Jul '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2906?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2906: ---------------------------------------- Resolution: Fixed Status: Done (was: To Do) > ovirt-engine_master_coverity-analysis broken - git proto missing > ----------------------------------------------------------------- > > Key: OVIRT-2906 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2906 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > I've noticed the engine coverity job failing due to the protocol being missing. > https://jenkins.ovirt.org/job/ovirt-engine_master_coverity-analysis/379/con…: > hudson.plugins.git.GitException: Command "git fetch --tags --progress ://gerrit.ovirt.org/ovirt-engine.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: > stdout: > stderr: fatal: I don't handle protocol '' > Likely related to OVIRT-2738, need to see which SCM definition is used and update that to https:// -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100168)

1 0

package in automation/*.packages not installed
by Yedidyah Bar David 08 Jul '21

08 Jul '21

On Wed, Jul 7, 2021 at 10:54 PM Code Review <gerrit(a)ovirt.org> wrote: > > From Jenkins CI <jenkins(a)ovirt.org>: > > Jenkins CI has posted comments on this change. ( https://gerrit.ovirt.org/c/ovirt-system-tests/+/115392 ) > > Change subject: test, do not merge: HE: Use node image > ...................................................................... > > > Patch Set 3: Continuous-Integration-1 > > Build Failed > > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/17737/ : FAILURE Hi all, Above failed with: [36m # Create disks for VM lago-he-basic-suite-master-host-0: [31mERROR [0m (in 0:00:00) [0m [36m # Missing current link, setting it to default [0m [36m@ Initialize and populate prefix: [31mERROR [0m (in 0:03:23) [0m [31mError occured, aborting ... RuntimeError: Failed to get info for /var/lib/lago/ost-images-2h8yHA/ b"qemu-img: Could not open '/var/lib/lago/ost-images-2h8yHA/': A regular file was expected by the 'file' driver, but something else was given\n" This job was for [1]. [1] also includes a patch to he-basic_suite_master.packages.el8 to install ost-images-node-base. It also removes ost-images-el8stream-he-installed. This should still work, because the latest published node image is a result of manually running the job in jenkins with [2]). Anyway, the console log [3] shows that ost-images-node-base was not installed. Any idea why, or what I should do? Thanks and best regards, [1] https://gerrit.ovirt.org/c/ovirt-system-tests/+/115392 [2] https://gerrit.ovirt.org/c/ost-images/+/115453 > > > -- > To view, visit https://gerrit.ovirt.org/c/ovirt-system-tests/+/115392 > To unsubscribe, or for help writing mail filters, visit https://gerrit.ovirt.org/settings > > Gerrit-Project: ovirt-system-tests > Gerrit-Branch: master > Gerrit-Change-Id: I0fd1313100997edde22fc6b5869ab98abb217f42 > Gerrit-Change-Number: 115392 > Gerrit-PatchSet: 3 > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Anton Marchukov <amarchuk(a)redhat.com> > Gerrit-Reviewer: Dafna Ron <dron(a)redhat.com> > Gerrit-Reviewer: Dusan Fodor <dfodor(a)redhat.com> > Gerrit-Reviewer: Gal Ben Haim <galbh2(a)gmail.com> > Gerrit-Reviewer: Galit Rosenthal <grosenth(a)redhat.com> > Gerrit-Reviewer: Jenkins CI <jenkins(a)ovirt.org> > Gerrit-Reviewer: Name of user not set #1001916 > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Comment-Date: Wed, 07 Jul 2021 19:54:31 +0000 > Gerrit-HasComments: No > Gerrit-Has-Labels: Yes > Gerrit-MessageType: comment > -- Didi

1 1