June 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2211) Add verification that the 'mock' GID is set to a proper value

by Barak Korren (oVirt JIRA)

Barak Korren created OVIRT-2211: ----------------------------------- Summary: Add verification that the 'mock' GID is set to a proper value Key: OVIRT-2211 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2211 Project: oVirt - virtualization made easy Issue Type: Outage Components: mock_runner, Standard CI (Pipelines) Reporter: Barak Korren Assignee: infra After having encountered OVIRT-2210, we want to detect such issues sooner next time we add a new slave OS. So we want to have the CI system pre-emptively verify the 'mock' GID is set to a proper value. There are two possible places we can do this: # In the 'check-patch' sage for the 'jenkins' repo # In {{global-setup.sh}} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2210) VDSM CI failes on all new FC28 slaves becaose of the 'mock' GID

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2210?page=com.atlassian.jir... ] Evgheni Dereveanchin reassigned OVIRT-2210: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > VDSM CI failes on all new FC28 slaves becaose of the 'mock' GID > --------------------------------------------------------------- > > Key: OVIRT-2210 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2210 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: CI client projects, Jenkins Slaves > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Priority: Highest > > We see all check-patch jobs for VDSM failing when running on the new FC28 slaves, with an error like the following: > {code} > ERROR: Command failed: > # /usr/sbin/groupadd -g 1000 mock > {code} > The reason for this issue is that mock tries to have the 'mock' group have the same GID inside and outside of the mock environment. In the case of the new slaves the GID for the 'mock' group is 1000. Since 1000 is the 1st GID you get of you run 'groupadd' the probability of it colliding with any GID created by a package inside the 'mock' env is quite high. > In the case of the VDSM CI, the GID 1000 is taken by the 'openvswitch' package for the 'hugetlbfs' group. This on its own is a bug because no package should be taking GIDs beyond 1000, but having said that, the CI should not break on this, so we need to move the mock GID to below 1000 to a number that is unlikely to collide with others. > In the meantime all fc28 slaves will be disabled. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

CI fails on vdsm 4.2 branch

by Ala Hino

Something is odd ... I see that CI run only on RHEL (CentOS), but not on Fedora. Link to CI log: https://jenkins.ovirt.org/job/vdsm_4.2_check-patch-el7-x86_64/370/console... Link to patch: https://gerrit.ovirt.org/#/c/92309/

6 years, 7 months

2
4
0 / 0

[JIRA] (OVIRT-2210) VDSM CI failes on all new FC28 slaves becaose of the 'mock' GID

by Barak Korren (oVirt JIRA)

Barak Korren created OVIRT-2210: ----------------------------------- Summary: VDSM CI failes on all new FC28 slaves becaose of the 'mock' GID Key: OVIRT-2210 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2210 Project: oVirt - virtualization made easy Issue Type: Outage Components: CI client projects, Jenkins Slaves Reporter: Barak Korren Assignee: infra Priority: Highest We see all check-patch jobs for VDSM failing when running on the new FC28 slaves, with an error like the following: {code} ERROR: Command failed: # /usr/sbin/groupadd -g 1000 mock {code} The reason for this issue is that mock tries to have the 'mock' group have the same GID inside and outside of the mock environment. In the case of the new slaves the GID for the 'mock' group is 1000. Since 1000 is the 1st GID you get of you run 'groupadd' the probability of it colliding with any GID created by a package inside the 'mock' env is quite high. In the case of the VDSM CI, the GID 1000 is taken by the 'openvswitch' package for the 'hugetlbfs' group. This on its own is a bug because no package should be taking GIDs beyond 1000, but having said that, the CI should not break on this, so we need to move the mock GID to below 1000 to a number that is unlikely to collide with others. In the meantime all fc28 slaves will be disabled. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[CQ]: 92263,1 (vdsm) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 92263,1 (vdsm) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/92263/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2426/

6 years, 7 months

2
1
0 / 0

CI failing: /usr/sbin/groupadd -g 1000 mock

by Nir Soffer

2 Fedora builds failed recently with this error: 19:40:34 ERROR: Command failed: 19:40:34 # /usr/sbin/groupadd -g 1000 mock See latest builds of this patch: https://gerrit.ovirt.org/#/c/91834/ I merged the patch regardless, but please take a look. Nir

6 years, 7 months

3
3
0 / 0

[JIRA] (OVIRT-2209) Add mock version to the mock cache key

by Barak Korren (oVirt JIRA)

Barak Korren created OVIRT-2209: ----------------------------------- Summary: Add mock version to the mock cache key Key: OVIRT-2209 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2209 Project: oVirt - virtualization made easy Issue Type: Improvement Components: mock_runner Reporter: Barak Korren Assignee: infra Sometimes updates to mock make in incompatible with caches created by older versions. We should have the mock version be a part of the key used to retrieve cached mock environments. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2209) Add mock version to the mock cache key

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2209?page=com.atlassian.jir... ] Barak Korren updated OVIRT-2209: -------------------------------- Epic Link: OVIRT-2189 > Add mock version to the mock cache key > -------------------------------------- > > Key: OVIRT-2209 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2209 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > > Sometimes updates to mock make in incompatible with caches created by older versions. We should have the mock version be a part of the key used to retrieve cached mock environments. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2208) Gate package changes on FC28 slaves

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2208?page=com.atlassian.jir... ] Barak Korren reassigned OVIRT-2208: ----------------------------------- Assignee: Barak Korren (was: infra) > Gate package changes on FC28 slaves > ----------------------------------- > > Key: OVIRT-2208 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2208 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > We need to gate package changes on FC28 slaves just like we do on all other slaves. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2208) Gate package changes on FC28 slaves

by Barak Korren (oVirt JIRA)

Barak Korren created OVIRT-2208: ----------------------------------- Summary: Gate package changes on FC28 slaves Key: OVIRT-2208 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2208 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra Priority: Highest We need to gate package changes on FC28 slaves just like we do on all other slaves. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2018