December 2016 - Infra - oVirt List Archives

[JIRA] (OST-17) repoman should only sync el7 rpms
by eyal edri [Administrator] (oVirt JIRA) 26 Dec '16

26 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OST-17?page=com.atlassian.jira.plug… ] eyal edri [Administrator] commented on OST-17: ---------------------------------------------- +1 if it can evaluate $distro when it runs. > repoman should only sync el7 rpms > ---------------------------------- > > Key: OST-17 > URL: https://ovirt-jira.atlassian.net/browse/OST-17 > Project: oVirt system tests > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > on OST jobs repoman also syncs fc24 rpms without any reason, since we only test el7. > we should include only el7 x86_64 for now to save time and avoid errors when network is unstable. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OST-17) repoman should only sync el7 rpms
by eyal edri [Administrator] (oVirt JIRA) 26 Dec '16

26 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OST-17?page=com.atlassian.jira.plug… ] eyal edri [Administrator] reassigned OST-17: -------------------------------------------- Assignee: Daniel Belenky (was: infra) > repoman should only sync el7 rpms > ---------------------------------- > > Key: OST-17 > URL: https://ovirt-jira.atlassian.net/browse/OST-17 > Project: oVirt system tests > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: Daniel Belenky > Priority: Highest > > on OST jobs repoman also syncs fc24 rpms without any reason, since we only test el7. > we should include only el7 x86_64 for now to save time and avoid errors when network is unstable. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OST-17) repoman should only sync el7 rpms
by Barak Korren (oVirt JIRA) 26 Dec '16

26 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OST-17?page=com.atlassian.jira.plug… ] Barak Korren commented on OST-17: --------------------------------- Maybe: {code} sh "echo rec:$repo_url/$distro > extra_sources" {code} Would be better > repoman should only sync el7 rpms > ---------------------------------- > > Key: OST-17 > URL: https://ovirt-jira.atlassian.net/browse/OST-17 > Project: oVirt system tests > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > on OST jobs repoman also syncs fc24 rpms without any reason, since we only test el7. > we should include only el7 x86_64 for now to save time and avoid errors when network is unstable. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OST-17) repoman should only sync el7 rpms
by Nadav Goldin (oVirt JIRA) 26 Dec '16

26 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OST-17?page=com.atlassian.jira.plug… ] Nadav Goldin commented on OST-17: --------------------------------- I think it would be safe enough to just give the full /el7 path in the groovy code that generates 'extra_sources', so repoman would take el7 only. i.e. change: https://github.com/oVirt/jenkins/blob/master/jobs/confs/groovy-scripts/test… {code} sh "echo rec:$repo_url > extra_sources" {code} to {code} sh "echo rec:$repo_url/el7 > extra_sources" {code} As I don't think we have any short term plans to test it on anything else than el7. > repoman should only sync el7 rpms > ---------------------------------- > > Key: OST-17 > URL: https://ovirt-jira.atlassian.net/browse/OST-17 > Project: oVirt system tests > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > on OST jobs repoman also syncs fc24 rpms without any reason, since we only test el7. > we should include only el7 x86_64 for now to save time and avoid errors when network is unstable. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OST-17) repoman should only sync el7 rpms
by eyal edri [Administrator] (oVirt JIRA) 26 Dec '16

26 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OST-17?page=com.atlassian.jira.plug… ] eyal edri [Administrator] reassigned OST-17: -------------------------------------------- Assignee: infra (was: eyal edri [Administrator]) > repoman should only sync el7 rpms > ---------------------------------- > > Key: OST-17 > URL: https://ovirt-jira.atlassian.net/browse/OST-17 > Project: oVirt system tests > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > on OST jobs repoman also syncs fc24 rpms without any reason, since we only test el7. > we should include only el7 x86_64 for now to save time and avoid errors when network is unstable. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3621 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 26 Dec '16

26 Dec '16

------=_Part_339_593499840.1482755220204 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3621/, Build Number: 3621, Build Status: FAILURE ------=_Part_339_593499840.1482755220204--

1 1

[JIRA] (OVIRT-981) ovirt-release 4.1 doesn't build 4.1 experimental rpms
by eyal edri [Administrator] (oVirt JIRA) 26 Dec '16

26 Dec '16

eyal edri [Administrator] created OVIRT-981: ----------------------------------------------- Summary: ovirt-release 4.1 doesn't build 4.1 experimental rpms Key: OVIRT-981 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-981 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra We have 4.1 experimental repos but we didn't create release rpm for them ( missing the .in file on ovirt-4.1 branch ) -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-981) ovirt-release 4.1 doesn't build 4.1 experimental rpms
by eyal edri [Administrator] (oVirt JIRA) 26 Dec '16

26 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-981?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-981: -------------------------------------------- Epic Link: OVIRT-411 > ovirt-release 4.1 doesn't build 4.1 experimental rpms > ----------------------------------------------------- > > Key: OVIRT-981 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-981 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > > We have 4.1 experimental repos but we didn't create release rpm for them ( missing the .in file on ovirt-4.1 branch ) -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-938) Fix Jenkins slave connection dying on vdsm check_merged jobs
by danken (oVirt JIRA) 26 Dec '16

26 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-938?page=com.atlassian.jira.p… ] danken commented on OVIRT-938: ------------------------------ This is indeed due to our buggy check-merged script, which mistakenly called `kill 0`. > Fix Jenkins slave connection dying on vdsm check_merged jobs > ------------------------------------------------------------ > > Key: OVIRT-938 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-938 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Something in the vdsm build_artifacs job makes the Jenkins slave disconnect when it is running. This in turn makes the cleanup scripts not run on the slave leaving it dirty enough to make the next job on that slave fail. > Example of this can be seen here: > http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/692/console > Relevant log lines: > {code} > 21:49:00 Ran 44 tests in 1231.988s > 21:49:00 > 21:49:00 OK > 21:49:00 + return 0 > 21:49:00 sh: [13086: 1 (255)] tcsetattr: Inappropriate ioctl for device > 21:49:00 Took 2464 seconds > 21:49:00 =================================== > 21:49:00 logout > 21:49:01 Slave went offline during the build > 21:49:01 ERROR: Connection was broken: java.io.IOException: Unexpected termination of the channel > 21:49:01 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) > 21:49:01 Caused by: java.io.EOFException > 21:49:01 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353) > 21:49:01 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822) > 21:49:01 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804) > 21:49:01 at java.io.ObjectInputStream.<init>(ObjectInputStream.java:301) > 21:49:01 at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48) > 21:49:01 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) > 21:49:01 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) > 21:49:01 > 21:49:01 Build step 'Execute shell' marked build as failure > 21:49:01 Performing Post build task... > 21:49:01 Match found for :.* : True > 21:49:01 Logical operation result is TRUE > 21:49:01 Running script : #!/bin/bash -x > 21:49:01 echo "shell-scripts/mock_cleanup.sh" > ... SNIP ... > 21:49:01 Exception when executing the batch command : no workspace from node hudson.slaves.DumbSlave[fc24-vm06.phx.ovirt.org] which is computer hudson.slaves.SlaveComputer@30863c81 and has channel null > 21:49:01 Build step 'Post build task' marked build as failure > 21:49:02 ERROR: Step ?Archive the artifacts? failed: no workspace for vdsm_master_check-merged-el7-x86_64 #692 > 21:49:02 ERROR: Failed to evaluate groovy script. > 21:49:02 java.lang.NullPointerException: Cannot invoke method child() on null object > 21:49:02 at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:77) > 21:49:02 at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45) > 21:49:02 at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) > 21:49:02 at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:32) > 21:49:02 at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) > 21:49:02 at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) > 21:49:02 at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) > 21:49:02 at Script1.run(Script1.groovy:2) > 21:49:02 at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580) > 21:49:02 at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618) > 21:49:02 at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589) > 21:49:02 at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.evaluate(SecureGroovyScript.java:166) > 21:49:02 at org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder.perform(GroovyPostbuildRecorder.java:361) > 21:49:02 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) > 21:49:02 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) > 21:49:02 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) > 21:49:02 at hudson.model.Build$BuildExecution.post2(Build.java:185) > 21:49:02 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) > 21:49:02 at hudson.model.Run.execute(Run.java:1763) > 21:49:02 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) > 21:49:02 at hudson.model.ResourceController.execute(ResourceController.java:98) > 21:49:02 at hudson.model.Executor.run(Executor.java:410) > 21:49:02 Build step 'Groovy Postbuild' marked build as failure > 21:49:02 Started calculate disk usage of build > 21:49:02 Finished Calculation of disk usage of build in 0 seconds > 21:49:02 Finished: FAILURE > {code} -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-980) fc25 mock is extremely slow
by Nadav Goldin (oVirt JIRA) 26 Dec '16

26 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-980?page=com.atlassian.jira.p… ] Nadav Goldin commented on OVIRT-980: ------------------------------------ Of course this needs some more testing. I didn't say it was related to mock, but actually to fc25 itself. > fc25 mock is extremely slow > --------------------------- > > Key: OVIRT-980 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-980 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Nadav Goldin > Assignee: infra > > Now that we build fc25 rpms for Lago I noticed that the tests themselves(not mock setup) are much slower than el7/fc24. On average they took 500 seconds on el7/fc24/fc23, while on fc25 they take ~700 seconds. I don't think this is specific to Lago(or at least I see no reason ATM), so worth checking when other projects start building fc25 if it is a fc25 issue. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0