May 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2055) failure in suspend resume vm not related to reported change - need to investigate
by Dafna Ron (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2055?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2055: ---------------------------------- as this is random, we need to see if resume suspend vm is still failing periodically and if so if we see the same errors, > failure in suspend resume vm not related to reported change - need to investigate > --------------------------------------------------------------------------------- > > Key: OVIRT-2055 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2055 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > Change 91507,1 (ovirt-engine-sdk-java) 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/91507/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ > I think the issue is on qemu/libvirt changed queries: > https://pastebin.com/afyeUAcT > https://pastebin.com/va20Y5Hp > checking his with vdsm people. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2054) false change reported since package is not deployed on ost
by Dafna Ron (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2054?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2054: ---------------------------------- Barak, any advice on how to start investigating this? > false change reported since package is not deployed on ost > ---------------------------------------------------------- > > Key: OVIRT-2054 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2054 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > Change 91507,1 (ovirt-engine-sdk-java) 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/91507/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ > The package is not deployed on OST so it could not have been the reason for failure. > + I am investigating the cause of failure but since we do not deploy the package on ost there is actually no chance that the failure was due to the change - hence its false report. > Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2056) All CQ failing due to ovirt-4.1 centos being EOL
by Dafna Ron (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2056?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2056: ----------------------------- Resolution: Fixed Status: Done (was: To Do) patch solved the issue. closing > All CQ failing due to ovirt-4.1 centos being EOL > ------------------------------------------------ > > Key: OVIRT-2056 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2056 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > 21:50:07 [upgrade-from-release-suit] raise e > 21:50:07 [upgrade-from-release-suit] yum.Errors.NoMoreMirrorsRepoError: failure: repodata/repomd.xml from centos-ovirt-4.1-el7: [Errno 256] No more mirrors to try. > 21:50:07 [upgrade-from-release-suit] http://mirror.centos.org/centos/7.4.1708/virt/x86_64/ovirt-4.1/repodata/rep…: [Errno 14] HTTP Error 404 - Not Found > 21:50:07 [upgrade-from-release-suit] > 21:50:07 [upgrade-from-release-suit] * Running reposync: ERROR (in 0:00:01) > 21:50:07 [upgrade-from-release-suit] # Syncing remote repos locally (this might take some time): ERROR (in 0:00:01) > 21:50:07 [upgrade-from-release-suit] @ Create prefix internal repo: ERROR (in 0:00:01) > 21:50:07 [upgrade-from-release-suit] Error occured, aborting -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2046) Bring up Trello-Bugzilla automation inside OpenShift to support oVirt 4.3 agile flow
by Evgheni Dereveanchin (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2046?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2046: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Bring up Trello-Bugzilla automation inside OpenShift to support oVirt 4.3 agile flow > ------------------------------------------------------------------------------------ > > Key: OVIRT-2046 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2046 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: Evgheni Dereveanchin > Priority: High > > Please bring up a service on shift.ovirt.org to support multiple Trello board for the oVirt team to integrate with Bugzilla. > [~msivak(a)redhat.com] should have all the relevant info the deployment, which works well locally on containers. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[oVirt Jenkins] ovirt-node-ng_4.2_build-artifacts-el7-x86_64 - Build # 89 - Failure!
by jenkins＠jenkins.phx.ovirt.org 31 May '18

31 May '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_64/8… Build Number: 89 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #89 [Daniel Belenky] Introduce STDCI summary [Sandro Bonazzola] ovirt-image-uploader: drop 4.1 jobs, move to fc28 [Sandro Bonazzola] ovirt-setup-lib: drop 4.1, move to fc28 [Daniel Belenky] Fix a typo in standard-stage analizer->analyzer [gzaidman] ovirt-engine: move from fc27 to fc28 [Sandro Bonazzola] kickstart: drop upstream cockpit copr repo ----------------- Failed Tests: ----------------- No tests ran.

1 1

[CQ]: 91731, 1 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 31 May '18

31 May '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 187 - Failure!
by jenkins＠jenkins.phx.ovirt.org 31 May '18

31 May '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/187/ Build Number: 187 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #187 [Sandro Bonazzola] repos: adding cockpit-machines-ovirt [Evgheni Dereveanchin] Verify Jenkins user settings from global_setup ----------------- Failed Tests: ----------------- No tests ran.

1 31

Re: [ovirt-devel] [Announcement] Introducing Standard CI build summary
by Eyal Edri 31 May '18

31 May '18

Adding infra also. I think it would be great to do a tweet on it on @ovirt as well. Adding an example link from the Jenkins repo: http://jenkins.ovirt.org/job/jenkins_standard-check-patch/625/artifact/ci_b… On Wed, May 30, 2018 at 5:49 PM, Daniel Belenky <dbelenky(a)redhat.com> wrote: > Hi, > > On behalf of oVirt's CI team, I'm happy to announce the STDCI build > summary - > *We've used patternfly *[1] <http://www.patternfly.org/> to ensure a clean, > simple and elegant view of information for your builds. > The summary is available for STDCI V2 [2] projects and it is located > under *build-artifacts/ci_build_summary.html* > > > *[image: location.png]* > > > STDCI build summary is a single web page, generated dynamically for every > build on STDCI. > It visualizes all CI threads that ran for that build and features a set of > quick links. > > The main view shows a list of all threads with an indicator if that thread > failed or passed. > The quick links to the right of each thread lead to *log* and *artifacts* > of that thread only. > Note that *log* shows the output of your script only to ease debugging. > [image: threads_list.png] > > At the top right side, you will find a set of quick links for convenience: > > [image: menus.png] > > *Test results* (available if JUnit XML files were exported during the > build) leads to a summary of all JUnit test results that were collected > during the build. > *Test results analyzer *shows the history of test execution results in a > tabular format. > *Findbugs results *(available if Findbugs report was generated and > exported during the build) shows trend report for Findbugs. > *Full build log* shows the full log of all threads. This log is harder to > understand as it includes output from CI runtime environment as well as > from your scripts. > > *Rebuild (for GitHub PR)/Retrigger (for Gerrit patch): *Run the build > again. The new build will report and vote to Gerrit/GitHub with the new > result. > *View PR/patch: *Links back to the PR on GitHub or patchset page in > Gerrit. > > > [image: view_in_jenkins.png] > *View in Jenkins* will lead you back to the build view in Jenkins > > [image: view_in_blueocean.png] > *View in Blue Ocean *will lead you to the build view in Jenkins Blue > Ocean view > > STDCI Documentation https://ovirt-infra-docs.readthedocs. > io/en/latest/CI/Build_and_test_standards/index.html > > For any questions, don't hesitate to contact the CI team at #rhev-integ, > #rhev-dev > or view mail at infra(a)ovirt.org. > > Thanks, > Daniel. > > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-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/devel@ovirt.org/ > message/XCRLR7XPCYBOMDT5MGBYHHI4FKO3427C/ > > -- Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

[CQ]: 91826,4 (ovirt-setup-lib) failed "ovirt-4.1" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 91826,4 (ovirt-setup-lib) is probably the reason behind recent system test failures in the "ovirt-4.1" 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/91826/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1796/

1 0

[CQ]: 91218,3 (vdsm) failed "ovirt-4.2" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 91218,3 (vdsm) 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/91218/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2128/

1 0