- Infra - oVirt List Archives

[JIRA] (OVIRT-2256) Install the Parametrized Remote Trigger plugin
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

Barak Korren created OVIRT-2256: ----------------------------------- Summary: Install the Parametrized Remote Trigger plugin Key: OVIRT-2256 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2256 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Jenkins Master Reporter: Barak Korren Assignee: infra Please install the [Parametrized Remote Trigger|https://plugins.jenkins.io/Parameterized-Remote-Trigger] plugin so we can use it to trigger jobs in remote Jenkins instances. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

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

26 Jun '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: 278 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #278 [Sandro Bonazzola] yum-repos: master: adjusted for new packages ----------------- Failed Tests: ----------------- All tests passed

1 1

[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: -------------------------------- Issue Type: New Feature (was: Bug) > Create slave borrowing flow > --------------------------- > > Key: OVIRT-2254 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2254 > Project: oVirt - virtualization made easy > Issue Type: New Feature > 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-2255) build aborted on time out
by Dafna Ron (oVirt JIRA) 26 Jun '18

26 Jun '18

Dafna Ron created OVIRT-2255: -------------------------------- Summary: build aborted on time out Key: OVIRT-2255 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2255 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra We had a test aborted which seemed to have been on time out. Build was aborted: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8350/ I can see it was a timeout: Timeout has been exceeded sigterm was sent by lago: '+ logger.success 'Cleanup done' + logger.log SUCCESS 'Cleanup done' + set +x run_suite.sh::env_cleanup::SUCCESS:: Cleanup done + exit 0 + exit Sending interrupt signal to process sh: line 1: 47038 Terminated JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests(a)tmp/durable-c13ed13b/script.sh' > '/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests(a)tmp/durable-c13ed13b/jenkins-log.txt' 2>&1 After 10s process did not stop' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

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

26 Jun '18

Barak Korren created OVIRT-2254: ----------------------------------- Summary: 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-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) 25 Jun '18

25 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) 25 Jun '18

25 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) 25 Jun '18

25 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) 25 Jun '18

25 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