- Infra - oVirt List Archives

Jenkins build became unstable: ovirt_4.2_publish-rpms_nightly #610
by jenkins＠jenkins.phx.ovirt.org 20 May '19

20 May '19

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

1 2

oVirt infra daily report - unstable production jobs - 830
by jenkins＠jenkins.phx.ovirt.org 20 May '19

20 May '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/830//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 99935,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 19 May '19

19 May '19

Change 99935,3 (ovirt-engine) 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/99935/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14173/

1 0

[JIRA] (OVIRT-2731) Can't docker push when using newer docker daemon?
by Roy Golan (oVirt JIRA) 19 May '19

19 May '19

Roy Golan created OVIRT-2731: -------------------------------- Summary: Can't docker push when using newer docker daemon? Key: OVIRT-2731 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2731 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Roy Golan Assignee: infra With this patch <https://github.com/oVirt/ovirt-openshift-extensions/pull/136>I'm building multi-stage images in my builds, and I'm trying to push them to quay. The docker push was working without any problems before the daemon change. The difference is that now the docker client is inside a container, which is inside mock, which has the docker socket of a docker daemon version 18. Docker login succeeds according to the job logs The push when uploading layers: [2019-05-19T06:12:03.008Z] + make push-containers PUSH_LATEST=0 <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] Login Succeeded <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] docker push quay.io/rgolangh/ovirt-flexvolume-driver:0.4.0-11.gd0ead0b <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] The push refers to repository [quay.io/rgolangh/ovirt-flexvolume-driver] <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] bf535c6e5461: Preparing <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] e6318b33302c: Preparing <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] a3890b39a2b2: Preparing <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] e78e5b504103: Preparing <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] f7fa4accb0ea: Preparing <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] 35265ad107f5: Preparing <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] 4765a2d3f85d: Preparing <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] 35265ad107f5: Waiting <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] 4765a2d3f85d: Waiting <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] unauthorized: access to the requested resource is not authorized <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] make: *** [container-push-ovirt-flexvolume-driver] Error 1 Can I get the daemon logs? anyone see it? any advice? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

1 0

[JIRA] (OVIRT-2730) Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/
by Barak Korren (oVirt JIRA) 19 May '19

19 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2730?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2730: ------------------------------------- On Fri, 17 May 2019 at 01:04, Nir Soffer (oVirt JIRA) < I looked at the parameters screen <https://jenkins.ovirt.org/job/standard-manual-runner/265/parameters/> for the refspec you passed to the manual runner (refs/changes/07/100007/8) and then simply checked out the patch with `git review -d 100007`. Looking at `stdci.yaml` there you can see its quite different then the one in the master branch. So is commenting `ci test please` or `ci please test` or just `ci test` in gerrit.... Checkout the patch and have a look, the CI system does not rebase before testing, so it does not matter which branch you intend to merge into, only which commit you started from when first creating the local branch you wrote the patch in. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/ > ------------------------------------------------------------------------------ > > Key: OVIRT-2730 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2730 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I tried to run check-patch and check-patch linters substage from the > command line: > using: > https://github.com/nirs/oci/pull/37 > I assumed that this will run the entire check-patch stage, including all > the sub stages: > ./ovirt-ci run -s check-patch 100007 > But it run something that looks like check-patch with el7: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > The test environment seems to be different that what we have when > check-patch is triggered > from gerrit. > Then I tried to run the linters substage: > ./ovirt-ci run -s check-patch.linters 100007 > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > ./ovirt-ci run -s check-patch.linters 100007 > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Both succeeded without running anything :-) > Running build-artifacts works, not sure about check-network. > Can we fix the manual job so: > - it run exactly the same way as it run when gerrit trigger the job > - allow selection of a sub stage? > - nice to have - allow selection of multiple sub stages > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

1 0

[JIRA] (OVIRT-2730) Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/
by Nir Soffer (oVirt JIRA) 19 May '19

19 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2730?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2730: ----------------------------------- On Thu, May 16, 2019 at 8:23 AM Barak Korren (oVirt JIRA) < How do you test this? But CI is sometimes flaky, and we need to re-trigger a build. Using the command line tool is an easy way. However this was mainly testing the capabilities of the manual runner. I don't think many people will use check-patch from the command line. Because you can't select substages like that. Very strange, the patch I tested is was on master which has valid stdci.yaml. Here is another check-network build - seems to work correctly: https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… I also did other 2 builds today, and they look normal: ./ovirt-ci run build-artifacts 98608 https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… ./ovirt-ci run check-patch 98608 https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… So running stages seems to work fine. It runs the exact same code. > Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/ > ------------------------------------------------------------------------------ > > Key: OVIRT-2730 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2730 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I tried to run check-patch and check-patch linters substage from the > command line: > using: > https://github.com/nirs/oci/pull/37 > I assumed that this will run the entire check-patch stage, including all > the sub stages: > ./ovirt-ci run -s check-patch 100007 > But it run something that looks like check-patch with el7: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > The test environment seems to be different that what we have when > check-patch is triggered > from gerrit. > Then I tried to run the linters substage: > ./ovirt-ci run -s check-patch.linters 100007 > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > ./ovirt-ci run -s check-patch.linters 100007 > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Both succeeded without running anything :-) > Running build-artifacts works, not sure about check-network. > Can we fix the manual job so: > - it run exactly the same way as it run when gerrit trigger the job > - allow selection of a sub stage? > - nice to have - allow selection of multiple sub stages > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

2 1

oVirt infra daily report - unstable production jobs - 829
by jenkins＠jenkins.phx.ovirt.org 19 May '19

19 May '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/829//artifact/exported-a… Cheers, Jenkins

1 0

Build failed in Jenkins: system-mk_mirrors_index-yum #53042
by jenkins＠jenkins.phx.ovirt.org 18 May '19

18 May '19

See <http://jenkins.ovirt.org/job/system-mk_mirrors_index-yum/53042/display/redi…> ------------------------------------------ Started by upstream project "system-sync_mirrors-fedora-base-fc29-x86_64" build number 579 originally caused by: Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-mk_mirrors_index-yum/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from http://gerrit.ovirt.org/jenkins.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:894) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1816) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune" returned status code 128: stdout: stderr: fatal: unable to access 'http://gerrit.ovirt.org/jenkins.git/': The requested URL returned error: 503 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to mirrors.phx.ovirt.org at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.GeneratedMethodAccessor301.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy94.execute(Unknown Source) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:892) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1816) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) ERROR: Error fetching remote repo 'origin'

1 1

oVirt infra daily report - unstable production jobs - 828
by jenkins＠jenkins.phx.ovirt.org 18 May '19

18 May '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/828//artifact/exported-a… Cheers, Jenkins

1 0

[Ovirt] [CQ weekly status] [17-05-2019]
by Dafna Ron 17 May '19

17 May '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) Last failure was on 15-5 for project ovirt-ansible-engine-setup due to failure in test 002_bootstrap.add_master_storage_domain. The fix for this test was submitted and merged in ost: https://gerrit.ovirt.org/#/c/100089/ *CQ-4.3*: GREEN (#1) Last failure was on 16-05 for project ovirt-host due to a build-artifacts for fc28. the issue has been resolved. *CQ-Master:* RED (#1) We have a current failure in project ovirt-engine which started last night. The failure is in run vm test and caused by change: https://gerrit.ovirt.org/#/c/99372/6 - core: Initial Ignition support over custom script <https://gerrit.ovirt.org/#/c/99372/6> It already has a fix (thank you Roy for the fast response) and we are awaiting a merge for the patch: https://gerrit.ovirt.org/#/c/100133/ - core: handle a case where cloudinit script is null Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… [3] 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