- Infra - oVirt List Archives

[CQ]: 97250, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jan '19

29 Jan '19

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

1 0

[CQ]: 97112, 12 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jan '19

29 Jan '19

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

1 0

oVirt infra daily report - unstable production jobs - 719
by jenkins＠jenkins.phx.ovirt.org 29 Jan '19

29 Jan '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/719//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 96578, 36 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Jan '19

28 Jan '19

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

1 0

[CQ]: 96567, 39 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Jan '19

28 Jan '19

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

1 0

[JIRA] (OVIRT-2653) Enable IPv6 for glance.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 28 Jan '19

28 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2653?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2653: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Enable IPv6 for glance.ovirt.org > -------------------------------- > > Key: OVIRT-2653 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2653 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Dominik Holler > Assignee: Evgheni Dereveanchin > Priority: Low > > glance.ovirt.org should be reachable from IPv6, because it is included in the default installation of oVirt. > oVirt 4.3.0 supports IPv6-only scenarios. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-kvm-common-el7-x86_64 #2144
by jenkins＠jenkins.phx.ovirt.org 28 Jan '19

28 Jan '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-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-centos-kvm-common-el7-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/changes/59/95959/1:test --prune > git rev-parse origin/test^{commit} # timeout=10 > git rev-parse test^{commit} # timeout=10 Checking out Revision 05b40dfb4ec43a82530e8c471395d1858e5c59e1 (test) > git config core.sparsecheckout # timeout=10 > git checkout -f 05b40dfb4ec43a82530e8c471395d1858e5c59e1 Commit message: "mirror-reposync: remove gluster-3.10 mirror" > git rev-list --no-walk 05b40dfb4ec43a82530e8c471395d1858e5c59e1 # timeout=10 [system-sync_mirrors-centos-kvm-common-el7-x86_64] $ /bin/bash -xe /tmp/jenkins8217577837560254053.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-kvm-common-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1022, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 700, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 695, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 632, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 875, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 821, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 914, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 189, in __init__ raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-base-fc29/metalink.xml is not XML Build step 'Execute shell' marked build as failure

1 1

Jenkins build became unstable: ovirt_master_publish-rpms_nightly #1239
by jenkins＠jenkins.phx.ovirt.org 28 Jan '19

28 Jan '19

See <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/1239/display…>

1 1

Jenkins build became unstable: ovirt_4.2_publish-rpms_nightly #487
by jenkins＠jenkins.phx.ovirt.org 28 Jan '19

28 Jan '19

See <http://jenkins.ovirt.org/job/ovirt_4.2_publish-rpms_nightly/487/display/red…>

1 1

oVirt infra daily report - unstable production jobs - 718
by jenkins＠jenkins.phx.ovirt.org 28 Jan '19

28 Jan '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/718//artifact/exported-a… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Barak Korren (oVirt JIRA) 27 Jan '19

27 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2662: ------------------------------------- The issue with adding to the org is that the user also gets permissions to all other projects along the way, and its also something the project maintainers are not supposed to be able to do. It would be best if we could find something that: # Permanently affects a single project # Can be easily done by maintainers. > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Eyal Edri (oVirt JIRA) 27 Jan '19

27 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2662: ---------------------------------- I wasn't aware of that, maybe its best to add the user to the oVirt org as a permanent solution since the whitelist can be removed as you say, until we'll have something permanent. > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Barak Korren (oVirt JIRA) 27 Jan '19

27 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2662: ------------------------------------- No he does not. He either need to be in the org or added via the bot command. Adding via the bot command saves the user name in the job XML file, so if we refresh the XML for some reason, like updating the job with JJB, the added user list goes away. I think we merged a few patches that refreshed all the jobs in the system recently, so that explains why the adding seems to fail from [~gshereme(a)redhat.com]'s point of view. Since we're making our own Ansible code for the job updates for the containerized masters now, we can consider adding a feature to preserve user whitelists there. Here are a few other tickets where issues and improvements to the whitelist mechanism have been discussed in the past: * OVIRT-1154 * OVIRT-1657 > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2653) Enable IPv6 for glance.ovirt.org
by Eyal Edri (oVirt JIRA) 27 Jan '19

27 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2653?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2653: ---------------------------------- [~ederevea] is that possible for our glance instance on PHX? How much work is needed to enable it? > Enable IPv6 for glance.ovirt.org > -------------------------------- > > Key: OVIRT-2653 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2653 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Dominik Holler > Assignee: infra > Priority: Low > > glance.ovirt.org should be reachable from IPv6, because it is included in the default installation of oVirt. > oVirt 4.3.0 supports IPv6-only scenarios. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 97298, 1 (ovirt-log-collector) failed "ovirt-master" system tests
by oVirt Jenkins 27 Jan '19

27 Jan '19

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

1 0

[CQ]: 97262, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Jan '19

27 Jan '19

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

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Eyal Edri (oVirt JIRA) 27 Jan '19

27 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2662: ---------------------------------- [~bkorren(a)redhat.com] is that true? the user has to be part of the oVirt ORG first before he can be added to whitelist with the 'add to whitelist' or its a bug we need to investigate? > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2661) No space left on vm0038.workers-phx.ovirt.org
by Barak Korren (oVirt JIRA) 27 Jan '19

27 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2661?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2661: ----------------------------------- Assignee: Barak Korren (was: infra) > No space left on vm0038.workers-phx.ovirt.org > --------------------------------------------- > > Key: OVIRT-2661 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2661 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Jenkins Slaves > Reporter: sbonazzo > Assignee: Barak Korren > > Hi, took > https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org/ > offline due to no space left. > Can you please reprovision the VM and possibly add some more disk to it > while doing? > Thanks, > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2661) No space left on vm0038.workers-phx.ovirt.org
by Barak Korren (oVirt JIRA) 27 Jan '19

27 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2661?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2661: ------------------------------------- [~dbelenky(a)redhat.com] [~eedri], [~eyonasi(a)redhat.com] [~ederevea] WDYT? > No space left on vm0038.workers-phx.ovirt.org > --------------------------------------------- > > Key: OVIRT-2661 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2661 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Jenkins Slaves > Reporter: sbonazzo > Assignee: infra > > Hi, took > https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org/ > offline due to no space left. > Can you please reprovision the VM and possibly add some more disk to it > while doing? > Thanks, > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2661) No space left on vm0038.workers-phx.ovirt.org
by Barak Korren (oVirt JIRA) 27 Jan '19

27 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2661?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2661: ------------------------------------- I've cleaned up and restored the slave, growing the disk is not an option, we`ll need to do that for all slaves. The issue seems to be that with the diverse set of work we have running on the slave the mock caches simply pile up even though we only keep them for two days. For most jobs that is not an issue but it makes the node /appliance build jobs crash because of the sheer amount of space they use. Once they crash they leave running processes behind that prevent the data they left from being successfully deleted, thereby making the next job in turn crash as well. It seems we simply crossed some threshold with the amount of separate mock environment caches we keep. In the short term the only simple solution would be to decrease the time we keep mock caches. > No space left on vm0038.workers-phx.ovirt.org > --------------------------------------------- > > Key: OVIRT-2661 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2661 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Jenkins Slaves > Reporter: sbonazzo > Assignee: infra > > Hi, took > https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org/ > offline due to no space left. > Can you please reprovision the VM and possibly add some more disk to it > while doing? > Thanks, > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 97298, 1 (ovirt-log-collector) failed "ovirt-master" system tests
by oVirt Jenkins 27 Jan '19

27 Jan '19

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

1 0

oVirt infra daily report - unstable production jobs - 717
by jenkins＠jenkins.phx.ovirt.org 27 Jan '19

27 Jan '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/717//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 97262, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jan '19

26 Jan '19

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

1 0

[CQ]: db9535f (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 26 Jan '19

26 Jan '19

Change db9535f (ovirt-ansible-hosted-engine-setup) 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-ansible-hosted-engine-setup/commit/db9535f14… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12520/

1 0

[CQ]: 97224, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jan '19

26 Jan '19

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

1 0

[CQ]: 97254, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jan '19

26 Jan '19

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

1 0

[CQ]: 97253, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jan '19

26 Jan '19

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

1 0

[CQ]: 97114, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jan '19

26 Jan '19

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

1 0

[CQ]: 7661de0 (ovirt-ansible-repositories) failed "ovirt-master" system tests
by oVirt Jenkins 26 Jan '19

26 Jan '19

Change 7661de0 (ovirt-ansible-repositories) 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-ansible-repositories/commit/7661de009d1ca132… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12493/

1 0

[CQ]: 96683, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jan '19

26 Jan '19

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

1 0

[CQ]: 97264, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jan '19

26 Jan '19

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

1 0

oVirt infra daily report - unstable production jobs - 716
by jenkins＠jenkins.phx.ovirt.org 26 Jan '19

26 Jan '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/716//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 97263, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jan '19

25 Jan '19

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

1 0

[Ovirt] [CQ weekly status] [25-01-2019]
by Dafna Ron 25 Jan '19

25 Jan '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: GREEN (#1) We have no current failures. Last failed job was for ovirt-ansible-hosted-engine due to a failed build-artiacts job on Jan 24. the issue has been resolved today by Simon Tiraboschi *CQ-Master:* RED (#1) 1. tests are still failing on ovirt-engine master due to create of domain in version 5. this was reported to the list this week and a patch has been merged to engine: https://gerrit.ovirt.org/97262 The change is currently in sected off changes and should pass CQ in the next 24 hours. you can view the status of the patch in the last "get next" job in CQ: https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chang… Current running jobs for 4.2 [1] and master [2] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0

[CQ]: 97145, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jan '19

25 Jan '19

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

1 0

[CQ]: 97144, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jan '19

25 Jan '19

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

1 0

[CQ]: 1352673 (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jan '19

25 Jan '19

A system test invoked by the "ovirt-4.2" change queue including change 1352673 (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change db9535f (ovirt-ansible-hosted- engine-setup) 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 db9535f (ovirt-ansible-hosted- engine-setup) 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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/1352673c9… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/db9535f14… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3787/

1 0

[CQ]: 96609, 12 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jan '19

25 Jan '19

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

1 0

[CQ]: 96177, 13 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jan '19

25 Jan '19

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

2 1

[JIRA] (OVIRT-2657) Please import ovirt-engine-sdk-go in oVirt organization
by sbonazzo (oVirt JIRA) 25 Jan '19

25 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2657?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-2657: --------------------------------- Il giorno ven 25 gen 2019 alle ore 06:00 Joey Ma <majunjiev(a)gmail.com> ha scritto: > Hi Sandro, > > I'm writing to expect to have a discussion with you about the upcoming CI > integration work. > > As we know that the ovirt-engine-sdk-go project is just a generator for go > sdk, not the sdk itself. So previously I used Travis-CI [1] to do the > testing and building, as well as pushing the auto-generated sdk code back > to another github repo https://github.com/imjoey/go-ovirt . Developers > could then use the sdk easily by '''import "github.com/imjoey/go-ovirt" > '''. > > So I was wondering if the CI integration work could be divided into the > following sequenced steps: > 1. Transfer the existing imjoey/go-ovirt repo under oVirt org, as also > mentioned in [2]; > 2. Besides the testing and building by Travis-CI, also make the > ovirt/ovirt-engine-sdk-go repo be capable of pushing the auto-generated > code to the ovirt/go-ovirt repo; > > Much similar to that the kubevirt/kubevirt project uses Travis-CI to > push the auto-generated Python SDK back to kubevirt/client-python [3]; > 3. Add integration with oVirt jenkins for testing, building and packaging > for rpm/src-rpm; > > To be honest, I am not quite sure if that meets the standard in our > community. Please feel free to correct me and your insights on that would > be highly appreciated. Thanks. > > Ondra can you please assist Joey setting up automation for the Go SDK to match the other SDKs? > Regards, > Joey > > [1]: *https://github.com/oVirt/ovirt-engine-sdk-go/blob/master/.travis/deploy-codes.sh > <https://github.com/oVirt/ovirt-engine-sdk-go/blob/master/.travis/deploy-cod…>* > [2]: https://ovirt-jira.atlassian.net/browse/OVIRT-2460 > [3]: https://github.com/kubevirt/client-python > > On Mon, Jan 21, 2019 at 3:58 PM Sandro Bonazzola <sbonazzo(a)redhat.com> > wrote: > >> Hi, >> ovirt-engine-sdk-go project has been accepted as incubator project under >> oVirt organization. >> Can you please import it granting Joey Ma <majunjiev(a)gmail.com> >> maintainer privileges for it? Joey has been already added as developer to >> oVirt team in github with >> https://ovirt-jira.atlassian.net/browse/OVIRT-2460 >> The project is currently in github at >> https://github.com/imjoey/ovirt-engine-sdk-go >> >> Joey, once the project is imported, please ensure to create jenkins jobs >> for testing and building it and add builds to master and 4.3 change queues. >> >> Thanks, >> -- >> >> SANDRO BONAZZOLA >> >> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >> >> Red Hat EMEA <https://www.redhat.com/> >> >> sbonazzo(a)redhat.com >> <https://red.ht/sig> >> > -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> > Please import ovirt-engine-sdk-go in oVirt organization > ------------------------------------------------------- > > Key: OVIRT-2657 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2657 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Hi, > ovirt-engine-sdk-go project has been accepted as incubator project under > oVirt organization. > Can you please import it granting Joey Ma <majunjiev(a)gmail.com> maintainer > privileges for it? Joey has been already added as developer to oVirt team > in github with https://ovirt-jira.atlassian.net/browse/OVIRT-2460 > The project is currently in github at > https://github.com/imjoey/ovirt-engine-sdk-go > Joey, once the project is imported, please ensure to create jenkins jobs > for testing and building it and add builds to master and 4.3 change queues. > Thanks, > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 96176, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jan '19

25 Jan '19

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

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 463 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Jan '19

25 Jan '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/463/ Build Number: 463 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #463 [Dafna Ron] ovirt-master: remove uneeded packages from pkgs file [Daniel Belenky] Containerized loader node ----------------- Failed Tests: ----------------- No tests ran.

1 1

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 463 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Jan '19

25 Jan '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/463/ Build Number: 463 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #463 [Dafna Ron] ovirt-master: remove uneeded packages from pkgs file [Daniel Belenky] Containerized loader node ----------------- Failed Tests: ----------------- No tests ran.

1 1

[CQ]: db9535f (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.2" system tests
by oVirt Jenkins 25 Jan '19

25 Jan '19

Change db9535f (ovirt-ansible-hosted-engine-setup) 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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/db9535f14… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3782/

1 0

oVirt infra daily report - unstable production jobs - 715
by jenkins＠jenkins.phx.ovirt.org 25 Jan '19

25 Jan '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/715//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 96174, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Jan '19

24 Jan '19

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

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Eyal Edri (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2662: ---------------------------------- Patches are welcome :) but just LMK and I'll update the msg... > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2625) lists.ovirt.org not showing threads
by Greg Sheremeta (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2625?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-2625: --------------------------------------- another example: https://lists.ovirt.org/archives/list/devel@ovirt.org/thread/FGTZNIGTNIKYEV… 3 messages, only 1 shows > lists.ovirt.org not showing threads > ----------------------------------- > > Key: OVIRT-2625 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2625 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > Attachments: Selection_258.png > > > Hi, > lists.ovirt.org hyperkitty is once again not showing threads. I tried to > find my old Jira ticket, but Jira is down. > For example, this doesn't show the thread, but there are 8 replies: > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/SDDH2OC5RBOVYY… > Screenshot: https://imgur.com/a/xHKDN6K > [image: Selection_258.png] > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Greg Sheremeta (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-2662: --------------------------------------- I asked Bohdan to check. "I think the user also has to be part of the oVirt org" -- that should be in the bot's message, then :) > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Eyal Edri (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2662: ---------------------------------- I think the user also has to be part of the oVirt org, I've just added 'bond95' user to the oVirt ORG, can you ask bond95 to send another PR and check it again? If it doesn't work, ,maybe [~ederevea][~amarchuk][~dron] can check it tomorrow, ( though most people are in devConf). If not [~eyonasi(a)redhat.com] can try to check it next week. I suggest to look at the logs in the webhooks to see what's happening. > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0