- Infra - oVirt List Archives

[JIRA] (OVIRT-2367) Functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback
by Maor Lipchuk (oVirt JIRA) 24 Jul '18

24 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2367?page=com.atlassian.jira.… ] Maor Lipchuk commented on OVIRT-2367: ------------------------------------- The funtional tests which I want to add is related to the disaster recovery scenario, it is not directly related to storage but to the whole setup. We want to check whether the recovery for the primary setup went well and the secondary setup recovered successfully. For doing that we need the OST to support two engines and after that we can start to write functional tests for it What is the difference between the QE functional tests and the OST functional tests. If you think it is the QE responsibility which ticket should I open for it? > Functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2367 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2367 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Maor Lipchuk > Assignee: infra > Priority: High > > RHV/oVirt should support functional tests for the disaster recovery feature which was introduced in oVirt/RHV 4.2 > The functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback between the different setups. > Here are more resources explaining about the feature and the its usecases: > github project: > https://github.com/oVirt/ovirt-ansible-disaster-recovery/ > Documentation: > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht… > Videos demostrating the usecases for oVirt DR: > https://www.youtube.com/watch?v=_TVhU9Sf2uc > https://www.youtube.com/watch?v=uRxsZME6fGs > https://www.youtube.com/watch?v=7dStBp7Wpo0 > https://www.youtube.com/watch?v=a44PdFbeIfE > https://youtu.be/ayYrV5IBFUg > https://www.youtube.com/watch?v=rt31-XJ45So&t=8s > [~gbenhaim(a)redhat.com] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2367) Functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback
by Dafna Ron (oVirt JIRA) 24 Jul '18

24 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2367?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2367: ---------------------------------- I also think that those sort of tests should be done by QE and not in CI testing. > Functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2367 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2367 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Maor Lipchuk > Assignee: infra > Priority: High > > RHV/oVirt should support functional tests for the disaster recovery feature which was introduced in oVirt/RHV 4.2 > The functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback between the different setups. > Here are more resources explaining about the feature and the its usecases: > github project: > https://github.com/oVirt/ovirt-ansible-disaster-recovery/ > Documentation: > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht… > Videos demostrating the usecases for oVirt DR: > https://www.youtube.com/watch?v=_TVhU9Sf2uc > https://www.youtube.com/watch?v=uRxsZME6fGs > https://www.youtube.com/watch?v=7dStBp7Wpo0 > https://www.youtube.com/watch?v=a44PdFbeIfE > https://youtu.be/ayYrV5IBFUg > https://www.youtube.com/watch?v=rt31-XJ45So&t=8s > [~gbenhaim(a)redhat.com] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.0-suite-master - Build # 2 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 Jul '18

24 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.0-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.0-suite-master/2/ Build Number: 2 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #2 [Lev Veyde] 004_basic_sanity.py cleanup ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.preview_snapshot_with_memory_40 Error Message: False != True after 600 seconds Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 78, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/workspace/ovirt-system-tests_compat-4.0-suite-master/ovirt-system-tests/compat-4.0-suite-master/test-scenarios/004_basic_sanity.py", line 431, in preview_snapshot_with_memory pass File "/usr/lib64/python2.7/contextlib.py", line 24, in __exit__ self.gen.next() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.0-suite-master/ovirt-system-tests/compat-4.0-suite-master/test_utils/__init__.py", line 264, in TestEvent lambda: File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 271, in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 258, in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 237, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) AssertionError: False != True after 600 seconds

1 4

[JIRA] (OVIRT-2367) Functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback
by Eyal Edri (oVirt JIRA) 24 Jul '18

24 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2367?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2367: ---------------------------------- Hi [~mlipchuk(a)redhat.com] I'm not sure what is the expectation here from the infra team, Do you need help in setting a new storage suite in OST or you're planning to write tests as part of the project check-pr job? > Functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2367 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2367 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Maor Lipchuk > Assignee: infra > Priority: High > > RHV/oVirt should support functional tests for the disaster recovery feature which was introduced in oVirt/RHV 4.2 > The functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback between the different setups. > Here are more resources explaining about the feature and the its usecases: > github project: > https://github.com/oVirt/ovirt-ansible-disaster-recovery/ > Documentation: > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht… > Videos demostrating the usecases for oVirt DR: > https://www.youtube.com/watch?v=_TVhU9Sf2uc > https://www.youtube.com/watch?v=uRxsZME6fGs > https://www.youtube.com/watch?v=7dStBp7Wpo0 > https://www.youtube.com/watch?v=a44PdFbeIfE > https://youtu.be/ayYrV5IBFUg > https://www.youtube.com/watch?v=rt31-XJ45So&t=8s > [~gbenhaim(a)redhat.com] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2363) 008_basic_ui_sanity.start_grid failure with error "[Errno 2] No such file or directory"
by Shirly Radco (oVirt JIRA) 24 Jul '18

24 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2363?page=com.atlassian.jira.… ] Shirly Radco commented on OVIRT-2363: ------------------------------------- Fluentd is not related to mom. > 008_basic_ui_sanity.start_grid failure with error "[Errno 2] No such file or directory" > --------------------------------------------------------------------------------------- > > Key: OVIRT-2363 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2363 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > patch that failed is: https://gerrit.ovirt.org/#/c/92882/ - core: hotplug new disk only if VM is up or paused states > I don't think the patch causes a regression but I am looking at the logs and checking to see if there was a behavior change which caused the ost test itself to fail. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2363) 008_basic_ui_sanity.start_grid failure with error "[Errno 2] No such file or directory"
by Dafna Ron (oVirt JIRA) 24 Jul '18

24 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2363?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2363: ---------------------------------- [~sradco(a)redhat.com] [~ybardavi] [~msivak(a)redhat.com] Martin Perina 1:59 PM (19 hours ago) to Yedidyah, Shirly, Martin, me, devel, infra Hi, I can see in vdsm.log that it received a kill signal: 2018-07-23 05:24:26,735-0400 INFO (MainThread) [vds] Received signal 15, shutting down (vdsmd:68) And in /var/log/messages I found that mom was killed: Jul 23 05:24:16 lago-basic-suite-master-host-1 systemd: Stopping MOM instance configured for VDSM purposes... ... Jul 23 05:24:26 lago-basic-suite-master-host-1 systemd: mom-vdsm.service stop-sigterm timed out. Killing. Jul 23 05:24:26 lago-basic-suite-master-host-1 systemd: mom-vdsm.service: main process exited, code=killed, status=9/KILL Jul 23 05:24:26 lago-basic-suite-master-host-1 systemd: Stopped MOM instance configured for VDSM purposes. Jul 23 05:24:26 lago-basic-suite-master-host-1 systemd: Unit mom-vdsm.service entered failed state. Jul 23 05:24:26 lago-basic-suite-master-host-1 systemd: mom-vdsm.service failed. So Didi/Shirly/Martin can fluentd error be related to mom shutdown? And could this be a cause of VDSM shutdown? > 008_basic_ui_sanity.start_grid failure with error "[Errno 2] No such file or directory" > --------------------------------------------------------------------------------------- > > Key: OVIRT-2363 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2363 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > patch that failed is: https://gerrit.ovirt.org/#/c/92882/ - core: hotplug new disk only if VM is up or paused states > I don't think the patch causes a regression but I am looking at the logs and checking to see if there was a behavior change which caused the ost test itself to fail. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2168) Show build artifacts as soon as they are created in STDCI build summary
by Barak Korren (oVirt JIRA) 24 Jul '18

24 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2168?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2168: ----------------------------------- Assignee: Barak Korren (was: infra) > Show build artifacts as soon as they are created in STDCI build summary > ----------------------------------------------------------------------- > > Key: OVIRT-2168 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2168 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines), STDCI Build Report > Reporter: Daniel Belenky > Assignee: Barak Korren > > As an STDCI user, I want to have access to build artifacts as soon as possible in order to access different logs and outputs of my code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2367) Functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback
by Maor Lipchuk (oVirt JIRA) 24 Jul '18

24 Jul '18

Maor Lipchuk created OVIRT-2367: ----------------------------------- Summary: Functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback Key: OVIRT-2367 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2367 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Maor Lipchuk Assignee: infra Priority: High RHV/oVirt should support functional tests for the disaster recovery feature which was introduced in oVirt/RHV 4.2 The functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback between the different setups. Here are more resources explaining about the feature and the its usecases: github project: https://github.com/oVirt/ovirt-ansible-disaster-recovery/ Documentation: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht… Videos demostrating the usecases for oVirt DR: https://www.youtube.com/watch?v=_TVhU9Sf2uc https://www.youtube.com/watch?v=uRxsZME6fGs https://www.youtube.com/watch?v=7dStBp7Wpo0 https://www.youtube.com/watch?v=a44PdFbeIfE https://youtu.be/ayYrV5IBFUg https://www.youtube.com/watch?v=rt31-XJ45So&t=8s [~gbenhaim(a)redhat.com] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2364) STDCI containers should register themselves as agents
by Barak Korren (oVirt JIRA) 24 Jul '18

24 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2364?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2364: ------------------------------------- The ticket title is a bit misleading as it seems to imply that each container will require access to credentials to register itself. Having run_stdci_containers.sh do it will require it to have crediatials as well, which probably also not the best approach. I think long-term the best approach will be to have the slave allocation flow in jenkins create the node objects and then setup the containers on the physical host. > STDCI containers should register themselves as agents > ----------------------------------------------------- > > Key: OVIRT-2364 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2364 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > Instead of manually setting up an agent from Jenkins GUI, run_stdci_containers.sh should register them automatically. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2366) Look at the Jenkins "configuration-as-code" plugin to automate more configuraiton
by Barak Korren (oVirt JIRA) 24 Jul '18

24 Jul '18

Barak Korren created OVIRT-2366: ----------------------------------- Summary: Look at the Jenkins "configuration-as-code" plugin to automate more configuraiton Key: OVIRT-2366 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2366 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Jenkins Master Reporter: Barak Korren Assignee: infra While JJB does a lot of cinfiguration for us, its limited to job and view configuration, the [configuration-as-code plugin|https://github.com/jenkinsci/configuration-as-code-plugin] may be able to allow us to configura more aspects of Jenkins automatically. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0