]
Evgheni Dereveanchin commented on OVIRT-2252:
---------------------------------------------
we have dedicated s390x VMs for Staging and production now. Is this still an issue?
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.