November 2019 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2830) Create an infra user for Krapali

by Evgheni Dereveanchin (oVirt JIRA)

Evgheni Dereveanchin created OVIRT-2830: ------------------------------------------- Summary: Create an infra user for Krapali Key: OVIRT-2830 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2830 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Krapali is the new team member so an infra user needs to be created -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

5 years, 1 month

1
0
0 / 0

[JIRA] (OST-137) OST: test for host being in up state should have retries

by Anton Marchukov (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OST-137?page=com.atlassian.jira.p... ] Anton Marchukov reassigned OST-137: ----------------------------------- Assignee: Anton Marchukov (was: infra) > OST: test for host being in up state should have retries > -------------------------------------------------------- > > Key: OST-137 > URL: https://ovirt-jira.atlassian.net/browse/OST-137 > Project: oVirt system tests > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: Anton Marchukov > > When host goes up after installation, it first goes up, then it falls back into (iirc) unknown state, then it goes up for good. > This confuses multiple tests that require host to be up (e.g. add storage domain), which wait for at least one host being up, and when they get past the condition, meanwhile host falls back to the unknown state, so following operation which requires host to be up fails. Then it tries fencing, but it cannot start fencing since there is no up host at the moment, which issues more errors... > It's same pattern in all such failure, i will paste console output & link to job next time i'll see this. > The resolution would be to wait if the host is REALLY up, so e.g. ask if it's up, wait a bit, ask again and if it's up both times, continue with operation. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

5 years, 1 month

1
0
0 / 0

[JIRA] (OST-137) OST: test for host being in up state should have retries

by Dusan Fodor (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OST-137?page=com.atlassian.jira.p... ] Dusan Fodor moved OVIRT-2821 to OST-137: ---------------------------------------- Components: (was: OST) Project: oVirt system tests (was: oVirt - virtualization made easy) Workflow: Workflow for Project OST (was: Task Management Workflow) Key: OST-137 (was: OVIRT-2821) > OST: test for host being in up state should have retries > -------------------------------------------------------- > > Key: OST-137 > URL: https://ovirt-jira.atlassian.net/browse/OST-137 > Project: oVirt system tests > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > > When host goes up after installation, it first goes up, then it falls back into (iirc) unknown state, then it goes up for good. > This confuses multiple tests that require host to be up (e.g. add storage domain), which wait for at least one host being up, and when they get past the condition, meanwhile host falls back to the unknown state, so following operation which requires host to be up fails. Then it tries fencing, but it cannot start fencing since there is no up host at the moment, which issues more errors... > It's same pattern in all such failure, i will paste console output & link to job next time i'll see this. > The resolution would be to wait if the host is REALLY up, so e.g. ask if it's up, wait a bit, ask again and if it's up both times, continue with operation. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

5 years, 1 month

1
0
0 / 0

[CQ]: 104534, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change 104534,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104040,10 (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 104040,10 (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/104534/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104040/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16878/

5 years, 1 month

1
0
0 / 0

[CQ]: 6ef3445 (ovirt-ansible-vm-infra) failed "ovirt-4.3" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-4.3" change queue including change 6ef3445 (ovirt-ansible-vm-infra) failed. However, this change seems not to be the root cause for this failure. Change 4e4aca6 (ovirt-ansible-vm-infra) 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 4e4aca6 (ovirt-ansible-vm- infra) 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://github.com/oVirt/ovirt-ansible-vm-infra/commit/6ef34455c9ca610884... For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-vm-infra/commit/4e4aca6f3c3b2f124d... For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2454/

5 years, 1 month

1
0
0 / 0

[CQ]: 4aa656b (ovirt-ansible-vm-infra) failed "ovirt-4.3" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-4.3" change queue including change 4aa656b (ovirt-ansible-vm-infra) failed. However, this change seems not to be the root cause for this failure. Change 4e4aca6 (ovirt-ansible-vm-infra) 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 4e4aca6 (ovirt-ansible-vm- infra) 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://github.com/oVirt/ovirt-ansible-vm-infra/commit/4aa656b17752ff4fee... For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-vm-infra/commit/4e4aca6f3c3b2f124d... For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2452/

5 years, 1 month

1
0
0 / 0

[JIRA] (OVIRT-2829) gmail can't verify emails sent from ovirt.org

by Anton Marchukov (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2829?page=com.atlassian.jir... ] Anton Marchukov reassigned OVIRT-2829: -------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > gmail can't verify emails sent from ovirt.org > --------------------------------------------- > > Key: OVIRT-2829 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2829 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Emil Natan > Assignee: Evgheni Dereveanchin > > It seems like something that started in the last few days, I see Gmail > marks email sent from gerrit.ovirt.org with "?" saying it could not verify > the emails are sent from ovirt.org domain. It could be related to bad SPF > record. > From the email header: Received-SPF: softfail (google.com: domain of > transitioning gerrit(a)ovirt.org does not designate 66.187.233.88 as > permitted sender) client-ip=66.187.233.88; > -- > Emil Natan > RHV/CNV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

5 years, 1 month

1
0
0 / 0

[JIRA] (OVIRT-2829) gmail can't verify emails sent from ovirt.org

by Emil Natan (oVirt JIRA)

Emil Natan created OVIRT-2829: --------------------------------- Summary: gmail can't verify emails sent from ovirt.org Key: OVIRT-2829 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2829 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Emil Natan Assignee: infra It seems like something that started in the last few days, I see Gmail marks email sent from gerrit.ovirt.org with "?" saying it could not verify the emails are sent from ovirt.org domain. It could be related to bad SPF record. From the email header: Received-SPF: softfail (google.com: domain of transitioning gerrit(a)ovirt.org does not designate 66.187.233.88 as permitted sender) client-ip=66.187.233.88; -- Emil Natan RHV/CNV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

5 years, 1 month

1
0
0 / 0

[CQ]: 104579,2 (ovirt-release) failed "ovirt-master" system tests

by oVirt Jenkins

Change 104579,2 (ovirt-release) 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/104579/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16873/

5 years, 1 month

1
0
0 / 0

[CQ]: 104196, 6 (ovirt-engine-api-model) failed "ovirt-master" system tests

by oVirt Jenkins

Change 104196,6 (ovirt-engine-api-model) 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/104196/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16868/

5 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra November 2019