[ https://ovirt-jira.atlassian.net/browse/OVIRT-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39148#comment-39148 ] Eyal Edri commented on OVIRT-2252: ---------------------------------- Can we drop it from staging? its best to have one working slave on production and if we really need it on staging, we can ask for one more

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#100099)