- Infra - oVirt List Archives

[JIRA] (OVIRT-2275) Finish to update "How to run OST" docs
by Greg Sheremeta (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2275?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-2275: --------------------------------------- Sorry, I gave up and deleted the environment. > Finish to update "How to run OST" docs > -------------------------------------- > > Key: OVIRT-2275 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2275 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > We need to finish updating https://gerrit.ovirt.org/#/c/90523/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2305) Clean up dead slaves from the staging Jenkins
by Barak Korren (oVirt JIRA) 11 Jul '18

11 Jul '18

Barak Korren created OVIRT-2305: ----------------------------------- Summary: Clean up dead slaves from the staging Jenkins Key: OVIRT-2305 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2305 Project: oVirt - virtualization made easy Issue Type: Outage Components: Staging infra Reporter: Barak Korren Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2304) Make usrc.py list all the added US patches in the commit message not the last one
by Barak Korren (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2304?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2304: -------------------------------- Issue Type: Improvement (was: New Feature) > Make usrc.py list all the added US patches in the commit message not the last one > --------------------------------------------------------------------------------- > > Key: OVIRT-2304 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2304 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: usrc.py > Reporter: Barak Korren > Assignee: infra > > When running the '{{usrc.py update --commit}}' command, it creates a commit message that includes various details about the patch that was linked to in '{{upstream-sources.yaml}}'. > This commit message does not really show the full picture for the change that is really being done to the DS repo, as when updating '{{upstream-sources.yaml}}', the effictive change to the repo is the sub of all commits between the new commit that is added to '{{upstream-sources.yaml}}' and the one that was there before. > It is desirable to list all the US commits between the previous one to the updated one in the commit message so that it is easier to understand the extent of the actual change that was made. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2304) Make usrc.py list all the added US patches in the commit message not the last one
by Barak Korren (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2304?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2304: -------------------------------- Issue Type: New Feature (was: Outage) > Make usrc.py list all the added US patches in the commit message not the last one > --------------------------------------------------------------------------------- > > Key: OVIRT-2304 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2304 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: usrc.py > Reporter: Barak Korren > Assignee: infra > > When running the '{{usrc.py update --commit}}' command, it creates a commit message that includes various details about the patch that was linked to in '{{upstream-sources.yaml}}'. > This commit message does not really show the full picture for the change that is really being done to the DS repo, as when updating '{{upstream-sources.yaml}}', the effictive change to the repo is the sub of all commits between the new commit that is added to '{{upstream-sources.yaml}}' and the one that was there before. > It is desirable to list all the US commits between the previous one to the updated one in the commit message so that it is easier to understand the extent of the actual change that was made. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2304) Make usrc.py list all the added US patches in the commit message not the last one
by Barak Korren (oVirt JIRA) 10 Jul '18

10 Jul '18

Barak Korren created OVIRT-2304: ----------------------------------- Summary: Make usrc.py list all the added US patches in the commit message not the last one Key: OVIRT-2304 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2304 Project: oVirt - virtualization made easy Issue Type: Outage Components: usrc.py Reporter: Barak Korren Assignee: infra When running the '{{usrc.py update --commit}}' command, it creates a commit message that includes various details about the patch that was linked to in '{{upstream-sources.yaml}}'. This commit message does not really show the full picture for the change that is really being done to the DS repo, as when updating '{{upstream-sources.yaml}}', the effictive change to the repo is the sub of all commits between the new commit that is added to '{{upstream-sources.yaml}}' and the one that was there before. It is desirable to list all the US commits between the previous one to the updated one in the commit message so that it is easier to understand the extent of the actual change that was made. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

oVirt infra daily report - unstable production jobs - 517
by jenkins＠jenkins.phx.ovirt.org 10 Jul '18

10 Jul '18

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/517//artifact/exported-a… Cheers, Jenkins

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 591 - Failure!
by jenkins＠jenkins.phx.ovirt.org 10 Jul '18

10 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/591/ Build Number: 591 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #591 [Sandro Bonazzola] master: consume qemu-kvm-ev test builds ----------------- Failed Tests: ----------------- All tests passed

1 1

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 112 - Failure!
by jenkins＠jenkins.phx.ovirt.org 10 Jul '18

10 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/11… Build Number: 112 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #112 [Sandro Bonazzola] master: consume qemu-kvm-ev test builds ----------------- Failed Tests: ----------------- All tests passed

1 1

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 320 - Failure!
by jenkins＠jenkins.phx.ovirt.org 10 Jul '18

10 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master… Build Number: 320 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #320 [Sandro Bonazzola] master: consume qemu-kvm-ev test builds ----------------- Failed Tests: ----------------- No tests ran.

1 2

[JIRA] (OVIRT-2287) ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs
by Yuval Turgeman (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2287?page=com.atlassian.jira.… ] Yuval Turgeman commented on OVIRT-2287: --------------------------------------- Gal took care of this already - https://gerrit.ovirt.org/#/c/92902/ :) On Tue, Jul 10, 2018, 18:59 Dafna Ron <dron(a)redhat.com> wrote: > host memory is 4720 for both hosts. since one is running the engine should > we increase it? > > {%- for i in range(hostCount) %} > lago-{{ env.suite_name }}-host-{{ i }}: > vm-type: ovirt-host > distro: el7 > service_provider: systemd > memory: 4720 > > > > On Sun, Jul 8, 2018 at 7:38 AM, Barak Korren <bkorren(a)redhat.com> wrote: > >> >> >> On 6 July 2018 at 11:57, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: >> >>> >>> >>> https://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/16… >>> >>> Cannot run VM. There is no host that satisfies current scheduling >>> constraints. See below for details:, The host >>> lago-he-node-ng-suite-master-host-0 did not satisfy internal filter Memory >>> because its available memory is too low (656 MB) to run the VM. >>> >>> >> >> this sounds like something that needs to be fixed in the suit's >> LagoInitFile. >> >> >> >>> -- >>> >>> SANDRO BONAZZOLA >>> >>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>> >>> Red Hat EMEA <https://www.redhat.com/> >>> >>> sbonazzo(a)redhat.com >>> <https://red.ht/sig> >>> >>> _______________________________________________ >>> 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/TDKLML6YDBATF… >>> >>> >> >> >> -- >> Barak Korren >> RHV DevOps team , RHCE, RHCi >> Red Hat EMEA >> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted >> >> _______________________________________________ >> 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/S6F3JGB3C5OSK… >> >> > _______________________________________________ > 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/CUT2OW3NUPU26… > > ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs > ------------------------------------------------------------------------------------- > > Key: OVIRT-2287 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2287 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: sbonazzo > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_lago > Attachments: srv.log > > > https://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/16… > Cannot run VM. There is no host that satisfies current scheduling > constraints. See below for details:, The host > lago-he-node-ng-suite-master-host-0 did not satisfy internal filter Memory > because its available memory is too low (656 MB) to run the VM. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0