[
https://ovirt-jira.atlassian.net/browse/OVIRT-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39149#comment-39149
]
Barak Korren commented on OVIRT-2252:
-------------------------------------
we cannot, because of the way stdciv2 works, if we drop the slave, the jobs for
the 'jenkins' repo will never finish.
I wouldn't want to just drop the 'jenkins' repo jobs, because that is the only
way we have ATM to pre-test some things.
I think at this point the solution we should aim for is to containerize the
s390x host, that would resolve this issue and would enable us to drop support
for not-containerized hosts in the future. I actually had a chat with the
host's maintainer a while ago, and he was willing to install docker there. The
intiative died out because I did not have time to push it further.
> 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)
_______________________________________________
Infra mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/44Q6QHOXI4J4A4I7GZZQGN4TAWQ6AK7V/
