- Infra - oVirt List Archives

Planned restart of production services
by Evgheni Dereveanchin 14 Jun '18

14 Jun '18

Hi everyone, I will be restarting several production systems within the next few hours to perform planned maintenance. The following services will be unreachable for some period of time: - gerrit.ovirt.org - code review - jenkins.ovirt.org - CI master It will not be possible to submit/review patches, clone repositories or run CI jobs during this period. I will announce you once the maintenance is complete. -- Regards, Evgheni Dereveanchin

1 2

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2200: -------------------------------- Component/s: usrc.py > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: STDCI DSL, usrc.py > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 01a6c0f (ovirt-ansible-v2v-conversion-host) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jun '18

14 Jun '18

Change 01a6c0f (ovirt-ansible-v2v-conversion-host) 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://github.com/oVirt/ovirt-ansible-v2v-conversion-host/commit/01a6c0f54… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8209/

1 0

[CQ]: 92238, 1 (ovirt-engine-dashboard) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jun '18

14 Jun '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 1 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 Jun '18

14 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/1/ Build Number: 1 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- No tests ran.

1 33

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2200: ------------------------------------- Just some more thoughts about this - we could maybe solve this by "exploading" directory symlinks in our code as if they were symlinks to each and every file in the directory. That way all the other symlink handling code will just work. But we need to be careful about this, as we can have directory symlinks to directories with directory symlinks in them... > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: STDCI DSL > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2200: ------------------------------------- [~dbelenky(a)redhat.com] not sure about the priority for this, we've seen that links to directories have a tendency to become directories with links sooner or later anyway... As you say its not a very easy fix, we need to go into the symlink resolution algorithms in usrc.py and add directory support. We have other things we want to do and other bugs we're not solving so well need to consider carefully if and when we're going to solve this. In the meantime there are various workarounds that could be used... > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: STDCI DSL > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2200: -------------------------------- Component/s: STDCI DSL > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: STDCI DSL > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2200: -------------------------------- Issue Type: Bug (was: By-EMAIL) > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch
by Daniel Belenky (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2200: --------------------------------------- [~bkorren(a)redhat.com] seems like something we've saw before with the original change-resolver. The current design doesn't resolve changes when the symlink is to the containing directory rather then to the file itself. Fix shouldn't take too long but not easy also. Should we give this higher priority? > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0