April 2018 - Infra - oVirt List Archives

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 289 - Failure!
by jenkins＠jenkins.phx.ovirt.org 03 Apr '18

03 Apr '18

------=_Part_941_414738129.1522589154973 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/289/ Build Number: 289 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #289 [Eitan Raviv] network: macpool: test disallowing dups while dups exist [Daniel Belenky] docker cleanup:Fix edge case for unamed containers [Daniel Belenky] nested_config: Count nesting level of options [Daniel Belenky] Introduce conditional execution in STDCI DSL [Daniel Belenky] Add OST STDCI V2 jobs ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.snapshot_merge Error Message: status: 409 reason: Conflict detail: Cannot remove Snapshot. Snapshot is currently being created for VM vm0. 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 68, in wrapper return func(prefix.virt_env.engine_vm().get_api(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-master/ovirt-system-tests/he-basic-suite-master/test-scenarios/004_basic_sanity.py", line 187, in snapshot_merge api.vms.get(VM0_NAME).snapshots.list()[-2].delete() File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 34001, in delete headers={"Correlation-Id":correlation_id,"Content-type":None} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 57, in delete return self.request('DELETE', url, body, headers, cls=cls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request persistent_auth=self.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body) RequestError: status: 409 reason: Conflict detail: Cannot remove Snapshot. Snapshot is currently being created for VM vm0. ------=_Part_941_414738129.1522589154973--

1 6

[CQ]: 89628, 2 (ovirt-guest-agent) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Apr '18

03 Apr '18

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

1 0

[CQ]: 89748,1 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 03 Apr '18

03 Apr '18

Change 89748,1 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/89748/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1523/

2 1

[JIRA] (OVIRT-1960) Make pusehr.py able to push Git tags
by Barak Korren (oVirt JIRA) 03 Apr '18

03 Apr '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1960?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1960: -------------------------------- Description: {{pusher.py}} knows how to push patches into remote SCMs. WE should also add functionality for pushing tags. More specifically: # It should be possible to request that and arbitrary tag for HEAD be created and pushed. This should make it possible to implement OVIRT-1717 # It should be possible to create and push a tag with information that is gathered and created by {{usrc.py}}. This is a counterpart to OVIRT-1959 was: {{pusher.py}} knows how to push patches into remote SCMs. WE should also add functionality for pushing tags. More specifically: # It should be possible to request that and arbitrary tag for HEAD be created and pushed. This should make it possible to implement OVRT-1717 # It should be possible to create and push a tag with information that is gathered and created by {{usrc.py}}. This is a counterpart to OVIRT-1959 > Make pusehr.py able to push Git tags > ------------------------------------ > > Key: OVIRT-1960 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1960 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[JIRA] (OVIRT-1960) Make pusehr.py able to push Git tags
by Barak Korren (oVirt JIRA) 03 Apr '18

03 Apr '18

This is a multi-part message in MIME format... ------------=_1522755723-27694-326 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1960?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1960: -------------------------------- Description: {{pusher.py}} knows how to push patches into remote SCMs. WE should also add functionality for pushing tags. More specifically: # It should be possible to request that and arbitrary tag for HEAD be created and pushed. This should make it possible to implement OVRT-1717 # It should be possible to create and push a tag with information that is gathered and created by {{usrc.py}}. This is a counterpart to OVIRT-1959 was: {{pusher.py}} knows how to push patches into remote SCMs. WE should also add functionality for pushing tags. More specifically: # It should be possible to request that and arbitrary tag for HEAD be created and pushed. # It should be possible to create and push a tag with information that is gathered and created by {{usrc.py}}. This is a counterpart to OVIRT-1959 > Make pusehr.py able to push Git tags > ------------------------------------ > > Key: OVIRT-1960 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1960 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ------------=_1522755723-27694-326 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1960?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1960:</h3> <pre>Description:</pre> <p>{{pusher.py}} knows how to push patches into remote SCMs. WE should also add functionality for pushing tags. More specifically: # It should be possible to request that and arbitrary tag for HEAD be created and pushed. This should make it possible to implement OVRT-1717 # It should be possible to create and push a tag with information that is gathered and created by {{usrc.py}}. This is a counterpart to OVIRT-1959</p> <pre>was:</pre> <p>{{pusher.py}} knows how to push patches into remote SCMs. WE should also add functionality for pushing tags. More specifically: # It should be possible to request that and arbitrary tag for HEAD be created and pushed. # It should be possible to create and push a tag with information that is gathered and created by {{usrc.py}}. This is a counterpart to OVIRT-1959</p> <blockquote><h3>Make pusehr.py able to push Git tags</h3> <pre> Key: OVIRT-1960 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1960 Project: oVirt - virtualization made easy Issue Type: Improvement Components: pusher.py Reporter: Barak Korren Assignee: infra</pre></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1522755723-27694-326--

1 0

[JIRA] (OVIRT-1960) Make pusehr.py able to push Git tags
by Barak Korren (oVirt JIRA) 03 Apr '18

03 Apr '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1960?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1960: -------------------------------- Epic Link: OVIRT-400 > Make pusehr.py able to push Git tags > ------------------------------------ > > Key: OVIRT-1960 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1960 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[JIRA] (OVIRT-1960) Make pusehr.py able to push Git tags
by Barak Korren (oVirt JIRA) 03 Apr '18

03 Apr '18

This is a multi-part message in MIME format... ------------=_1522755543-10296-283 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1960: ----------------------------------- Summary: Make pusehr.py able to push Git tags Key: OVIRT-1960 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1960 Project: oVirt - virtualization made easy Issue Type: Improvement Components: pusher.py Reporter: Barak Korren Assignee: infra {{pusher.py}} knows how to push patches into remote SCMs. WE should also add functionality for pushing tags. More specifically: # It should be possible to request that and arbitrary tag for HEAD be created and pushed. # It should be possible to create and push a tag with information that is gathered and created by {{usrc.py}}. This is a counterpart to OVIRT-1959 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ------------=_1522755543-10296-283 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1960:</h3> <pre> Summary: Make pusehr.py able to push Git tags Key: OVIRT-1960 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1960 Project: oVirt - virtualization made easy Issue Type: Improvement Components: pusher.py Reporter: Barak Korren Assignee: infra</pre> <p>{{pusher.py}} knows how to push patches into remote SCMs. WE should also add functionality for pushing tags. More specifically: # It should be possible to request that and arbitrary tag for HEAD be created and pushed. # It should be possible to create and push a tag with information that is gathered and created by {{usrc.py}}. This is a counterpart to OVIRT-1959</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1522755543-10296-283--

1 0

[JIRA] (OVIRT-1959) Make usrc.py support Git tags
by Barak Korren (oVirt JIRA) 03 Apr '18

03 Apr '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1959?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1959: -------------------------------- Description: There are multiple features that could be useful to add to {{usrc.py}} that has to do with Git tags: # *Snap to tag* - when running {{update}} take the latest tagged commit from the branch instead of the latest commit. This could further be enhanced to decide what to do when there is no tagged commit that is newer then what we already have - we can either decide not to update or update to the latest (untagged) commit. # *Copy tag* - when running with {{--commit}} and the upstream commit we're updating into is tagged, store some information somewhere so that if the commit is merged, the CI system could tag it automatically and push that tag. It should be possible to customise the tag we add to allow it to be different but derived from the upstream tag. One possible place to store the needed information is to use a header in the commit message like we do for auto-merge. was:There are multiple features that could be useful to add to usrc.py that has to do with Git tags: > Make usrc.py support Git tags > ----------------------------- > > Key: OVIRT-1959 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1959 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: usrc.py > Reporter: Barak Korren > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

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

03 Apr '18

Change 89737,1 (vdsm) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/89737/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1521/

2 1

Re: [ovirt-users] Install oVirt node without Internet repository
by Pavol Brilla 03 Apr '18

03 Apr '18

Ovirt-node should provide all you need as host on 1 ISO: https://www.ovirt.org/node/ On Mon, Apr 2, 2018 at 12:31 PM, G, Maghesh Kumar (Nokia - IN/Bangalore) < magheshkumar.g(a)nokia.com> wrote: > Hi > > > > Description of problem: > > Cannot add host - install fails & Install oVirt node without Internet repository > > > > Version: Ovirt-4.2 > > Host is installed with RHEL 7.4 > > > > Actual results: > > Host KVM02 installation failed. Command returned failure code 1 during SSH session 'root(a)192.175.2.231' > > > > I found that right now on my oVirt Nodes in my test environment *does not > NOT connect to the internet.*.. > > Basically, i need the offline repository to access from oVirt nodes > without Internet access. > > > > Please guide us how to proceed > > > > Regards, > > Maghesh > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > -- PAVOL BRILLA RHV QUALITY ENGINEER, CLOUD Red Hat Czech Republic, Brno <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0