October 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue

by Gal Ben Haim (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jir... ] Gal Ben Haim commented on OVIRT-2556: ------------------------------------- [~lbednar] FYI > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roman Mohr > Assignee: infra > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//a... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

6 years

1
0
0 / 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue

by Gal Ben Haim (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jir... ] Gal Ben Haim commented on OVIRT-2556: ------------------------------------- I've killed the old STDCI container and spawned a new one instead. > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roman Mohr > Assignee: infra > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//a... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

6 years

1
0
0 / 0

[JIRA] (OVIRT-2555) failures on ovirt-master failed due to access to resources

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2555?page=com.atlassian.jir... ] Evgheni Dereveanchin reassigned OVIRT-2555: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > failures on ovirt-master failed due to access to resources > ----------------------------------------------------------- > > Key: OVIRT-2555 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2555 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Evgheni Dereveanchin > Labels: ost_failures, ost_infra > > 21:38:01 [upgrade-from-release-suite.el7.x86_64] RuntimeError: Failed to run reposync 3 times for repoid: ovirt-4.2-tested-el7, aborting. > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10896/ > [~ederevea] can you please take a look to see if we have issues with the server? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

6 years

1
0
0 / 0

[CQ]: 95003, 3 (pthreading) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

6 years

1
0
0 / 0

[JIRA] (OVIRT-2555) failures on ovirt-master failed due to access to resources

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2555?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2555: ---------------------------------- I was able to wget and repoquery the package: https://pastebin.com/d0ALuqGF > failures on ovirt-master failed due to access to resources > ----------------------------------------------------------- > > Key: OVIRT-2555 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2555 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra > > 21:38:01 [upgrade-from-release-suite.el7.x86_64] RuntimeError: Failed to run reposync 3 times for repoid: ovirt-4.2-tested-el7, aborting. > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10896/ > [~ederevea] can you please take a look to see if we have issues with the server? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

6 years

1
0
0 / 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue

by Roman Mohr (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jir... ] Roman Mohr commented on OVIRT-2556: ----------------------------------- Ok, let me see if it looks better now. For reference here a very bad run https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2347/ar... from https://github.com/kubevirt/kubevirt/pull/1627. Retriggered test runs there now. > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roman Mohr > Assignee: infra > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//a... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

6 years

1
0
0 / 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue

by Gal Ben Haim (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jir... ] Gal Ben Haim commented on OVIRT-2556: ------------------------------------- All the jobs that failed run on `ovirt-srv04.phx.ovirt.org-container-1`. For the meanwhile, I marked this slave offline in Jenkins. Looks like the docker daemon in this slave runs correctly, so further investigation is needed. > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roman Mohr > Assignee: infra > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//a... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

6 years

1
0
0 / 0

[CQ]: 95058,2 (cockpit-ovirt) failed "ovirt-master" system tests

by oVirt Jenkins

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

6 years

2
1
0 / 0

[JIRA] (OVIRT-2555) failures on ovirt-master failed due to access to resources

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2555?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2555: ---------------------------------- https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10903/ > failures on ovirt-master failed due to access to resources > ----------------------------------------------------------- > > Key: OVIRT-2555 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2555 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra > > 21:38:01 [upgrade-from-release-suite.el7.x86_64] RuntimeError: Failed to run reposync 3 times for repoid: ovirt-4.2-tested-el7, aborting. > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10896/ > [~ederevea] can you please take a look to see if we have issues with the server? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

6 years

1
0
0 / 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue

by Roman Mohr (oVirt JIRA)

Roman Mohr created OVIRT-2556: --------------------------------- Summary: kubevirt test runs and nested docker issue Key: OVIRT-2556 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Roman Mohr Assignee: infra Hi, we see a lot of tests which fail with during the setup [1] : ``` /usr/bin/docker-current: Error response from daemon: grpc: the connection is unavailable. time="2018-10-23T07:17:55Z" level=error msg="error getting events from daemon: context canceled" ``` It looks like the docker daemon may not run properly. Best Regards, Roman [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//a... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

6 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra October 2018