- Infra - oVirt List Archives

[JIRA] (OVIRT-2212) Document the steps needed to add a new distro for CI slaves
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2212?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2212: ------------------------------------- Just so we don't forget - when we add a new distro we need to: # Create mirror sync jobs for it # Create a 'slave-repos' file in the 'jenkins' repo to force the slaves of that distro to use a particular mirror snapshot. > Document the steps needed to add a new distro for CI slaves > ----------------------------------------------------------- > > Key: OVIRT-2212 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2212 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation, Jenkins Slaves > Reporter: Evgheni Dereveanchin > Assignee: infra > > Adding a new distro/architecture to CI involves multiple steps like installing software, creating users, managing software mirrors. This process needs to be documented on ReadTheDocs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2212) Document the steps needed to add a new distro for CI slaves
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2212?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2212: -------------------------------- Component/s: Jenkins Slaves > Document the steps needed to add a new distro for CI slaves > ----------------------------------------------------------- > > Key: OVIRT-2212 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2212 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation, Jenkins Slaves > Reporter: Evgheni Dereveanchin > Assignee: infra > > Adding a new distro/architecture to CI involves multiple steps like installing software, creating users, managing software mirrors. This process needs to be documented on ReadTheDocs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2212) Document the steps needed to add a new distro for CI slaves
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2212?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2212: -------------------------------- Summary: Document the steps needed to add a new distro for CI slaves (was: Document the steps needed to add a new distro to CI) > Document the steps needed to add a new distro for CI slaves > ----------------------------------------------------------- > > Key: OVIRT-2212 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2212 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation > Reporter: Evgheni Dereveanchin > Assignee: infra > > Adding a new distro/architecture to CI involves multiple steps like installing software, creating users, managing software mirrors. This process needs to be documented on ReadTheDocs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2212) Document the steps needed to add a new distro to CI
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2212?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2212: -------------------------------- Component/s: Documentation > Document the steps needed to add a new distro to CI > --------------------------------------------------- > > Key: OVIRT-2212 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2212 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation > Reporter: Evgheni Dereveanchin > Assignee: infra > > Adding a new distro/architecture to CI involves multiple steps like installing software, creating users, managing software mirrors. This process needs to be documented on ReadTheDocs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2212) Document the steps needed to add a new distro to CI
by Evgheni Dereveanchin (oVirt JIRA) 18 Jun '18

18 Jun '18

Evgheni Dereveanchin created OVIRT-2212: ------------------------------------------- Summary: Document the steps needed to add a new distro to CI Key: OVIRT-2212 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2212 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Adding a new distro/architecture to CI involves multiple steps like installing software, creating users, managing software mirrors. This process needs to be documented on ReadTheDocs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2211) Add verification that the 'mock' GID is set to a proper value
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

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)

1 0

[JIRA] (OVIRT-2210) VDSM CI failes on all new FC28 slaves becaose of the 'mock' GID
by Evgheni Dereveanchin (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2210?page=com.atlassian.jira.… ] 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)

1 0

CI fails on vdsm 4.2 branch
by Ala Hino 18 Jun '18

18 Jun '18

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/consoleFu… Link to patch: https://gerrit.ovirt.org/#/c/92309/

2 4

[JIRA] (OVIRT-2210) VDSM CI failes on all new FC28 slaves becaose of the 'mock' GID
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

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)

1 0

[CQ]: 92263,1 (vdsm) failed "ovirt-4.2" system tests
by oVirt Jenkins 18 Jun '18

18 Jun '18

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/

2 1