July 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2387) Ensure that /var/lib/lago under jenkins slave removed 4.1 jobs+data

by Ehud Yonasi (oVirt JIRA)

Ehud Yonasi created OVIRT-2387: ---------------------------------- Summary: Ensure that /var/lib/lago under jenkins slave removed 4.1 jobs+data Key: OVIRT-2387 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2387 Project: oVirt - virtualization made easy Issue Type: Outage Components: CI client projects, oVirt CI, oVirt Infra Reporter: Ehud Yonasi Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2386) Kubevirt checp-patch logs get truncated

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2386?page=com.atlassian.jir... ] Barak Korren reassigned OVIRT-2386: ----------------------------------- Assignee: Barak Korren (was: infra) > Kubevirt checp-patch logs get truncated > --------------------------------------- > > Key: OVIRT-2386 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2386 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > For some reason, output that kubevirt sends to the stdout_stderr.log gets truncated and is not in the file when then job finishes. The same output can be seens just fine in the jenkins output console. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2386) Kubevirt checp-patch logs get truncated

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2386?page=com.atlassian.jir... ] Barak Korren updated OVIRT-2386: -------------------------------- Epic Link: OVIRT-2339 > Kubevirt checp-patch logs get truncated > --------------------------------------- > > Key: OVIRT-2386 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2386 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > For some reason, output that kubevirt sends to the stdout_stderr.log gets truncated and is not in the file when then job finishes. The same output can be seens just fine in the jenkins output console. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2386) Kubevirt checp-patch logs get truncated

by Barak Korren (oVirt JIRA)

Barak Korren created OVIRT-2386: ----------------------------------- Summary: Kubevirt checp-patch logs get truncated Key: OVIRT-2386 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2386 Project: oVirt - virtualization made easy Issue Type: Bug Components: mock_runner Reporter: Barak Korren Assignee: infra Priority: Highest For some reason, output that kubevirt sends to the stdout_stderr.log gets truncated and is not in the file when then job finishes. The same output can be seens just fine in the jenkins output console. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2385) configure and collect sosreport in ost

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2385?page=com.atlassian.jir... ] Dafna Ron updated OVIRT-2385: ----------------------------- Labels: ost_lago (was: ) > configure and collect sosreport in ost > -------------------------------------- > > Key: OVIRT-2385 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2385 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_lago > > We encounter situations where debugging becomes hard as the machine has frozen and even messages, engine and server logs are no longer written to. > This makes it hard to debug as we no longer have any of the machines and system status is unknown. > I am looking into the reports tool that is used by our customer service to debug customers systems to see if it would also provide further info we do not have at the moment but for now I think adding sosreport from all machines would be a good addition. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2385) configure and collect sosreport in ost

by Dafna Ron (oVirt JIRA)

Dafna Ron created OVIRT-2385: -------------------------------- Summary: configure and collect sosreport in ost Key: OVIRT-2385 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2385 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra We encounter situations where debugging becomes hard as the machine has frozen and even messages, engine and server logs are no longer written to. This makes it hard to debug as we no longer have any of the machines and system status is unknown. I am looking into the reports tool that is used by our customer service to debug customers systems to see if it would also provide further info we do not have at the moment but for now I think adding sosreport from all machines would be a good addition. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 4 months

1
0
0 / 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 398 - Failure!

by jenkins＠jenkins.phx.ovirt.org

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/398/ Build Number: 398 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #398 [Gal Ben Haim] compat: Set "ex" bash flags ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: 143 -------------------- >> begin captured logging << -------------------- cli: DEBUG: signal 15 was caught --------------------- >> end captured logging << --------------------- Stack Trace: 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_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 229, in add_hosts add_hosts_4(prefix) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 273, in add_hosts_4 testlib.assert_true_within(_host_is_up_4, timeout=15*60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 263, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 254, in _host_is_up_4 host_obj = host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 36846, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 54, in wait response = self._connection.wait(self._context) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 496, in wait return self.__wait(context, failed_auth) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 532, in __wait self._multi.select(1.0) File "/usr/lib/python2.7/site-packages/lago/cmd.py", line 922, in exit_handler sys.exit(128 + signum) '143\n-------------------- >> begin captured logging << --------------------\ncli: DEBUG: signal 15 was caught\n--------------------- >> end captured logging << ---------------------'

6 years, 4 months

1
3
0 / 0

[JIRA] (OVIRT-2384) Allow single slot deployment in run_stdci_containers.sh

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2384?page=com.atlassian.jir... ] Daniel Belenky reassigned OVIRT-2384: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Allow single slot deployment in run_stdci_containers.sh > ------------------------------------------------------- > > Key: OVIRT-2384 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2384 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > As an STDCI operator, I want to have the ability to deploy/modify a single slot of the containerized slave so that I won't have to remove all running slaves to modify one of them. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2384) Allow single slot deployment in run_stdci_containers.sh

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2384?page=com.atlassian.jir... ] Daniel Belenky updated OVIRT-2384: ---------------------------------- Epic Link: OVIRT-2326 > Allow single slot deployment in run_stdci_containers.sh > ------------------------------------------------------- > > Key: OVIRT-2384 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2384 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI operator, I want to have the ability to deploy/modify a single slot of the containerized slave so that I won't have to remove all running slaves to modify one of them. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2384) Allow single slot deployment in run_stdci_containers.sh

by Daniel Belenky (oVirt JIRA)

Daniel Belenky created OVIRT-2384: ------------------------------------- Summary: Allow single slot deployment in run_stdci_containers.sh Key: OVIRT-2384 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2384 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Daniel Belenky Assignee: infra As an STDCI operator, I want to have the ability to deploy/modify a single slot of the containerized slave so that I won't have to remove all running slaves to modify one of them. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra July 2018