January 2020 - Infra - oVirt List Archives

[JIRA] (OVIRT-1707) The infra docs index page needs a face lift
by Evgheni Dereveanchin (oVirt JIRA) 15 Jan '20

15 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1707?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1707: ------------------------------------------- Assignee: Krapali Rai (was: infra) > The infra docs index page needs a face lift > ------------------------------------------- > > Key: OVIRT-1707 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1707 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: General > Reporter: Barak Korren > Assignee: Krapali Rai > Priority: High > Labels: documentation, first_time_task > > The infra-docs index page is the first page about the oVirt infra team that anyone will see, but it looks bad. Here are a few issues with it: > # The page title was probably auto-generated by GitHub and looks wrong > # The page contains no text. There needs to be some short 2-3 line explanation about what is this page and what could be found in it. The sub sections should probably also include 1-2 lines each about which documents can be found in them. > # Some links have opaque non-descriptive text. For example "Communication" should probably be "Communicating with the oVirt infra team". > # The documents and sections are listed in semi-random order. Instead, they should be ordered in such a way that the more important public-facing documents are closer to the top > # The "general" section is just a random collection of things. It should probably be split apart into more specific sections like "Gerrit", "Contribution guidelines" and "Procedures for infra-team members". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2252) The s390x slave is used in parallel by both the staging and the production CI systems
by Evgheni Dereveanchin (oVirt JIRA) 15 Jan '20

15 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2252?page=com.atlassian.jira.… ] 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. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2337) Ensure emergency access to PHX production VMs
by Evgheni Dereveanchin (oVirt JIRA) 15 Jan '20

15 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2337?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2337: ------------------------------------------- Assignee: Krapali Rai (was: infra) > Ensure emergency access to PHX production VMs > --------------------------------------------- > > Key: OVIRT-2337 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2337 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: oVirt Infra > Reporter: Barak Korren > Assignee: Krapali Rai > Priority: High > > Make sure that in case of malfunction we have multiple fail-safe ways of gaining access to the PHX production VMs to resolve issues. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[CQ]: d3bd33b (ovirt-ansible-shutdown-env) failed "ovirt-4.3" system tests
by oVirt Jenkins 15 Jan '20

15 Jan '20

Change d3bd33b (ovirt-ansible-shutdown-env) is probably the reason behind recent system test failures in the "ovirt-4.3" 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://github.com/oVirt/ovirt-ansible-shutdown-env/commit/d3bd33b8a02df36a… For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2813/

1 0

[CQ]: 105983, 26 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '20

15 Jan '20

A system test invoked by the "ovirt-master" change queue including change 105983,26 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106134,5 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106134,5 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/105983/26 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106134/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18048/

1 0

[CQ]: 104521, 16 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '20

15 Jan '20

A system test invoked by the "ovirt-4.3" change queue including change 104521,16 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106120,5 (ovirt-system-tests) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106120,5 (ovirt-system-tests) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/104521/16 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106120/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2809/

1 0

[oVirt Jenkins] deploy-to-gated-ovirt-4.3 - Build #128 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 15 Jan '20

15 Jan '20

Build: https://jenkins.ovirt.org/job/deploy-to-gated-ovirt-4.3/128/ Build Name: #128 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 9

[CQ]: 106321, 2 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '20

15 Jan '20

A system test invoked by the "ovirt-4.3" change queue including change 106321,2 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106120,5 (ovirt-system-tests) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106120,5 (ovirt-system-tests) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106321/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106120/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2807/

1 0

[CQ]: 106320, 1 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '20

15 Jan '20

A system test invoked by the "ovirt-4.3" change queue including change 106320,1 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106120,5 (ovirt-system-tests) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106120,5 (ovirt-system-tests) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106320/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106120/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2806/

1 0

[CQ]: 106211, 1 (ovirt-engine-sdk-java) failed "ovirt-master" system tests
by oVirt Jenkins 15 Jan '20

15 Jan '20

Change 106211,1 (ovirt-engine-sdk-java) is probably the reason behind recent system test failures in the "ovirt-master" 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/106211/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18043/

1 0