- Infra - oVirt List Archives

[JIRA] (OVIRT-1192) Bugzilla bug is missing patchset
by Gil Shinar (oVirt JIRA) 23 Feb '17

23 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1192?page=com.atlassian.jira.… ] Gil Shinar reassigned OVIRT-1192: --------------------------------- Assignee: Gil Shinar (was: infra) > Bugzilla bug is missing patchset > -------------------------------- > > Key: OVIRT-1192 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1192 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: Gil Shinar > > The following bug in Bugzilla is missing a patchset: > https://gerrit.ovirt.org/#/c/72682 > This bug has 5 patchsets but only 1, 2, 3 and 5 are visible in the patchset > list while patchsets 4 and 5 are inaccessible. -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1192) Bugzilla bug is missing patchset
by Gil Shinar (oVirt JIRA) 23 Feb '17

23 Feb '17

Gil Shinar created OVIRT-1192: --------------------------------- Summary: Bugzilla bug is missing patchset Key: OVIRT-1192 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1192 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Gil Shinar Assignee: infra The following bug in Bugzilla is missing a patchset: https://gerrit.ovirt.org/#/c/72682 This bug has 5 patchsets but only 1, 2, 3 and 5 are visible in the patchset list while patchsets 4 and 5 are inaccessible. -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Martin Sivak (oVirt JIRA) 23 Feb '17

23 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Martin Sivak commented on OVIRT-1154: ------------------------------------- And we should start maintaining the contributor/maintainer list too. It will help with assigning reviewers to newly posted patches. Please see my comment about that in the relevant JIRA: https://ovirt-jira.atlassian.net/browse/OVIRT-1165?focusedCommentId=27649&p… > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[ OST Failure Report ] [ oVirt master ] [ 22/2/2017 ] [prepare_migration_attachments_ipv4]
by Barak Korren 23 Feb '17

23 Feb '17

Test failed: [ prepare_migration_attachments_ipv4 ] Link to suspected patches: - Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5480/ Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5480/artif… Error snippet from log: <error> status: 409 reason: Conflict detail: Cannot setup Networks. Operation can be performed only when Host status is Maintenance, Up, NonOperational. </error> -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

2 2

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Martin Sivak (oVirt JIRA) 23 Feb '17

23 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Martin Sivak commented on OVIRT-1154: ------------------------------------- I am not opposed to Gerrit comments, but those need to be part of the message the user gets so we do not have to search for the right syntax. Barak asked me to paste my email about the matter here, so here you go: > Btw, I just found a project that uses whitelist - kubernetes. But they > make it very easy for maintainers to accept patches. Check for example > this pull request: https://github.com/kubernetes/kubernetes/pull/41119 > > The idea I like is that the CI will immediately tell me what needs to > be done in the comments. No need to search through documentation for > the right keyword. > > - The bot told the contributor who the relevant maintainers are, > computed the list of people with enough permissions and notified them > too. And just a comment by maintainer was needed to enable CI for the > pull request. > - The same for failing tests - they provide the command to retrigger > it directly in the message > > It all basically boils down to "Do not make me think" approach. > Everything that needs to be done is immediately obvious without > searching. And that I could accept even with the whitelist enabled. > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1191) Addition to the Jenkins whitelist
by Barak Korren (oVirt JIRA) 23 Feb '17

23 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1191?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1191: ----------------------------------- Assignee: Barak Korren (was: infra) > Addition to the Jenkins whitelist > --------------------------------- > > Key: OVIRT-1191 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1191 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Benny Zlotnik > Assignee: Barak Korren > > Hi, > Please add me to the whitelist > Thanks -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1191) Addition to the Jenkins whitelist
by Barak Korren (oVirt JIRA) 23 Feb '17

23 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1191?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1191: ------------------------------------- Please link to the patch that was blocked. > Addition to the Jenkins whitelist > --------------------------------- > > Key: OVIRT-1191 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1191 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Benny Zlotnik > Assignee: infra > > Hi, > Please add me to the whitelist > Thanks -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1191) Addition to the Jenkins whitelist
by Benny Zlotnik (oVirt JIRA) 23 Feb '17

23 Feb '17

Benny Zlotnik created OVIRT-1191: ------------------------------------ Summary: Addition to the Jenkins whitelist Key: OVIRT-1191 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1191 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Benny Zlotnik Assignee: infra Hi, Please add me to the whitelist Thanks -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-925) OST job failed on workflow error
by eyal edri [Administrator] (oVirt JIRA) 23 Feb '17

23 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-925?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-925: -------------------------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) > OST job failed on workflow error > -------------------------------- > > Key: OVIRT-925 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-925 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > Labels: ost_failures > > http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… > Need to find root cause. > Started by timer > org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: > WorkflowScript: 305: expecting '}', found '' @ line 305, column 1. > 1 error > at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:302) > at org.codehaus.groovy.control.ErrorCollector.addFatalError(ErrorCollector.java:149) > at org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.java:119) > at org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.java:131) > at org.codehaus.groovy.control.SourceUnit.addError(SourceUnit.java:359) > at org.codehaus.groovy.antlr.AntlrParserPlugin.transformCSTIntoAST(AntlrParserPlugin.java:142) > at org.codehaus.groovy.antlr.AntlrParserPlugin.parseCST(AntlrParserPlugin.java:108) > at org.codehaus.groovy.control.SourceUnit.parse(SourceUnit.java:236) > at org.codehaus.groovy.control.CompilationUnit$1.call(CompilationUnit.java:161) > at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:846) > at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:550) > at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:526) > at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:503) > at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:302) > at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:281) > at groovy.lang.GroovyShell.parseClass(GroovyShell.java:731) > at groovy.lang.GroovyShell.parse(GroovyShell.java:743) > at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:106) > at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:376) > at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:343) > at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:212) > at hudson.model.ResourceController.execute(ResourceController.java:98) > at hudson.model.Executor.run(Executor.java:410) > Finished: FAILURE -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1190) Migrate some SAT6 VMs from Amazon to PHX production DC
by Evgheni Dereveanchin (oVirt JIRA) 23 Feb '17

23 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1190?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1190: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Migrate some SAT6 VMs from Amazon to PHX production DC > ------------------------------------------------------ > > Key: OVIRT-1190 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1190 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > > Opening a ticket to start tracking the info for this effort. > Initial info on the instances in Amazon: > 3 m1 larges (8 GB RAM, 2 VCPU, 800.0 GB DISK) > 1 m4 large (8 GB RAM, 2 VCPU, 400 GB DISK) -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0