December 2017 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1790) User does not identify a registered user or group

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1790?page=com.atlassian.jir... ] Daniel Belenky reassigned OVIRT-1790: ------------------------------------- Assignee: Daniel Belenky (was: infra) > User does not identify a registered user or group > ------------------------------------------------- > > Key: OVIRT-1790 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1790 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Arik Hadas > Assignee: Daniel Belenky > > Hi, > Since trying by mistake to login to gerrit with my red hat's account, I > cannot be added as a reviewer to patches on gerrit.ovirt.org, the following > message is displayed: > Arik Hadas <ahadas(a)redhat.com> does not identify a registered user or group > Could you please fix that? > Thanks! -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

7 years

1
0
0 / 0

[CQ]: 85048,1 (ovirt-imageio) failed "ovirt-master" system tests

by oVirt Jenkins

Change 85048,1 (ovirt-imageio) 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/85048/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4266/

7 years

1
0
0 / 0

Build failed in Jenkins: system-sync_mirrors-epel-el7-x86_64 #945

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el7-x86_64/945/disp...> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el7-x86_64/ws/> > 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 http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 62343eba27398b928493782b606398396d899336 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 62343eba27398b928493782b606398396d899336 Commit message: "Exclude docker from fedora-updates in fc27 mock" > git rev-list 62343eba27398b928493782b606398396d899336 # timeout=10 [system-sync_mirrors-epel-el7-x86_64] $ /bin/bash -xe /tmp/jenkins4367780086483793549.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Resyncing repo: epel-el7 Syncing yum repo epel-el7 for arch: x86_64 epel-el7/group 22% [=== ] 0.0 B/s | 307 kB --:-- ETA epel-el7/group | 1.3 MB 00:00 lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt-devel-1. 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-devel-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-devel-1.25.0-1.el7 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-devel-1.25.0-1.el7. FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1 FAILED (1/5): lightdm-gobject-dev 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt5-1.25.0-1.el7.x86_6 FAILED (1/5): lightdm-qt5-1.25.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-qt-1.25.0-1.el7.x86_64 FAILED (1/5): lightdm-qt-1.25.0-1 0% [ ] 0.0 B/s | 0 B --:-- ETA lightdm-gobject-devel-1.25.0-1.el7.x86_64: [Errno 256] No more mirrors to try. lightdm-gobject-1.25.0-1.el7.x86_64: Insufficient space in download directory /var/www/html/repos/yum/epel-el7/base/Packages/l * free 56 k * needed 67 k lightdm-qt5-1.25.0-1.el7.x86_64: [Errno 256] No more mirrors to try. lightdm-qt-devel-1.25.0-1.el7.x86_64: [Errno 256] No more mirrors to try. lightdm-qt5-devel-1.25.0-1.el7.x86_64: [Errno 256] No more mirrors to try. lightdm-1.25.0-1.el7.x86_64: Insufficient space in download directory /var/www/html/repos/yum/epel-el7/base/Packages/l * free 56 k * needed 216 k lightdm-qt-1.25.0-1.el7.x86_64: [Errno 256] No more mirrors to try. Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 326, in main result, error = my.sigCheckPkg(pkg) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 2759, in sigCheckPkg ts, po.localPkg(), payload=self.conf.payload_gpgcheck, File "/usr/lib/python2.7/site-packages/rpmUtils/miscutils.py", line 76, in checkSig fdno = os.open(package, os.O_RDONLY) OSError: [Errno 2] No such file or directory: '/var/www/html/repos/yum/epel-el7/base/Packages/l/lightdm-1.25.0-1.el7.x86_64.rpm' Build step 'Execute shell' marked build as failure

7 years

1
1
0 / 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium

by Greg Sheremeta (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jir... ] Greg Sheremeta commented on OVIRT-1788: --------------------------------------- Ok, thanks. Why is a container better than simply doing a std-ci project similar to nodejs-dependencies? > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

7 years

1
0
0 / 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-1788: ------------------------------------- Ok, I get the issue now - I think long term it would be easier to maintain our own container images with specific browser versions then our own RPM packages. Its just a little challenge to get the same caching behaviour we have for RPMs for containers. I just discussed the details about how to go about thing this with [~gbenhaim(a)redhat.com] and [~dbelenky(a)redhat.com], some small changes will be needed in OST and our CI cleanup code to enable this, but its certainly doable. Guys, please fill in the details of what we've discussed here. > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

7 years

1
0
0 / 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium

by Greg Sheremeta (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jir... ] Greg Sheremeta commented on OVIRT-1788: --------------------------------------- > a new std-ci project called 'ovirt-ui-test-dependencies' or something similar and there you can build a new RPM in build-artifacts which will get into OST/CQ flow as any other project. works for me > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

7 years

1
0
0 / 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium

by Greg Sheremeta (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jir... ] Greg Sheremeta commented on OVIRT-1788: --------------------------------------- The drivers aren't packaged. https://github.com/mozilla/geckodriver/releases > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

7 years

1
0
0 / 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-1788: ------------------------------------- I also think that using containers or chroots to consume the different browser versions would work better then trying to maintain our own packaging. > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

7 years

1
0
0 / 0

[JIRA] (OVIRT-1790) User does not identify a registered user or group

by Arik Hadas (oVirt JIRA)

Arik Hadas created OVIRT-1790: --------------------------------- Summary: User does not identify a registered user or group Key: OVIRT-1790 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1790 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Arik Hadas Assignee: infra Hi, Since trying by mistake to login to gerrit with my red hat's account, I cannot be added as a reviewer to patches on gerrit.ovirt.org, the following message is displayed: Arik Hadas <ahadas(a)redhat.com> does not identify a registered user or group Could you please fix that? Thanks! -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

7 years

1
0
0 / 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc26-x86_64 #424

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc26-x86_...> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc26-x86_...> > 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 http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 62343eba27398b928493782b606398396d899336 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 62343eba27398b928493782b606398396d899336 Commit message: "Exclude docker from fedora-updates in fc27 mock" > git rev-list 62343eba27398b928493782b606398396d899336 # timeout=10 [system-sync_mirrors-fedora-updates-fc26-x86_64] $ /bin/bash -xe /tmp/jenkins3554869966821101733.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc26 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Resyncing repo: fedora-updates-fc26 Syncing yum repo fedora-updates-fc26 for arch: x86_64 fedora-updates-fc26/group 35% [===== ] 0.0 B/s | 662 kB --:-- ETA fedora-updates-fc26/group | 1.8 MB 00:00 : xneur-devel-0.20.0-1.fc26.x86_64.rpm | 17 kB 00:00 Generating yum repo metadata for: fedora-updates-fc26 Could not remove temp metadata dir: .repodata Error was [Errno 39] Directory not empty: '/var/www/html/repos/yum/fedora-updates-fc26/base/.repodata' Please clean up this directory manually. Spawning worker 0 with 1140 pkgs Spawning worker 1 with 1140 pkgs Spawning worker 2 with 1140 pkgs Spawning worker 3 with 1140 pkgs Spawning worker 4 with 1140 pkgs Spawning worker 5 with 1140 pkgs Spawning worker 6 with 1140 pkgs Spawning worker 7 with 1140 pkgs Workers Finished Saving Primary metadata Saving file lists metadata Saving other metadata Generating sqlite DBs Traceback (most recent call last): File "/usr/share/createrepo/genpkgmetadata.py", line 309, in <module> main(sys.argv[1:]) File "/usr/share/createrepo/genpkgmetadata.py", line 274, in main mdgen.doRepoMetadata() File "/usr/lib/python2.7/site-packages/createrepo/__init__.py", line 1014, in doRepoMetadata gen_func(complete_path, csum) File "/usr/lib64/python2.7/site-packages/sqlitecachec.py", line 54, in getFilelists self.repoid)) TypeError: Can not create keyfile index: unable to open database file Build step 'Execute shell' marked build as failure

7 years

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra December 2017