- Infra - oVirt List Archives

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

30 Aug '19

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

1 0

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

30 Aug '19

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

1 0

[CQ]: 102923, 3 (ovirt-engine-nodejs-modules) failed "ovirt-4.2" system tests
by oVirt Jenkins 30 Aug '19

30 Aug '19

Change 102923,3 (ovirt-engine-nodejs-modules) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/102923/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4762/

1 0

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

30 Aug '19

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

1 0

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

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

1 0

[CQ]: 102941, 2 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Aug '19

29 Aug '19

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

1 0

[CQ]: 102946, 1 (ovirt-host-deploy) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Aug '19

29 Aug '19

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

1 0

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

29 Aug '19

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

1 0

[CQ]: 102745,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 29 Aug '19

29 Aug '19

Change 102745,2 (vdsm) 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/102745/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15608/

1 0

[JIRA] (OVIRT-1602) [RFE] allow passing a gerrit link to ovirt-system-tests_manual
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1602?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-1602: ----------------------------- Resolution: Fixed Status: Done (was: To Do) This is now supported by the new CLI tool written by [~accountid:557058:5b558a0f-5666-4b7f-a655-83e5cc3a5de0] > [RFE] allow passing a gerrit link to ovirt-system-tests_manual > -------------------------------------------------------------- > > Key: OVIRT-1602 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1602 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > How about $subject? > So that when ovirt-system-tests_manual sees a gerrit link supplied in > CUSTOM_REPOS, it will do by itself 'ci please build' (extra points for > checking if that's already done and reusing) and use the resultant > build as if that build itself was supplied in CUSTOM_REPOS, thus > freeing the user from doing that? I find myself many times running 'ci > please build' only to later wait until it finished and then pass that > to ovirt-system-tests_manual. For projects that are very quick to > build, that's a bit tedious, but not too much. But for engine builds, > that take somewhat longer, I often forget this and come back later. It > would have been nice to be able to do this in a "single shot". > Thanks, > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2599) Investigate sync between JIRA cloud to JIRA server
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2599?page=com.atlassian.jira.… ] Eyal Edri reassigned OVIRT-2599: -------------------------------- Assignee: Anton Marchukov (was: infra) > Investigate sync between JIRA cloud to JIRA server > -------------------------------------------------- > > Key: OVIRT-2599 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2599 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Eyal Edri > Assignee: Anton Marchukov > > We would like to converge on using a single JIRA board to show all our issues. > There are some solution available, more info the following links; > https://community.atlassian.com/t5/Jira-questions/Sync-between-JIRA-Cloud-a… > from that blog: > https://marketplace.atlassian.com/apps/1215199/backbone-issue-sync-for-jira… > https://confluence.atlassian.com/jiracoreserver073/linking-issues-861257339… > https://confluence.atlassian.com/applinks/application-links-documentation-1… > https://www.connectall.com/ > https://marketplace.atlassian.com/apps/1215199/backbone-issue-sync-for-jira… > There are other options, shown up on a quick search. > Once we find a reasonable plugin, we can ask PnT to purchase and install it on the d/s instance. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2714: ----------------------------- Status: Done (was: To Do) > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2078) Check option for private changes on Gerrit
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2078?page=com.atlassian.jira.… ] Eyal Edri reassigned OVIRT-2078: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Check option for private changes on Gerrit > ------------------------------------------ > > Key: OVIRT-2078 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2078 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Eyal Edri > Assignee: Evgheni Dereveanchin > Priority: High > > We need an option sometimes to post private changes ( not draft ) to Gerrit, > Gerrit has support for private changes [1], we should check if its available in current version. > [1] https://gerrit-review.googlesource.com/Documentation/intro-user.html#privat… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2540) improving the upgrade suites
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2540?page=com.atlassian.jira.… ] Eyal Edri reassigned OVIRT-2540: -------------------------------- Assignee: Galit Rosenthal (was: infra) > improving the upgrade suites > ----------------------------- > > Key: OVIRT-2540 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2540 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Galit Rosenthal > Priority: High > > our upgrade suites are testing engine upgrade with no objects created pre upgrade and after upgrade are running a basic sanity test. > 1. upgrade should not take more then basic sanity and as we are running both for the upgrade suite we need to change it > 2. we are not testing vdsm/host upgrade and we are also not testing basic objects upgrade > the upgrade suites should be modified. > [~mwperina] said he would write a design and until we have modified the test-cases we should perhaps stop running upgrade on every run as I do not think its contributing to our testing. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2566) make network suite blocking
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2566: ---------------------------------- we can consider this once we enable zuul/patch gating. [~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143] will we be able to enable network suite for gating network patches? > make network suite blocking > --------------------------- > > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. > Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". > [~gbenhaim(a)redhat.com] what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2757) Re: Jenkins Developer group
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2757?page=com.atlassian.jira.… ] Eyal Edri closed OVIRT-2757. ---------------------------- Resolution: Fixed > Re: Jenkins Developer group > --------------------------- > > Key: OVIRT-2757 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2757 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Anton Marchukov > Assignee: Anton Marchukov > > Adding infra-support to generate a ticket. > > On 16 Jul 2019, at 13:34, Andrej Cernek <acernek(a)redhat.com> wrote: > > > > Hi, > > I am intern in the oVirt networking team, but I am missing the Gerrit/ManualTrigger permission. Could you add me to the Developer group? My user ID is acernek. > > Thank you > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/O4RERPUWYX2ZP… > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2446) Github push trigger will fail if was trigger by a tag push
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2446?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2446: ----------------------------- Status: To Do (was: Blocked) > Github push trigger will fail if was trigger by a tag push > ---------------------------------------------------------- > > Key: OVIRT-2446 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2446 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Roy Golan > Assignee: infra > > When pushing a tag to a GH it triggers the jenkins webhook. In the invoked > job, > it will try to fech a new head with that tag, but that will fail since the > repo doesn't have > a head since it is started as git init. > A breakdown from > https://jenkins.ovirt.org/job/oVirt_ovirt-openshift-extensions_standard-on-… > - git init a repo > *14:57:15* > git init > /home/jenkins/workspace/oVirt_ovirt-openshift-extensions_standard-on-ghpush/ovirt-openshift-extensions > # timeout=10 > - git fetch tags (maybe the problem is here as it doesn't reffer to refs/tags) > *15:35:07* [check-merged.el7.x86_64] > git fetch --tags --progress > https://gerrit.ovirt.org/jenkins +refs/heads/*:refs/remotes/origin/* > - fetch upstream changes, which is here a tag v0.3.2, so it uses > 'refs/tags/v0.3.2' > *14:57:18* > git fetch --tags --progress > https://github.com/oVirt/ovirt-openshift-extensions > +refs/tags/v0.3.2:myhead > This fails with > *14:57:19* stderr: error: cannot update ref 'refs/heads/myhead': > trying to write non-commit object > 3c7b5a5d243d1f3bcecbe7b527726b06113d0ec5 to branch 'refs/heads/myhead' > While in regular merge with a tag on it uses 'refs/heads/master': > *15:35:10* [check-merged.el7.x86_64] > git fetch --tags --progress > https://gerrit.ovirt.org/jenkins +refs/heads/master:myhead > Since refs/tags/v0.3.2 doesn't exist locally it can't reference it. Since > refs/heads/master exists locally it can create the alias 'myhead' to it. > I would like to have the option to push a tag and trigger a build but this > is not working atm without a commit attached to it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2294) HC symlinks to deployment scripts
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2294?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2294: ---------------------------------- [~accountid:5b25ec3f8b08c009c48b25c9] can you add info on this? is it still needed? > HC symlinks to deployment scripts > ---------------------------------- > > Key: OVIRT-2294 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2294 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Components: OST > Reporter: Galit Rosenthal > Assignee: infra > > HC - create symlinks for deployment scripts -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2695: ----------------------------- Resolution: Fixed Status: Done (was: Blocked) > [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?) > ------------------------------------------------------------------ > > Key: OVIRT-2695 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: CI client projects, Jenkins Slaves > Reporter: Nir Soffer > Assignee: Barak Korren > > build-artifacts on s390x fail now with: > [Errno 2] No such file or directory: > '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm' > Here are few example failures: > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > This is going to block the change queue when we merge these patches, > and we have 4.3 build soon. > We had this issue few week ago, and Barak fixed this by deleting caches on > the slaves. I hope this can be fixed quickly > this time. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[CQ]: 102841, 26 (ovirt-node-coreos) failed "ovirt-master" system tests
by oVirt Jenkins 29 Aug '19

29 Aug '19

Change 102841,26 (ovirt-node-coreos) 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/102841/26 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15607/

1 0

[JIRA] (OVIRT-2785) Unable to add Documentation +1 flag to patch
by Dafna Ron (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2785?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2785: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Unable to add Documentation +1 flag to patch > -------------------------------------------- > > Key: OVIRT-2785 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2785 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Steve Goodman > Assignee: infra > > I was able to add the Documentation +1 to patches in the ovirt-engine-api project, but now I can't. For example, https://gerrit.ovirt.org/#/c/102438/, when I click Reply, I don't see the Documentation flag. I do see the Code Review and Verified flags. > I checked to see if I'm on https://gerrit.ovirt.org/#/admin/groups/131,members and I am. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2785) Unable to add Documentation +1 flag to patch
by Dafna Ron (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2785?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2785: ---------------------------------- any time 🙂 > Unable to add Documentation +1 flag to patch > -------------------------------------------- > > Key: OVIRT-2785 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2785 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Steve Goodman > Assignee: infra > > I was able to add the Documentation +1 to patches in the ovirt-engine-api project, but now I can't. For example, https://gerrit.ovirt.org/#/c/102438/, when I click Reply, I don't see the Documentation flag. I do see the Code Review and Verified flags. > I checked to see if I'm on https://gerrit.ovirt.org/#/admin/groups/131,members and I am. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2785) Unable to add Documentation +1 flag to patch
by Steve Goodman (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2785?page=com.atlassian.jira.… ] Steve Goodman commented on OVIRT-2785: -------------------------------------- OK. I don’t believe that I’m part of any other group right now. Thanks, Dafna\! > Unable to add Documentation +1 flag to patch > -------------------------------------------- > > Key: OVIRT-2785 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2785 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Steve Goodman > Assignee: infra > > I was able to add the Documentation +1 to patches in the ovirt-engine-api project, but now I can't. For example, https://gerrit.ovirt.org/#/c/102438/, when I click Reply, I don't see the Documentation flag. I do see the Code Review and Verified flags. > I checked to see if I'm on https://gerrit.ovirt.org/#/admin/groups/131,members and I am. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2140) enforce SSL on resources.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2140?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2140: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > enforce SSL on resources.ovirt.org > ---------------------------------- > > Key: OVIRT-2140 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2140 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > SSL was enabled on Resources with OVIRT-1472, this ticket is to transform the non-SSL virtual hosts into redirects to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2140) enforce SSL on resources.ovirt.org
by Anton Marchukov (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2140?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2140: ---------------------------------------- Using “http” instead of “https” nowadays seems like using “telnet” instead of “ssh”, so I understand why security team is concerned. Unfortunately if something is not working it is not a question of if we still need to do it, but how to fix it instead. I think we are ok to proceed given that we do it gradually and test for any issues. Once issues are identified we can discuss how to approach them. > enforce SSL on resources.ovirt.org > ---------------------------------- > > Key: OVIRT-2140 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2140 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > SSL was enabled on Resources with OVIRT-1472, this ticket is to transform the non-SSL virtual hosts into redirects to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2140) enforce SSL on resources.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2140?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2140: --------------------------------------------- {{https://gerrit.ovirt.org/102951}} Change mirrorlist link to HTTPS > enforce SSL on resources.ovirt.org > ---------------------------------- > > Key: OVIRT-2140 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2140 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > SSL was enabled on Resources with OVIRT-1472, this ticket is to transform the non-SSL virtual hosts into redirects to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2140) enforce SSL on resources.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2140?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2140: --------------------------------------------- Thanks for the feedback. Need to test if creating an HTTP->HTTPS redirect can break existing older installations. I’m not sure yum/dnf can follow redirects. Let’s start by changing the link in the mirrorlist file here: [https://resources.ovirt.org/pub/yum-repo/mirrorlist|https://resources.ovirt…] This will make all requests to resources go through https, we can then move on and change links in [ovirt-release|https://gerrit.ovirt.org/gitweb?p=ovirt-release.git;a=blob;f=…] [~accountid:557058:3a069952-633d-482c-90ab-2451cac6751a] what do you think? Can I go ahead and change the protocol in the mirrorlist? > enforce SSL on resources.ovirt.org > ---------------------------------- > > Key: OVIRT-2140 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2140 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > SSL was enabled on Resources with OVIRT-1472, this ticket is to transform the non-SSL virtual hosts into redirects to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2785) Unable to add Documentation +1 flag to patch
by Dafna Ron (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2785?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2785: ---------------------------------- since your old user name is inactive, if you were added with that user to any groups you will need to be re-added with the new user. this is not something you can fix yourself but as I could only find you in that project then it should not happen again. if you have any other groups that you would like me to check in case I missed it, please let me know and I will check it now. > Unable to add Documentation +1 flag to patch > -------------------------------------------- > > Key: OVIRT-2785 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2785 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Steve Goodman > Assignee: infra > > I was able to add the Documentation +1 to patches in the ovirt-engine-api project, but now I can't. For example, https://gerrit.ovirt.org/#/c/102438/, when I click Reply, I don't see the Documentation flag. I do see the Code Review and Verified flags. > I checked to see if I'm on https://gerrit.ovirt.org/#/admin/groups/131,members and I am. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2785) Unable to add Documentation +1 flag to patch
by Steve Goodman (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2785?page=com.atlassian.jira.… ] Steve Goodman commented on OVIRT-2785: -------------------------------------- I tried now and it works, thank you\! How can I fix my two accounts so that this doesn’t happen again? > Unable to add Documentation +1 flag to patch > -------------------------------------------- > > Key: OVIRT-2785 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2785 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Steve Goodman > Assignee: infra > > I was able to add the Documentation +1 to patches in the ovirt-engine-api project, but now I can't. For example, https://gerrit.ovirt.org/#/c/102438/, when I click Reply, I don't see the Documentation flag. I do see the Code Review and Verified flags. > I checked to see if I'm on https://gerrit.ovirt.org/#/admin/groups/131,members and I am. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2784) please update maintainers for ovirt-engine-nodejs-modules
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2784?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2784: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > please update maintainers for ovirt-engine-nodejs-modules > --------------------------------------------------------- > > Key: OVIRT-2784 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2784 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > as per https://lists.ovirt.org/archives/list/devel@ovirt.org/thread/S3ULX7EQZ7YHRM… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[CQ]: 102802,1 (ovirt-vdsmfake) failed "ovirt-master" system tests
by oVirt Jenkins 29 Aug '19

29 Aug '19

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

1 0

[JIRA] (OVIRT-2785) Unable to add Documentation +1 flag to patch
by Dafna Ron (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2785?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2785: ---------------------------------- He does have two accounts but one is marked as inactive. I removed and added the user to see if the issue is that the inactive account was the one that is added and not the active one. [~accountid:5cbfd1757742d70ffbc788e2] can you try now? > Unable to add Documentation +1 flag to patch > -------------------------------------------- > > Key: OVIRT-2785 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2785 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Steve Goodman > Assignee: infra > > I was able to add the Documentation +1 to patches in the ovirt-engine-api project, but now I can't. For example, https://gerrit.ovirt.org/#/c/102438/, when I click Reply, I don't see the Documentation flag. I do see the Code Review and Verified flags. > I checked to see if I'm on https://gerrit.ovirt.org/#/admin/groups/131,members and I am. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2785) Unable to add Documentation +1 flag to patch
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2785?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2785: ---------------------------------- I just added myself to the documentation group and was able to add the Documentation flag myself. Is it possible you have 2 users that might need merging? On Thu, Aug 29, 2019 at 10:54 AM Dafna Ron (oVirt JIRA) < -- Eyal edri He / Him / His MANAGER CONTINUOUS PRODUCTIZATION SYSTEM ENGINEERING Red Hat <https://www.redhat.com/> <https://red.ht/sig> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel) > Unable to add Documentation +1 flag to patch > -------------------------------------------- > > Key: OVIRT-2785 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2785 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Steve Goodman > Assignee: infra > > I was able to add the Documentation +1 to patches in the ovirt-engine-api project, but now I can't. For example, https://gerrit.ovirt.org/#/c/102438/, when I click Reply, I don't see the Documentation flag. I do see the Code Review and Verified flags. > I checked to see if I'm on https://gerrit.ovirt.org/#/admin/groups/131,members and I am. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2785) Unable to add Documentation +1 flag to patch
by Dafna Ron (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2785?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2785: ---------------------------------- [~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143] was this removed? > Unable to add Documentation +1 flag to patch > -------------------------------------------- > > Key: OVIRT-2785 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2785 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Steve Goodman > Assignee: infra > > I was able to add the Documentation +1 to patches in the ovirt-engine-api project, but now I can't. For example, https://gerrit.ovirt.org/#/c/102438/, when I click Reply, I don't see the Documentation flag. I do see the Code Review and Verified flags. > I checked to see if I'm on https://gerrit.ovirt.org/#/admin/groups/131,members and I am. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

2 1

[JIRA] (OVIRT-2785) Unable to add Documentation +1 flag to patch
by Steve Goodman (oVirt JIRA) 29 Aug '19

29 Aug '19

Steve Goodman created OVIRT-2785: ------------------------------------ Summary: Unable to add Documentation +1 flag to patch Key: OVIRT-2785 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2785 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Steve Goodman Assignee: infra I was able to add the Documentation +1 to patches in the ovirt-engine-api project, but now I can't. For example, https://gerrit.ovirt.org/#/c/102438/, when I click Reply, I don't see the Documentation flag. I do see the Code Review and Verified flags. I checked to see if I'm on https://gerrit.ovirt.org/#/admin/groups/131,members and I am. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2140) enforce SSL on resources.ovirt.org
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2140?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2140: ---------------------------------- [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] can we enable https for only the official releases under /pub and not for tested? so it won't affect the CI jobs speed, at least not at first stage? > enforce SSL on resources.ovirt.org > ---------------------------------- > > Key: OVIRT-2140 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2140 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > SSL was enabled on Resources with OVIRT-1472, this ticket is to transform the non-SSL virtual hosts into redirects to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[CQ]: 102845,2 (cockpit-ovirt) failed "ovirt-master" system tests
by oVirt Jenkins 29 Aug '19

29 Aug '19

Change 102845,2 (cockpit-ovirt) 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/102845/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15602/

1 0

[JIRA] (OVIRT-2140) enforce SSL on resources.ovirt.org
by Marc Dequènes (Duck) (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2140?page=com.atlassian.jira.… ] Marc Dequènes (Duck) commented on OVIRT-2140: --------------------------------------------- [~accountid:557058:2dee8503-051b-4630-8a75-2c544524dce8] with the above security concerns then YES we need to do it and infosec just came at my door to ask for the progress, so we’d better prioritize this task before one day we’re told to shutdown the service altogether. > enforce SSL on resources.ovirt.org > ---------------------------------- > > Key: OVIRT-2140 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2140 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > SSL was enabled on Resources with OVIRT-1472, this ticket is to transform the non-SSL virtual hosts into redirects to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2140) enforce SSL on resources.ovirt.org
by Marc Dequènes (Duck) (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2140?page=com.atlassian.jira.… ] Marc Dequènes (Duck) commented on OVIRT-2140: --------------------------------------------- [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] signed packages on HTTP are not safe because old releases are also valid thus it’s possible to do replay attacks by providing older and security buggy packages. it’s better but not sufficient. > enforce SSL on resources.ovirt.org > ---------------------------------- > > Key: OVIRT-2140 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2140 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > SSL was enabled on Resources with OVIRT-1472, this ticket is to transform the non-SSL virtual hosts into redirects to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

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

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

1 0

[CQ]: 960bb3d (ovirt-web-ui) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Aug '19

28 Aug '19

A system test invoked by the "ovirt-4.2" change queue including change 960bb3d (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change 4aaca2c (ovirt-web-ui) 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 4aaca2c (ovirt-web-ui) 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-web-ui/commit/960bb3d33f463f68448eda99b74acb… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-web-ui/commit/4aaca2c9b02867698024c4ae2f3e28… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4756/

1 0

[CQ]: 960bb3d (ovirt-web-ui) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Aug '19

28 Aug '19

A system test invoked by the "ovirt-4.3" change queue including change 960bb3d (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change 4aaca2c (ovirt-web-ui) 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 4aaca2c (ovirt-web-ui) 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-web-ui/commit/960bb3d33f463f68448eda99b74acb… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-web-ui/commit/4aaca2c9b02867698024c4ae2f3e28… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1927/

1 0

[CQ]: 960bb3d (ovirt-web-ui) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Aug '19

28 Aug '19

A system test invoked by the "ovirt-master" change queue including change 960bb3d (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change 4aaca2c (ovirt-web-ui) 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 4aaca2c (ovirt-web-ui) 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-web-ui/commit/960bb3d33f463f68448eda99b74acb… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-web-ui/commit/4aaca2c9b02867698024c4ae2f3e28… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15598/

1 0

[CQ]: 8f8d072 (ovirt-web-ui) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Aug '19

28 Aug '19

A system test invoked by the "ovirt-4.3" change queue including change 8f8d072 (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change 4aaca2c (ovirt-web-ui) 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 4aaca2c (ovirt-web-ui) 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-web-ui/commit/8f8d072fc78be48bd832a239eaa8a4… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-web-ui/commit/4aaca2c9b02867698024c4ae2f3e28… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1925/

1 0

[CQ]: 8f8d072 (ovirt-web-ui) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Aug '19

28 Aug '19

A system test invoked by the "ovirt-4.2" change queue including change 8f8d072 (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change 4aaca2c (ovirt-web-ui) 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 4aaca2c (ovirt-web-ui) 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-web-ui/commit/8f8d072fc78be48bd832a239eaa8a4… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-web-ui/commit/4aaca2c9b02867698024c4ae2f3e28… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4754/

1 0

[CQ]: 8f8d072 (ovirt-web-ui) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Aug '19

28 Aug '19

A system test invoked by the "ovirt-master" change queue including change 8f8d072 (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change 4aaca2c (ovirt-web-ui) 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 4aaca2c (ovirt-web-ui) 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-web-ui/commit/8f8d072fc78be48bd832a239eaa8a4… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-web-ui/commit/4aaca2c9b02867698024c4ae2f3e28… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15596/

1 0

[CQ]: 4aaca2c (ovirt-web-ui) failed "ovirt-4.3" system tests
by oVirt Jenkins 28 Aug '19

28 Aug '19

Change 4aaca2c (ovirt-web-ui) is probably the reason behind recent system test failures in the "ovirt-4.3" 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-web-ui/commit/4aaca2c9b02867698024c4ae2f3e28… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1924/

1 0

[CQ]: 4aaca2c (ovirt-web-ui) failed "ovirt-4.2" system tests
by oVirt Jenkins 28 Aug '19

28 Aug '19

Change 4aaca2c (ovirt-web-ui) 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-web-ui/commit/4aaca2c9b02867698024c4ae2f3e28… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4753/

1 0

[CQ]: 4aaca2c (ovirt-web-ui) failed "ovirt-master" system tests
by oVirt Jenkins 28 Aug '19

28 Aug '19

Change 4aaca2c (ovirt-web-ui) 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-web-ui/commit/4aaca2c9b02867698024c4ae2f3e28… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15594/

1 0

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

28 Aug '19

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

1 0