June 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2254) Create slave borrowing flow
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2254?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2254: -------------------------------- Epic Link: OVIRT-2178 > Create slave borrowing flow > --------------------------- > > Key: OVIRT-2254 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2254 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Master, Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > Create a set of jobs and groovy functions that will enable one Jenkins master to borrow slaves from another jenkins master. > h3. Acceptance criteria -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2252) The s390x slave is used in parallel by both the staging and the production CI systems
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2252?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2252: -------------------------------- Component/s: (was: CI Mirrors) Jenkins Slaves > The s390x slave is used in parallel by both the staging and the production CI systems > ------------------------------------------------------------------------------------- > > Key: OVIRT-2252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > Since we only have one s390x slave, it is currently attached to both the staging and the production CI systems, and while they use separate user accounts, it turns out this is not enough to isolate them from one another. > The are several issues that are caused by this configuration: > # Tests that allocate a fixed network port can fail if they are run by both systems at the same time - this happens in practice when sending Python patchs to the '{{jenkins}}' repo because the {{mirror_client.py}} tests start a web server on port 8675. > # The {{mock_cleanup.sh}} script that is being run by one system can time out trying to umount things from a mock environment that was created and is being used by the other system. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2252) The s390x slave is used in parallel by both the staging and the production CI systems
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2252?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2252: -------------------------------- Description: "Since we only have one s390x slave, it is currently attached to both the staging and the production CI systems, and while they use separate user accounts, it turns out this is not enough to isolate them from one another.\r\n\r\nThe are several issues that are caused by this configuration:\r\n# Tests that allocate a fixed network port can fail if they are run by both systems at the same time - this happens in practice when sending Python patchs to the '{{jenkins}}' repo because the {{mirror_client.py}} tests start a web server on port 8675.\r\n# The {{mock_cleanup.sh}} script that is being run by one system can time out trying to umount things from a mock environment that was created and is being used by the other system.\r\n\r\n\r\n\r\n" (was: One of the tests of the CI mirrors python package is starting up an HTTP server on a fixed port number. This can cause an issue if the same test is running in parallel on the same machine. This typically cannot be an issue on the CI infra because it never runs more then one STDCI thread at a time on a given slave. This issue does arise specifically on the s390x slave because there the same slave is used both by the staging and the production CI systems. In that case the two systems might be trying to run the same test at the same time, so this can lead to port allocation exceptions. ) > The s390x slave is used in parallel by both the staging and the production CI systems > ------------------------------------------------------------------------------------- > > Key: OVIRT-2252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors > Reporter: Barak Korren > Assignee: infra > > Since we only have one s390x slave, it is currently attached to both the staging and the production CI systems, and while they use separate user accounts, it turns out this is not enough to isolate them from one another. > The are several issues that are caused by this configuration: > # Tests that allocate a fixed network port can fail if they are run by both systems at the same time - this happens in practice when sending Python patchs to the '{{jenkins}}' repo because the {{mirror_client.py}} tests start a web server on port 8675. > # The {{mock_cleanup.sh}} script that is being run by one system can time out trying to umount things from a mock environment that was created and is being used by the other system. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2252) The s390x slave is used in parallel by both the staging and the production CI systems
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2252?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2252: -------------------------------- Summary: The s390x slave is used in parallel by both the staging and the production CI systems (was: Rece condition in python tests in jenkins repo on s390x) > The s390x slave is used in parallel by both the staging and the production CI systems > ------------------------------------------------------------------------------------- > > Key: OVIRT-2252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors > Reporter: Barak Korren > Assignee: infra > > One of the tests of the CI mirrors python package is starting up an HTTP server on a fixed port number. > This can cause an issue if the same test is running in parallel on the same machine. This typically cannot be an issue on the CI infra because it never runs more then one STDCI thread at a time on a given slave. > This issue does arise specifically on the s390x slave because there the same slave is used both by the staging and the production CI systems. In that case the two systems might be trying to run the same test at the same time, so this can lead to port allocation exceptions. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2252) Rece condition in python tests in jenkins repo on s390x
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2252?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2252: -------------------------------- Description: "One of the tests of the CI mirrors python package is starting up an HTTP server on a fixed port number.\r\n\r\nThis can cause an issue if the same test is running in parallel on the same machine. This typically cannot be an issue on the CI infra because it never runs more then one STDCI thread at a time on a given slave.\r\n\r\nThis issue does arise specifically on the s390x slave because there the same slave is used both by the staging and the production CI systems. In that case the two systems might be trying to run the same test at the same time, so this can lead to port allocation exceptions.\r\n\r\n\r\n" (was: One of the tests of the CI mirrors python package is starting up an HTTP server on a fixed port number. This can cause an issue if the same test is running in parallel on the same machine. This typically cannot be an issue on the CI infra because it never runs more then one STDCI thread at a time on a given slave. This issue does arise specifically on the s390x slave because there the same slave is used both by the staging and the production CI systems. In that case the two systems might be trying to run the same test at the same time, so this can lead to port allocation exceptions.) > Rece condition in python tests in jenkins repo on s390x > ------------------------------------------------------- > > Key: OVIRT-2252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors > Reporter: Barak Korren > Assignee: infra > > One of the tests of the CI mirrors python package is starting up an HTTP server on a fixed port number. > This can cause an issue if the same test is running in parallel on the same machine. This typically cannot be an issue on the CI infra because it never runs more then one STDCI thread at a time on a given slave. > This issue does arise specifically on the s390x slave because there the same slave is used both by the staging and the production CI systems. In that case the two systems might be trying to run the same test at the same time, so this can lead to port allocation exceptions. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 292 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Jun '18

25 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/292/ Build Number: 292 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #292 [Sandro Bonazzola] yum-repos: master: adjusted for new packages ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.snapshot_merge Error Message: status: 409 reason: Conflict detail: Cannot remove Snapshot. Snapshot is currently being created for VM vm0. Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 68, in wrapper return func(prefix.virt_env.engine_vm().get_api(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/004_basic_sanity.py", line 200, in snapshot_merge api.vms.get(VM0_NAME).snapshots.list()[-2].delete() File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 34001, in delete headers={"Correlation-Id":correlation_id,"Content-type":None} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 57, in delete return self.request('DELETE', url, body, headers, cls=cls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request persistent_auth=self.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body) RequestError: status: 409 reason: Conflict detail: Cannot remove Snapshot. Snapshot is currently being created for VM vm0.

1 3

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 323 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Jun '18

25 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/323/ Build Number: 323 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #323 [Sandro Bonazzola] yum-repos: master: adjusted for new packages ----------------- Failed Tests: ----------------- All tests passed

1 1

[CQ]: 92522, 2 (ovirt-engine-dashboard) failed "ovirt-master" system tests
by oVirt Jenkins 25 Jun '18

25 Jun '18

Change 92522,2 (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/92522/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8355/

1 0

[CQ]: 91870, 7 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 25 Jun '18

25 Jun '18

Change 91870,7 (ovirt-provider-ovn) 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/91870/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8350/

1 0

[JIRA] (OVIRT-2248) Add CI for kubevirt-apb repo
by Gal Ben Haim (oVirt JIRA) 25 Jun '18

25 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2248?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2248: -------------------------------- Assignee: Gal Ben Haim (was: infra) Status: In Progress (was: To Do) > Add CI for kubevirt-apb repo > ---------------------------- > > Key: OVIRT-2248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2248 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Gal Ben Haim > Assignee: Gal Ben Haim > Priority: High > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0