[ https://ovirt-jira.atlassian.net/browse/OVIRT-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38382#comment-38382 ] Barak Korren commented on OVIRT-2594: ------------------------------------- This looks like a very old known issue - this happens when someone sets up a slave when the {{jenkins}} UID/GID are 1000. [~eedri], [~ena@redhat.com] - this seems to be all happenning on the fc27 slaves you brought up, I guess now we know why they were down in the 1st place... [~nsoffer@redhat.com] WRT your 2nd issue - we actually have fixes for that where possible - but not in STDCI V1... The code structure of STDCI V1 makes this close to impossible to do there... But for this particular issue, its not really possible to tell the difference because the failure is occurring in the innermost {{mock}} invocation that is launching your script...

Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run ---------------------------------------------------------------------

Key: OVIRT-2594 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2594 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra

I have seen this issue in the recent days several times. Here are some examples: - https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/conso... - https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/conso... - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console - https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/conso... There are too issues: - No test ran, so we need to retrigger manually - Gerrit report build FAILURE instead of build ERROR I reported the second issue many times in the last 5 years, no progress yet. Nir

-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)