- Infra - oVirt List Archives

oVirt infra daily report - unstable production jobs - 303
by jenkins＠jenkins.phx.ovirt.org 25 Apr '17

25 Apr '17

------=_Part_295_1815500242.1493161206561 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/303//artifact/exported-a… Cheers, Jenkins ------=_Part_295_1815500242.1493161206561 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 25/04/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master-ansible-system-tests/">ovirt_master-ansible-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_295_1815500242.1493161206561--

1 0

[JIRA] (OVIRT-1349) Create Jenkins job for the new poll STD-CI stage
by Gil Shinar (oVirt JIRA) 25 Apr '17

25 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1349?page=com.atlassian.jira.… ] Gil Shinar reassigned OVIRT-1349: --------------------------------- Assignee: Gil Shinar (was: infra) > Create Jenkins job for the new poll STD-CI stage > ------------------------------------------------ > > Key: OVIRT-1349 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1349 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Gil Shinar > > Create Jenkins job for the new poll STD-CI stage > - Created a new stage builder > - Created project and scms for the new stage > - Wrote python script that implements the > poll upstream sources stage > - Added new trigger macro that uses a new parameter > named trigger-repo for repos that has non standard > names > This stage job does as follows: > 1) Clones from gerrit > 2) Updates U/S sources with latest commit in branch > 3) clones the U/S sources > 4) Run std-ci procedure including poll.sh scripts > which is currently empty. -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

1 0

[JIRA] (OVIRT-1349) Create Jenkins job for the new poll STD-CI stage
by Gil Shinar (oVirt JIRA) 25 Apr '17

25 Apr '17

Gil Shinar created OVIRT-1349: --------------------------------- Summary: Create Jenkins job for the new poll STD-CI stage Key: OVIRT-1349 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1349 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra Create Jenkins job for the new poll STD-CI stage - Created a new stage builder - Created project and scms for the new stage - Wrote python script that implements the poll upstream sources stage - Added new trigger macro that uses a new parameter named trigger-repo for repos that has non standard names This stage job does as follows: 1) Clones from gerrit 2) Updates U/S sources with latest commit in branch 3) clones the U/S sources 4) Run std-ci procedure including poll.sh scripts which is currently empty. -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

1 0

[JIRA] (OVIRT-1348) upstream re-basing capability
by Gil Shinar (oVirt JIRA) 25 Apr '17

25 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1348?page=com.atlassian.jira.… ] Gil Shinar reassigned OVIRT-1348: --------------------------------- Assignee: Gil Shinar (was: infra) > upstream re-basing capability > ------------------------------ > > Key: OVIRT-1348 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1348 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Gil Shinar > > The new STD-CI stage actually adds the capability of "rebasing" > prerequisite repositories on top of current one. > That way one won't need to have duplications in two repositories. > Whenver he'll want to work on the current repo, the rebasing > will take place and copy all the files he needs in order to > work. -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

1 0

[JIRA] (OVIRT-1348) upstream re-basing capability
by Gil Shinar (oVirt JIRA) 25 Apr '17

25 Apr '17

Gil Shinar created OVIRT-1348: --------------------------------- Summary: upstream re-basing capability Key: OVIRT-1348 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1348 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra The new STD-CI stage actually adds the capability of "rebasing" prerequisite repositories on top of current one. That way one won't need to have duplications in two repositories. Whenver he'll want to work on the current repo, the rebasing will take place and copy all the files he needs in order to work. -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

1 0

Which is the official oVirt docker repository, 'ovirt' or 'ovirtorg'?
by Juan Hernández 25 Apr '17

25 Apr '17

Hello, Both exist: https://hub.docker.com/u/ovirt https://hub.docker.com/u/ovirtorg The first, 'ovirt', has some branding, but it is empty, no images. The second, 'ovirtorg', has no branding, but hosts some images. Which one should we use to publish our official images? I'd like to start publishing the images that we are building for the engine? Who has the credentials for that? Thanks in advance, Juan Hernández

3 3

[JIRA] (OVIRT-1347) General changes to upstream yamls for the new std-ci stage
by Gil Shinar (oVirt JIRA) 25 Apr '17

25 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1347?page=com.atlassian.jira.… ] Gil Shinar reassigned OVIRT-1347: --------------------------------- Assignee: Gil Shinar (was: infra) > General changes to upstream yamls for the new std-ci stage > ----------------------------------------------------------- > > Key: OVIRT-1347 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1347 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Gil Shinar > > refactor some yamls so I'll have all the prerequisites > for the new std-ci stage -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

1 0

[JIRA] (OVIRT-1347) General changes to upstream yamls for the new std-ci stage
by Gil Shinar (oVirt JIRA) 25 Apr '17

25 Apr '17

Gil Shinar created OVIRT-1347: --------------------------------- Summary: General changes to upstream yamls for the new std-ci stage Key: OVIRT-1347 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1347 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra refactor some yamls so I'll have all the prerequisites for the new std-ci stage -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

1 0

[JIRA] (OVIRT-1069) Make CI information available to scripts in standard CI
by eyal edri [Administrator] (oVirt JIRA) 25 Apr '17

25 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1069?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1069: ------------------------------------------------ Assignee: Daniel Belenky (was: infra) > Make CI information available to scripts in standard CI > ------------------------------------------------------- > > Key: OVIRT-1069 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1069 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: Daniel Belenky > Labels: mock_runner.sh, standard-ci > > Right now scripts running in standard-CI have no information about the environment they are running in. This is by design, because the scripts are supposed to behave the same if they are running locally or on a Jenkins slave. > But there are cases where letting the script know it is running in CI is useful. For example - to make it use the package mirrors in the CI system instead of getting packages over the internet. > It seems that essentially all the information that is passed to '{{mock_runner.sh}}' on the command line should be made available to the automation script as environment variables. Additionally, information from Gerrit would probably also be useful. -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

1 0

[JIRA] (OVIRT-1342) Re: Java exception when pushing changes to Gerrit
by Barak Korren (oVirt JIRA) 25 Apr '17

25 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1342?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1342: ------------------------------------- The error message quoted above is caused because the email of the person submitting the patch appears in two different accounts IDs. Our {{gerrit-dedup}} tool can fix that. This probably has nothing to do with the alerts from Icinga. > Re: Java exception when pushing changes to Gerrit > ------------------------------------------------- > > Key: OVIRT-1342 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1342 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: infra > > Adding infra-support to open a ticket as well. > On Wed, Apr 19, 2017 at 1:42 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote: > > [ykaul@ykaul ovirt-system-tests]$ git review -r origin master > > remote: Processing changes: refs: 2, done > > To ssh://gerrit.ovirt.org:29418/ovirt-system-tests.git > > ! [remote rejected] HEAD -> refs/publish/master (internal server error: > > java.lang.IllegalArgumentException: expected one element but was: > > <1000060, 1001032>) > > error: failed to push some refs to 'ssh://ykaul@gerrit.ovirt.org: > > 29418/ovirt-system-tests.git' > > > > > > It does seem to be pushed, though. Any ideas? > > Y. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal edri > ASSOCIATE 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) -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

1 0