April 2020 - Infra - oVirt List Archives

[JIRA] (OVIRT-2909) CI is Not Triggered and Success Does Not result in +1
by Anton Marchukov (oVirt JIRA) 17 Apr '20

17 Apr '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2909?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2909: ---------------------------------------- [~accountid:5b7bd5022762c957ea676264] I think you are right. Closing. > CI is Not Triggered and Success Does Not result in +1 > ----------------------------------------------------- > > Key: OVIRT-2909 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2909 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: infra > > https://gerrit.ovirt.org/#/c/108365/ here CI was not triggered and after > "ci please build" and successful CI finish it did not get +1 set. > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100124)

1 0

[CQ]: fc69a24 (ovirt-cockpit-sso) failed "ovirt-master" system tests
by oVirt Jenkins 17 Apr '20

17 Apr '20

Change fc69a24 (ovirt-cockpit-sso) 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-cockpit-sso/commit/fc69a24e9d6ec4f2e9858d523… For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23199/

1 0

[JIRA] (OVIRT-2909) CI is Not Triggered and Success Does Not result in +1
by Marcin Sobczyk (oVirt JIRA) 17 Apr '20

17 Apr '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2909?page=com.atlassian.jira.… ] Marcin Sobczyk commented on OVIRT-2909: --------------------------------------- Is this really a bug? AFAIK “ci please build“ never altered CI marks in gerrit - it runs “build-artifacts” stage which should not run tests. “ci please test“ OTOH should alter the CI mark. > CI is Not Triggered and Success Does Not result in +1 > ----------------------------------------------------- > > Key: OVIRT-2909 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2909 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: infra > > https://gerrit.ovirt.org/#/c/108365/ here CI was not triggered and after > "ci please build" and successful CI finish it did not get +1 set. > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100124)

1 0

[CQ]: 108209, 4 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Apr '20

17 Apr '20

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

1 0

[CQ]: 108230, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Apr '20

17 Apr '20

A system test invoked by the "ovirt-master" change queue including change 108230,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 108081,5 (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 108081,5 (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/108230/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108081/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23183/

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc29-x86_64 #1592
by jenkins＠jenkins.phx.ovirt.org 17 Apr '20

17 Apr '20

See <https://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/1…> Changes: [Evgheni Dereveanchin] Define more CentOS 8 repo mirrors ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <https://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/w…> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 33b0b453a5688b9717c8ff0ba7b6fef04969d5f5 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 33b0b453a5688b9717c8ff0ba7b6fef04969d5f5 Commit message: "Define more CentOS 8 repo mirrors" > git rev-list --no-walk 7ff2d84e95416ee1b17480ab34f3fc11f26a6646 # timeout=10 [system-sync_mirrors-fedora-base-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins2298685885673237565.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + YUM_PATH=/yum/ + MIRRORS_BASE_PREFIX=/var/www/html/repos/yum/ + REPOQUERY_HTTP_BASE=http://mirrors.phx.ovirt.org/repos/yum/ + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + MAX_AGE=14 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-base-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs fedora-base-fc29 yum + local repo_name=fedora-base-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-base-fc29 /var/www/html/repos/yum/fedora-base-fc29/base + check_yum_sync_needed fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-base-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/fedora-base-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-base-fc29 ++ 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=fedora-base-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-base-fc29/base --norepopath --newest-only --urls --quiet Error setting up repositories: Cannot find a valid baseurl for repo: centos-extras-el8 + reposync_out= Build step 'Execute shell' marked build as failure

1 2

[CQ]: 108211, 4 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Apr '20

17 Apr '20

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

1 0

[CQ]: 108210, 4 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Apr '20

17 Apr '20

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

1 0

[CQ]: 108208, 2 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Apr '20

17 Apr '20

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

1 0

[oVirt Jenkins] cleanup-gated-dummy-master - Build #115 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 17 Apr '20

17 Apr '20

Build: https://jenkins.ovirt.org/job/cleanup-gated-dummy-master/115/ Build Name: #115 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 3