- Infra - oVirt List Archives

[JIRA] (OVIRT-2202) 006_migrations.prepare_migration_attachments_ipv4 for ovirt-engine-dashboard
by Dafna Ron (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2202?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2202: ----------------------------- Labels: ost_code_regression ost_failures ost_race (was: ost_code_regression ost_failures) > 006_migrations.prepare_migration_attachments_ipv4 for ovirt-engine-dashboard > ---------------------------------------------------------------------------- > > Key: OVIRT-2202 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2202 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_code_regression, ost_failures, ost_race > > There was a failed test 006_migrations.prepare_migration_attachments_ipv4 > Error: The response content type 'text/html; charset=iso-8859-1' isn't the expected XML > Build: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8208/ > patch reported: https://gerrit.ovirt.org/#/c/92238/1 - add resolutions section to force jquery and bootstrap versions > The actual error is: Unable to process messages Broken pipe: java.io.IOException: Broken pipe > this would be the error in vdsm: > '2018-06-14 04:05:34,698-0400 ERROR (jsonrpc/5) [vds] connectivity check failed (API:1537) > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1534, in setupNetworks > supervdsm.getProxy().setupNetworks(networks, bondings, options) > File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ > return callMethod() > File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda> > **kwargs) > File "<string>", line 2, in setupNetworks > File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod > raise convert_to_error(kind, result) > ConfigNetworkError: (10, 'connectivity check failed') > 2018-06-14 04:05:34,699-0400 INFO (jsonrpc/5) [api.network] FINISH setupNetworks return={'status': {'message': 'connectivity check failed', 'code': 10}} from=::ffff:192.168.201.4,50952 (api:53) > 2018-06-14 04:05:34,699-0400 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call Host.setupNetworks failed (error 10) in 127.20 seconds (__init__:311)' > The patch may be related so I will as Greg to take a look -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2203) failure in update host caused patch to fail
by Dafna Ron (oVirt JIRA) 14 Jun '18

14 Jun '18

Dafna Ron created OVIRT-2203: -------------------------------- Summary: failure in update host caused patch to fail Key: OVIRT-2203 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2203 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra The patch failed due to failure to update the host: '2018-06-14 08:25:38,754-04 ERROR [org.ovirt.engine.core.bll.host.HostUpgradeManager] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [cb22fd71-b94d-4567-a8e4-78238868d2de] Failed to run check-update of host 'lago-basic-suite-master- host-0'' I can see that the upgrade suite also failed for not seeing repos The next metrics build succeeded successfully so there is no need to do anything I cannot be sure but I think its probably a network glitch or jenkins issue which happened during the test run. here is the info from the mail: Change 92195,2 (ovirt-engine-metrics) 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/92195/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8213/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2202) 006_migrations.prepare_migration_attachments_ipv4 for ovirt-engine-dashboard
by Dafna Ron (oVirt JIRA) 14 Jun '18

14 Jun '18

Dafna Ron created OVIRT-2202: -------------------------------- Summary: 006_migrations.prepare_migration_attachments_ipv4 for ovirt-engine-dashboard Key: OVIRT-2202 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2202 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra There was a failed test 006_migrations.prepare_migration_attachments_ipv4 Error: The response content type 'text/html; charset=iso-8859-1' isn't the expected XML Build: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8208/ patch reported: https://gerrit.ovirt.org/#/c/92238/1 - add resolutions section to force jquery and bootstrap versions The actual error is: Unable to process messages Broken pipe: java.io.IOException: Broken pipe this would be the error in vdsm: '2018-06-14 04:05:34,698-0400 ERROR (jsonrpc/5) [vds] connectivity check failed (API:1537) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1534, in setupNetworks supervdsm.getProxy().setupNetworks(networks, bondings, options) File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ return callMethod() File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda> **kwargs) File "<string>", line 2, in setupNetworks File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod raise convert_to_error(kind, result) ConfigNetworkError: (10, 'connectivity check failed') 2018-06-14 04:05:34,699-0400 INFO (jsonrpc/5) [api.network] FINISH setupNetworks return={'status': {'message': 'connectivity check failed', 'code': 10}} from=::ffff:192.168.201.4,50952 (api:53) 2018-06-14 04:05:34,699-0400 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call Host.setupNetworks failed (error 10) in 127.20 seconds (__init__:311)' The patch may be related so I will as Greg to take a look -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 478 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 Jun '18

14 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/478/ Build Number: 478 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #477 [Andrej Krejcir] HE: Test restarting HE VM Changes for Build #478 [Andrej Krejcir] HE: Test restarting HE VM ----------------- Failed Tests: ----------------- No tests ran.

1 2

[CQ]: 92195, 2 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jun '18

14 Jun '18

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

1 0

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2201: ------------------------------------- Pasting IRC transcript of me trying to understand the user story behind this {code} <sbonazzo> bkorren: maybe there are better ways, but to me this is a regression that complicates my work experience and make me rethink about the switch to v2 <bkorren> sbonazzo, my point is, that v2 gave you certain ways to do things; but we shouldn't fixate on those, if we can examine the use case and figure out ways to deliver what you really need in a more convenient way <sbonazzo> bkorren: I need an end point in jenkins pointing me to latest successfull build per branch per project * ena has quit (Ping timeout: 622 seconds) <bkorren> sbonazzo, must it be in jenkins? if I put it in resources for example? <bkorren> sbonazzo, does it need to be the build with logs , etc, or just the artifacts? <sbonazzo> bkorren: resources may be ok too. artifacts only may be ok too, including yum repodata directory <sbonazzo> bkorren: but that will make difficult to correlate the artifact to the job <bkorren> sbonazzo, another question - will an HTML page with links be enough, or would you need predictable URLs? <bkorren> sbonazzo, that begs the question about why do you need to correlate the artifact with the job? is the job just a way to get at the patch? or do you need the build logs? <sbonazzo> bkorren: predictable urls would work far better for me. about correlation, it may be needed in the only case latest successful build results older than the packages in testing, requiring an inspection on what happened <bkorren> sbonazzo, I wonder about the root cause for all these requirements, is there a certain work process here we can revisit and modify so it becomes less labor intensive and requires less data gathering and manual correlation? <bkorren> sbonazzo, in other words - is there a way to "short-circuit" these requirements and make a system that will just deliver the end result you need instead of parts you need to gather manually? <sbonazzo> bkorren: there are cases when you merge a patch and the build keeps hanging in change queue for months before landing to tested due to some reason. I want to be aware of this happening in a shorter loop so i want to check that latest build lands in tested within the day. <sbonazzo> bkorren: I also would like to be able to have a quick look to a page (up to now it was a jenkins view) showing me that master was failing while 4.2 was fine and not the other way around <bkorren> sbonazzo, again if the point is to know what landed in 'tested' when - I'll just find one or more ways to deliver that exact info back to gerrit. <bkorren> sbonazzo, when you say 'master failing' here you mean builds for master branch of a certain project, if patches from master branch of said project are passing CQ/OST or if 'ovirt master' is OK from an OST POV? <sbonazzo> bkorren: a master jenkins job failing for a certain project. not sure you can see it, but have a look at: https://jenkins.ovirt.org/user/sbonazzo/my-views/view/Failing%20by%20releas… <bkorren> sbonazzo, what is the purpose of gathering this information? I see a whole mix of things - check patch mixed with build artifats and with check merged... <sbonazzo> bkorren: getting an insight on what's failing per target <sbonazzo> bkorren: since we are not gating the builds on check-merged I need to know if we built something which is not passing check-merged <bkorren> sbonazzo, adding gatting on check-merged to CQ would be quite a low hanging fruit from me if it means you can spend less time monitoring things manually... <bkorren> sbonazzo, I gate on build-artifacts already, actually now that I think of it - v2 already gives me that... <sbonazzo> bkorren: gating will help indeed :-) not sure how RDO managed to do it on their automation, but I really like zuul <bkorren> sbonazzo, I liked zool, until I fugure how rigid was it <bkorren> sbonazzo, but I think we're talking about different things - there is pre-merge gating and post-merge gating <bkorren> sbonazzo, pre-merge gating is VERY expensive to accomplish, and while CQ was designed with that in mind - I don't think its likely we'll go there at this point; but is we say that what you want to know is that a package or a patch that reached 'testing' had passed check-merged, then as I said, we already do that in V2. * sbonazzo is now known as sbonazzo|mtg <bkorren> sbonazzo, the issue with zuul is that it just assumes infinite hardware or very cheap tests... <sbonazzo|mtg> bkorren: so all v2 built packages landing in tested are certified passing check-merged? <bkorren> sbonazzo|mtg, yes. this is a side-effect of both check-merged and build-artifacts running within the same job as opposed to different jobs; I'm surprised this did not occur to me or I would've listed it as a benefit somewhere... :) <sbonazzo|mtg> bkorren: :-D {code} > [regression] STDCI v2 doesn't distinguish jobs for different branches > --------------------------------------------------------------------- > > Key: OVIRT-2201 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > In V1 we had jobs with different name based on branches they were building. > In V2 we have single job building all branches. > As an example for imgbased: > https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBuil… > will contain randomly 4.2 or master builds. > This won't allow to filter jenkins to see which branches are failing to > build, forcing developers to check manually. > This also won't allow to check if latest build landed in tested repo > because thee build may be targeted to a different branch than the one under > check. > To me this is a regression that will make me rethink about the switching to > v2 and considering reverting to v1. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches
by sbonazzo (oVirt JIRA) 14 Jun '18

14 Jun '18

sbonazzo created OVIRT-2201: ------------------------------- Summary: [regression] STDCI v2 doesn't distinguish jobs for different branches Key: OVIRT-2201 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra In V1 we had jobs with different name based on branches they were building. In V2 we have single job building all branches. As an example for imgbased: https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBuil… will contain randomly 4.2 or master builds. This won't allow to filter jenkins to see which branches are failing to build, forcing developers to check manually. This also won't allow to check if latest build landed in tested repo because thee build may be targeted to a different branch than the one under check. To me this is a regression that will make me rethink about the switching to v2 and considering reverting to v1. -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 68 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 Jun '18

14 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/68/ Build Number: 68 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #68 [Gal Ben Haim] 4.2: Backport tests from master [Barak Korren] Fix mock_cleanup.sh trying to umount bad things [Barak Korren] Switch fabric-ovirt to STDCI v2 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_he_hosts Error Message: Adding HE hosts requires API v4. 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 "/home/jenkins/workspace/ovirt-system-tests_he-node-ng-suite-master/ovirt-system-tests/he-node-ng-suite-master/test-scenarios/002_bootstrap.py", line 360, in add_he_hosts raise RuntimeError('Adding HE hosts requires API v4.') RuntimeError: Adding HE hosts requires API v4.

1 32

[JIRA] (OVIRT-2055) failure in suspend resume vm not related to reported change - need to investigate
by Dafna Ron (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2055?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2055: ---------------------------------- I have another build that failed. https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8204/ I can see that vdsm log on node1 reports: 2018-06-14 00:39:22,368-0400 WARN (qgapoller/0) [virt.periodic.VmDispatcher] could not run <function <lambda> at 0x7fbd68314f50> on ['1c0ed9a0-3430-45fa-8b1e-dd535356e620'] (periodic:289) I am not seeing an actual issue and I will ask someone from virt team look at the logs. > failure in suspend resume vm not related to reported change - need to investigate > --------------------------------------------------------------------------------- > > Key: OVIRT-2055 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2055 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > Change 91507,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/91507/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ > I think the issue is on qemu/libvirt changed queries: > https://pastebin.com/afyeUAcT > https://pastebin.com/va20Y5Hp > checking his with vdsm people. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

Planned restart of production services
by Evgheni Dereveanchin 14 Jun '18

14 Jun '18

Hi everyone, I will be restarting several production systems within the next few hours to perform planned maintenance. The following services will be unreachable for some period of time: - gerrit.ovirt.org - code review - jenkins.ovirt.org - CI master It will not be possible to submit/review patches, clone repositories or run CI jobs during this period. I will announce you once the maintenance is complete. -- Regards, Evgheni Dereveanchin

1 2

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2200: -------------------------------- Component/s: usrc.py > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: STDCI DSL, usrc.py > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 01a6c0f (ovirt-ansible-v2v-conversion-host) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jun '18

14 Jun '18

Change 01a6c0f (ovirt-ansible-v2v-conversion-host) 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://github.com/oVirt/ovirt-ansible-v2v-conversion-host/commit/01a6c0f54… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8209/

1 0

[CQ]: 92238, 1 (ovirt-engine-dashboard) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jun '18

14 Jun '18

Change 92238,1 (ovirt-engine-dashboard) 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/92238/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8208/

1 0

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 1 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 Jun '18

14 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/1/ Build Number: 1 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- No tests ran.

1 33

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2200: ------------------------------------- Just some more thoughts about this - we could maybe solve this by "exploading" directory symlinks in our code as if they were symlinks to each and every file in the directory. That way all the other symlink handling code will just work. But we need to be careful about this, as we can have directory symlinks to directories with directory symlinks in them... > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: STDCI DSL > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2200: ------------------------------------- [~dbelenky(a)redhat.com] not sure about the priority for this, we've seen that links to directories have a tendency to become directories with links sooner or later anyway... As you say its not a very easy fix, we need to go into the symlink resolution algorithms in usrc.py and add directory support. We have other things we want to do and other bugs we're not solving so well need to consider carefully if and when we're going to solve this. In the meantime there are various workarounds that could be used... > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: STDCI DSL > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2200: -------------------------------- Component/s: STDCI DSL > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: STDCI DSL > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2200: -------------------------------- Issue Type: Bug (was: By-EMAIL) > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch
by Daniel Belenky (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2200: --------------------------------------- [~bkorren(a)redhat.com] seems like something we've saw before with the original change-resolver. The current design doesn't resolve changes when the symlink is to the containing directory rather then to the file itself. Fix shouldn't take too long but not easy also. Should we give this higher priority? > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch
by Eitan Raviv (oVirt JIRA) 14 Jun '18

14 Jun '18

Eitan Raviv created OVIRT-2200: ---------------------------------- Summary: OST network-suite-4.2 does not run in check-patch Key: OVIRT-2200 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Eitan Raviv Assignee: infra Following my conversation with Barak, we found that when a patch is pushed to OST/network-suite-master, there are tests results only for network-suite-master on check-patch job, although it is expected that network-suite-4.2 would be run as well. See for example: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ Can you guys please fix? Thanks Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2199) Set content security policy at Jenkins startup
by Daniel Belenky (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2199?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2199: ---------------------------------- Labels: jenkins standard-ci stdci-summary (was: ) > Set content security policy at Jenkins startup > ---------------------------------------------- > > Key: OVIRT-2199 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2199 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > Labels: jenkins, standard-ci, stdci-summary > > STDCI summary requires some content security policy to be set so that Jenkins won't add blocking headers to the summary HTML. > The required policy is: > {code:java} > sandbox allow-scripts; default-src 'self' https://cdnjs.cloudflare.com; img-src 'self'; style-src 'self' https://cdnjs.cloudflare.com; > {code} > Documentation can be found [here|https://wiki.jenkins.io/display/JENKINS/Configuring+Content+Security+Policy] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2199) Set content security policy at Jenkins startup
by Daniel Belenky (oVirt JIRA) 14 Jun '18

14 Jun '18

Daniel Belenky created OVIRT-2199: ------------------------------------- Summary: Set content security policy at Jenkins startup Key: OVIRT-2199 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2199 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Daniel Belenky Assignee: infra STDCI summary requires some content security policy to be set so that Jenkins won't add blocking headers to the summary HTML. The required policy is: {code:java} sandbox allow-scripts; default-src 'self' https://cdnjs.cloudflare.com; img-src 'self'; style-src 'self' https://cdnjs.cloudflare.com; {code} Documentation can be found [here|https://wiki.jenkins.io/display/JENKINS/Configuring+Content+Security+Policy] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2199) Set content security policy at Jenkins startup
by Daniel Belenky (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2199?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2199: ---------------------------------- Epic Link: OVIRT-403 > Set content security policy at Jenkins startup > ---------------------------------------------- > > Key: OVIRT-2199 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2199 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > STDCI summary requires some content security policy to be set so that Jenkins won't add blocking headers to the summary HTML. > The required policy is: > {code:java} > sandbox allow-scripts; default-src 'self' https://cdnjs.cloudflare.com; img-src 'self'; style-src 'self' https://cdnjs.cloudflare.com; > {code} > Documentation can be found [here|https://wiki.jenkins.io/display/JENKINS/Configuring+Content+Security+Policy] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1578
by jenkins＠jenkins.phx.ovirt.org 14 Jun '18

14 Jun '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1578/displ…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 6953f4671b4f06efddbd388f2ec1ea81f5ba746d (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 6953f4671b4f06efddbd388f2ec1ea81f5ba746d Commit message: "add ovirt-appliance to standard pipelines" > git rev-list --no-walk 6953f4671b4f06efddbd388f2ec1ea81f5ba746d # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins1422341312358250813.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2001) Create FAQ/Knowledge Base/HOWTO pages for STDCI
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2001?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2001: ------------------------------------- Add HOWTO run STDCI V2 jobs manually with the 'standard-manual-runner' job. > Create FAQ/Knowledge Base/HOWTO pages for STDCI > ----------------------------------------------- > > Key: OVIRT-2001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2001 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > There are many common use cases and issues in STDCI that could benefit from case/task-specific documentation. So we should have a FAQ page or a Knowledge Base about STDCI to cover these issues. > Before we can make the page we need a critical mass (at least 3) of issues and solutions, so we will use comments on this ticket to collect them as they arise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2001) Create FAQ/Knowledge Base/HOWTO pages for STDCI
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2001?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2001: ------------------------------------- Issue when 'git describe' returns the wrong tag when running from jenkins. This is because jenkins adds its own tag after cloning the source and the way around it is to use the '--match' option for git describe. > Create FAQ/Knowledge Base/HOWTO pages for STDCI > ----------------------------------------------- > > Key: OVIRT-2001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2001 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > There are many common use cases and issues in STDCI that could benefit from case/task-specific documentation. So we should have a FAQ page or a Knowledge Base about STDCI to cover these issues. > Before we can make the page we need a critical mass (at least 3) of issues and solutions, so we will use comments on this ticket to collect them as they arise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 92236, 1 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jun '18

14 Jun '18

Change 92236,1 (ovirt-engine-nodejs-modules) 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/92236/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8204/

1 0

[JIRA] (OVIRT-2001) Create FAQ/Knowledge Base/HOWTO pages for STDCI
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2001?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2001: -------------------------------- Summary: Create FAQ/Knowledge Base/HOWTO pages for STDCI (was: Create FAQ/Knowledge Base for STDCI) > Create FAQ/Knowledge Base/HOWTO pages for STDCI > ----------------------------------------------- > > Key: OVIRT-2001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2001 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > There are many common use cases and issues in STDCI that could benefit from case/task-specific documentation. So we should have a FAQ page or a Knowledge Base about STDCI to cover these issues. > Before we can make the page we need a critical mass (at least 3) of issues and solutions, so we will use comments on this ticket to collect them as they arise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 01a6c0f (ovirt-ansible-v2v-conversion-host) failed "ovirt-4.2" system tests
by oVirt Jenkins 14 Jun '18

14 Jun '18

Change 01a6c0f (ovirt-ansible-v2v-conversion-host) 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://github.com/oVirt/ovirt-ansible-v2v-conversion-host/commit/01a6c0f54… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2398/

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 31 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 Jun '18

14 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/31/ Build Number: 31 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #31 [Andrej Krejcir] HE: Test restarting HE VM [Yuval Turgeman] add ovirt-appliance to standard pipelines ----------------- Failed Tests: ----------------- All tests passed

1 2

[JIRA] (OVIRT-2198) FC28 is missing python2-six which is needed by usrc.py
by Evgheni Dereveanchin (oVirt JIRA) 13 Jun '18

13 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2198?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2198: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > FC28 is missing python2-six which is needed by usrc.py > ------------------------------------------------------ > > Key: OVIRT-2198 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2198 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: High > > There seems to be one more unlisted dependency for usrc.py - python2-six that needs to be installed before global_setup: > http://jenkins.ovirt.org/job/ovirt-master_change-queue/25059/console -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2198) FC28 is missing python2-six which is needed by usrc.py
by Evgheni Dereveanchin (oVirt JIRA) 13 Jun '18

13 Jun '18

Evgheni Dereveanchin created OVIRT-2198: ------------------------------------------- Summary: FC28 is missing python2-six which is needed by usrc.py Key: OVIRT-2198 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2198 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Priority: High There seems to be one more unlisted dependency for usrc.py - python2-six that needs to be installed before global_setup: http://jenkins.ovirt.org/job/ovirt-master_change-queue/25059/console -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2195) race in 004_basic_sanity.verify_vm_import on master CQ
by Dafna Ron (oVirt JIRA) 13 Jun '18

13 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2195?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2195: ---------------------------------- https://gerrit.ovirt.org/#/c/91361/ - storage.constants: Use REPO_DATA_CENTER instead of storage_repository the log shows no failures in migration and no Errors to suggest this patch caused any issues. It is possible that its the same cause as the first failure which is that sparsify is failing. > race in 004_basic_sanity.verify_vm_import on master CQ > ------------------------------------------------------ > > Key: OVIRT-2195 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2195 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > We have a race that causes test: 004_basic_sanity.verify_vm_import to fail > This build: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8183/ failed but there is nothing in the log to suggest that the import failed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2195) race in 004_basic_sanity.verify_vm_import on master CQ
by Barak Korren (oVirt JIRA) 13 Jun '18

13 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2195?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2195: -------------------------------- Summary: race in 004_basic_sanity.verify_vm_import on master CQ (was: race in 004_basic_sanity.verify_vm_import) > race in 004_basic_sanity.verify_vm_import on master CQ > ------------------------------------------------------ > > Key: OVIRT-2195 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2195 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > We have a race that causes test: 004_basic_sanity.verify_vm_import to fail > This build: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8183/ failed but there is nothing in the log to suggest that the import failed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2195) race in 004_basic_sanity.verify_vm_import
by Barak Korren (oVirt JIRA) 13 Jun '18

13 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2195?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2195: ------------------------------------- Which change was blamed for this? Are you sure its not related? > race in 004_basic_sanity.verify_vm_import > ----------------------------------------- > > Key: OVIRT-2195 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2195 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > We have a race that causes test: 004_basic_sanity.verify_vm_import to fail > This build: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8183/ failed but there is nothing in the log to suggest that the import failed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt CI] standard-enqueue - Build #14320 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Jun '18

13 Jun '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/14320/ Build Name: #14320 Build Description: Gerrit: 91422 - ovirt-imageio (4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91422 - title: tickets: Ticket dict argument is not optional - project: ovirt-imageio - branch: master - author: Nir Soffer <nsoffer(a)redhat.com>

1 0

[JIRA] (OVIRT-2163) Build repoman for fedora 28
by Gal Ben Haim (oVirt JIRA) 13 Jun '18

13 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2163?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2163: ------------------------------------- It works, thanks. > Build repoman for fedora 28 > --------------------------- > > Key: OVIRT-2163 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2163 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: repoman > Reporter: Gal Ben Haim > Assignee: infra > Priority: Highest > > It's needed by lago-ovirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2196) 4.2 ovirt-engine failing on cpu 002_bootstrap.update_default_cluster on basic suite: The chosen CPU is not supported
by Dafna Ron (oVirt JIRA) 13 Jun '18

13 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2196?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2196: ---------------------------------- Patch will be reverted to allow new build to pass CQ > 4.2 ovirt-engine failing on cpu 002_bootstrap.update_default_cluster on basic suite: The chosen CPU is not supported > -------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2196 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2196 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_code_regression, ost_failures > > The error is: The chosen CPU is not supported > 2018-06-13 04:19:26,203-04 WARN [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-16) [593df572-8cee-424e-a106-ff584f2f0027] Validation of action 'UpdateCluster' failed for user admin@internal-authz. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_CPU_NOT_FOUND,VAR__TYPE__CLUSTER > 2018-06-13 04:19:26,204-04 INFO [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-16) [593df572-8cee-424e-a106-ff584f2f0027] Lock freed to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}' > 2018-06-13 04:19:26,204-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-16) [593df572-8cee-424e-a106-ff584f2f0027] method: runAction, params: [UpdateCluster, ManagementNetworkOnClusterOperationParameters:{commandId='bab8f4a9-1ad6-4650-b92b-52c622fb7fd7', user='null', commandType='Unknown'}], timeElapsed: 49ms > 2018-06-13 04:19:26,208-04 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-16) [] Operation Failed: [Cannot edit Cluster. The chosen CPU is not supported.] > 2018-06-13 04:19:26,272-04 DEBUG [org.ovirt.engine.core.utils.timer.FixedDelayJobListener] (DefaultQuartzScheduler6) [] Rescheduling DEFAULT.org.ovirt.engine.core.bll.gluster.GlusterSyncJob.refreshLightWeightData#-9223372036854775795 as there is no unfired trigger. > This is caused due to this change: https://gerrit.ovirt.org/#/c/91980/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 13-06-2018 ] [ 002_bootstrap.update_default_cluster ]
by Dafna Ron 13 Jun '18

13 Jun '18

Hi, We have a failure in basic suite of ovirt-engine. Test failing is: 002_bootstrap.update_default_cluster The error is: Cannot edit Cluster. The chosen CPU is not supported This is the patch that was reported by CQ: https://gerrit.ovirt.org/#/c/91980/7 - core: fix cpu flag validation the full logs are here: https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2380/artifact/e… I opened a Jira ticket so we can track the issue: https://ovirt-jira.atlassian.net/browse/OVIRT-2196 Thanks, Dafna

2 2

[JIRA] (OVIRT-2196) 4.2 ovirt-engine failing on cpu 002_bootstrap.update_default_cluster on basic suite: The chosen CPU is not supported
by Dafna Ron (oVirt JIRA) 13 Jun '18

13 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2196?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2196: ---------------------------------- A new build was created for 4.2: https://gerrit.ovirt.org/#/c/92179/2 it was suppose to have passed but the build change is failing due to https://gerrit.ovirt.org/#/c/91980/7 A system test invoked by the "ovirt-4.2" change queue including change 92179,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91980,7 (ovirt-engine) 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 91980,7 (ovirt-engine) 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/92179/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91980/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2387/ > 4.2 ovirt-engine failing on cpu 002_bootstrap.update_default_cluster on basic suite: The chosen CPU is not supported > -------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2196 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2196 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_code_regression, ost_failures > > The error is: The chosen CPU is not supported > 2018-06-13 04:19:26,203-04 WARN [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-16) [593df572-8cee-424e-a106-ff584f2f0027] Validation of action 'UpdateCluster' failed for user admin@internal-authz. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_CPU_NOT_FOUND,VAR__TYPE__CLUSTER > 2018-06-13 04:19:26,204-04 INFO [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-16) [593df572-8cee-424e-a106-ff584f2f0027] Lock freed to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}' > 2018-06-13 04:19:26,204-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-16) [593df572-8cee-424e-a106-ff584f2f0027] method: runAction, params: [UpdateCluster, ManagementNetworkOnClusterOperationParameters:{commandId='bab8f4a9-1ad6-4650-b92b-52c622fb7fd7', user='null', commandType='Unknown'}], timeElapsed: 49ms > 2018-06-13 04:19:26,208-04 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-16) [] Operation Failed: [Cannot edit Cluster. The chosen CPU is not supported.] > 2018-06-13 04:19:26,272-04 DEBUG [org.ovirt.engine.core.utils.timer.FixedDelayJobListener] (DefaultQuartzScheduler6) [] Rescheduling DEFAULT.org.ovirt.engine.core.bll.gluster.GlusterSyncJob.refreshLightWeightData#-9223372036854775795 as there is no unfired trigger. > This is caused due to this change: https://gerrit.ovirt.org/#/c/91980/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 92179, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Jun '18

13 Jun '18

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

1 0

[JIRA] (OVIRT-2139) enforce SSL on jenkins.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 13 Jun '18

13 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2139?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2139: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > enforce SSL on jenkins.ovirt.org > -------------------------------- > > Key: OVIRT-2139 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2139 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > SSL was enabled on Jenkins with OVIRT-1471, this ticket is to transform the non-SSL virtual host into a redirect to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 92164, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Jun '18

13 Jun '18

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

1 0

[JIRA] (OVIRT-2197) ovirt-engine build-artifacts job failed due to No space left on device on the vm
by Dafna Ron (oVirt JIRA) 13 Jun '18

13 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2197?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2197: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > ovirt-engine build-artifacts job failed due to No space left on device on the vm > -------------------------------------------------------------------------------- > > Key: OVIRT-2197 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2197 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_build-arifacts, ost_failures, ost_infra > > A patch failed to run on CQ because of failed build-artifacts job. > the error was: > '08:13:09 [EnvInject] - Variables injected successfully. > 08:13:09 [EnvInject] - Injecting contributions. > 08:13:09 Building remotely on vm0092.workers-phx.ovirt.org (libvirt el7 phx nested) in workspace /home/jenkins/workspace/ovirt-engine_master_build-artifacts-el7-x86_64 > 08:13:09 [ssh-agent] Looking for ssh-agent implementation... > 08:13:09 [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) > 08:13:09 $ ssh-agent > 08:13:09 [ssh-agent] Java/JNR ssh-agent > 08:13:10 ERROR: [ssh-agent] Could not register BouncyCastle on the remote agent. > 08:13:10 java.nio.file.FileSystemException: /tmp/resource-673894941857540110: No space left on device > 08:13:10 at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91) > 08:13:10 at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) > 08:13:10 at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)' > Evgheni looked at the vm and the df seems to be ok now so the cleanup jobs helped. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2197) ovirt-engine build-artifacts job failed due to No space left on device on the vm
by Dafna Ron (oVirt JIRA) 13 Jun '18

13 Jun '18

Dafna Ron created OVIRT-2197: -------------------------------- Summary: ovirt-engine build-artifacts job failed due to No space left on device on the vm Key: OVIRT-2197 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2197 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra A patch failed to run on CQ because of failed build-artifacts job. the error was: '08:13:09 [EnvInject] - Variables injected successfully. 08:13:09 [EnvInject] - Injecting contributions. 08:13:09 Building remotely on vm0092.workers-phx.ovirt.org (libvirt el7 phx nested) in workspace /home/jenkins/workspace/ovirt-engine_master_build-artifacts-el7-x86_64 08:13:09 [ssh-agent] Looking for ssh-agent implementation... 08:13:09 [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) 08:13:09 $ ssh-agent 08:13:09 [ssh-agent] Java/JNR ssh-agent 08:13:10 ERROR: [ssh-agent] Could not register BouncyCastle on the remote agent. 08:13:10 java.nio.file.FileSystemException: /tmp/resource-673894941857540110: No space left on device 08:13:10 at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91) 08:13:10 at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) 08:13:10 at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)' Evgheni looked at the vm and the df seems to be ok now so the cleanup jobs helped. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2196) 4.2 ovirt-engine failing on cpu 002_bootstrap.update_default_cluster on basic suite: The chosen CPU is not supported
by Dafna Ron (oVirt JIRA) 13 Jun '18

13 Jun '18

Dafna Ron created OVIRT-2196: -------------------------------- Summary: 4.2 ovirt-engine failing on cpu 002_bootstrap.update_default_cluster on basic suite: The chosen CPU is not supported Key: OVIRT-2196 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2196 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra The error is: The chosen CPU is not supported 2018-06-13 04:19:26,203-04 WARN [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-16) [593df572-8cee-424e-a106-ff584f2f0027] Validation of action 'UpdateCluster' failed for user admin@internal-authz. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_CPU_NOT_FOUND,VAR__TYPE__CLUSTER 2018-06-13 04:19:26,204-04 INFO [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-16) [593df572-8cee-424e-a106-ff584f2f0027] Lock freed to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}' 2018-06-13 04:19:26,204-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-16) [593df572-8cee-424e-a106-ff584f2f0027] method: runAction, params: [UpdateCluster, ManagementNetworkOnClusterOperationParameters:{commandId='bab8f4a9-1ad6-4650-b92b-52c622fb7fd7', user='null', commandType='Unknown'}], timeElapsed: 49ms 2018-06-13 04:19:26,208-04 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-16) [] Operation Failed: [Cannot edit Cluster. The chosen CPU is not supported.] 2018-06-13 04:19:26,272-04 DEBUG [org.ovirt.engine.core.utils.timer.FixedDelayJobListener] (DefaultQuartzScheduler6) [] Rescheduling DEFAULT.org.ovirt.engine.core.bll.gluster.GlusterSyncJob.refreshLightWeightData#-9223372036854775795 as there is no unfired trigger. This is caused due to this change: https://gerrit.ovirt.org/#/c/91980/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 91730,10 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 13 Jun '18

13 Jun '18

Change 91730,10 (ovirt-engine) 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/91730/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8191/

1 0

[CQ]: 92158, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Jun '18

13 Jun '18

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

1 0

[JIRA] (OVIRT-2195) race in 004_basic_sanity.verify_vm_import
by Dafna Ron (oVirt JIRA) 13 Jun '18

13 Jun '18

Dafna Ron created OVIRT-2195: -------------------------------- Summary: race in 004_basic_sanity.verify_vm_import Key: OVIRT-2195 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2195 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra We have a race that causes test: 004_basic_sanity.verify_vm_import to fail This build: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8183/ failed but there is nothing in the log to suggest that the import failed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 255 - Failure!
by jenkins＠jenkins.phx.ovirt.org 13 Jun '18

13 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/255/ Build Number: 255 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #255 [Andrej Krejcir] HE: Test restarting HE VM ----------------- Failed Tests: ----------------- No tests ran.

1 2