- Infra - oVirt List Archives

[CQ]: 92835, 2 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 17 Jul '18

17 Jul '18

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

2 1

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 358 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Jul '18

17 Jul '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/358/ Build Number: 358 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #358 [Dafna Ron] ovirt-master: skipping deactivae/activate storage tests ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: Failed to read response: [(<pycurl.Curl object at 0x7fb32362eda8>, 7, 'TCP connection reset by peer')] -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7fb3236095f0> Traceback (most recent call last): 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 510, in __wait raise Error("Failed to read response: {}".format(err_list)) Error: Failed to read response: [(<pycurl.Curl object at 0x7fb32362eda8>, 7, 'TCP connection reset by peer')] --------------------- >> 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 510, in __wait raise Error("Failed to read response: {}".format(err_list)) 'Failed to read response: [(<pycurl.Curl object at 0x7fb32362eda8>, 7, \'TCP connection reset by peer\')]\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7fb3236095f0>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within\n res = func()\n 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\n host_obj = host_service.get()\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 36846, in get\n return self._internal_get(headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 54, in wait\n response = self._connection.wait(self._context)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 496, in wait\n return self.__wait(context, failed_auth)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 510, in __wait\n raise Error("Failed to read response: {}".format(err_list))\nError: Failed to read response: [(<pycurl.Curl object at 0x7fb32362eda8>, 7, \'TCP connection reset by peer\')]\n--------------------- >> end captured logging << ---------------------'

1 1

[JIRA] (OVIRT-2338) resources got stuck
by Dafna Ron (oVirt JIRA) 17 Jul '18

17 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2338?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2338: ----------------------------- Labels: ost_failures ost_infra (was: ) > resources got stuck > ------------------- > > Key: OVIRT-2338 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2338 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Emil Natan > Assignee: infra > Labels: ost_failures, ost_infra > > resources.ovirt.org got stuck. Initially we received different nagios alerts about number of processes and filesystems usage, but the root cause was "Socket timeout after 10 seconds". There was not ssh connectivity, so reset of the VM through the engine UI helped to get it running again. > The issue affected few CQ tests. > Possible improvement could be to set watchdog to automatically reboot the VM if it gets stuck. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

1 0

[JIRA] (OVIRT-2338) resources got stuck
by Emil Natan (oVirt JIRA) 17 Jul '18

17 Jul '18

Emil Natan created OVIRT-2338: --------------------------------- Summary: resources got stuck Key: OVIRT-2338 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2338 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Emil Natan Assignee: infra resources.ovirt.org got stuck. Initially we received different nagios alerts about number of processes and filesystems usage, but the root cause was "Socket timeout after 10 seconds". There was not ssh connectivity, so reset of the VM through the engine UI helped to get it running again. The issue affected few CQ tests. Possible improvement could be to set watchdog to automatically reboot the VM if it gets stuck. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

1 0

[CQ]: 92835, 2 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 17 Jul '18

17 Jul '18

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

2 1

[CQ]: 82352, 28 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Jul '18

17 Jul '18

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

2 1

Build failed in Jenkins: deploy-to_ovirt-4.2_tested #1773
by jenkins＠jenkins.phx.ovirt.org 17 Jul '18

17 Jul '18

See <http://jenkins.ovirt.org/job/deploy-to_ovirt-4.2_tested/1773/display/redire…> ------------------------------------------ Started by upstream project "ovirt-release_4.2_build-artifacts-el7-x86_64" build number 356 originally caused by: Started by timer [EnvInject] - Loading node environment variables. Building remotely on vm0139.workers-phx.ovirt.org (phx fc28 nested) in workspace <http://jenkins.ovirt.org/job/deploy-to_ovirt-4.2_tested/ws/> [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-DupUy9XRUwVy/agent.30722 SSH_AGENT_PID=30724 [ssh-agent] Started. $ ssh-add <http://jenkins.ovirt.org/job/deploy-to_ovirt-4.2_tested/ws/@tmp/private_key…> Identity added: <http://jenkins.ovirt.org/job/deploy-to_ovirt-4.2_tested/ws/@tmp/private_key…> (<http://jenkins.ovirt.org/job/deploy-to_ovirt-4.2_tested/ws/@tmp/private_key…)> [ssh-agent] Using credentials deploy-ovirt-experimental (SSH key for deploying to the tested repo) [deploy-to_ovirt-4.2_tested] $ /bin/bash -xe /tmp/jenkins1093368437180442068.sh + [[ http://jenkins.ovirt.org/job/ovirt-release_4.2_build-artifacts-el7-x86_64/3… == '' ]] + queue_name=ovirt-4.2 + ssh -o StrictHostKeyChecking=no deploy-ovirt-experimental(a)resources.ovirt.org + echo repo-extra-dir:4.2 + echo http://jenkins.ovirt.org/job/ovirt-release_4.2_build-artifacts-el7-x86_64/3… Pseudo-terminal will not be allocated because stdin is not a terminal. ssh_exchange_identification: read: Connection reset by peer Build step 'Execute shell' marked build as failure $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 30724 killed; [ssh-agent] Stopped.

1 1

[JIRA] (OVIRT-2335) Ensure SPICE traffic to PHX engine is not blocked by firewalls
by Barak Korren (oVirt JIRA) 17 Jul '18

17 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2335?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2335: -------------------------------- Epic Link: OVIRT-2337 > Ensure SPICE traffic to PHX engine is not blocked by firewalls > -------------------------------------------------------------- > > Key: OVIRT-2335 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2335 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > In case we get locke out of servers, SPICE is our only option, only it seems to not work at all for now. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

1 0

[JIRA] (OVIRT-2335) Ensure SPICE traffic to PHX engine is not blocked by firewalls
by Barak Korren (oVirt JIRA) 17 Jul '18

17 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2335?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2335: -------------------------------- Epic Link: OVIRT-2337 > Ensure SPICE traffic to PHX engine is not blocked by firewalls > -------------------------------------------------------------- > > Key: OVIRT-2335 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2335 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > In case we get locke out of servers, SPICE is our only option, only it seems to not work at all for now. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

1 0

[JIRA] (OVIRT-2336) Ensure the serial console for production VMs is reacahble
by Barak Korren (oVirt JIRA) 17 Jul '18

17 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2336?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2336: -------------------------------- Epic Link: OVIRT-2337 > Ensure the serial console for production VMs is reacahble > --------------------------------------------------------- > > Key: OVIRT-2336 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2336 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: High > > Make sure everyone can reach the serial console for the production VMs (And know how to do it) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

1 0

[JIRA] (OVIRT-2336) Ensure the serial console for production VMs is reacahble
by Barak Korren (oVirt JIRA) 17 Jul '18

17 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2336?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2336: -------------------------------- Epic Link: OVIRT-2337 > Ensure the serial console for production VMs is reacahble > --------------------------------------------------------- > > Key: OVIRT-2336 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2336 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: High > > Make sure everyone can reach the serial console for the production VMs (And know how to do it) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

1 0

[CQ]: 92782, 3 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Jul '18

17 Jul '18

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

2 1

[JIRA] (OVIRT-2334) Enable spice+VNC and virtio console on all production VMs in PHX
by Barak Korren (oVirt JIRA) 17 Jul '18

17 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2334?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2334: -------------------------------- Epic Link: OVIRT-2337 > Enable spice+VNC and virtio console on all production VMs in PHX > ----------------------------------------------------------------- > > Key: OVIRT-2334 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2334 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > We need more alternative ways to reach oVirt infra in case we get locket out of VMs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

1 0

[JIRA] (OVIRT-2334) Enable spice+VNC and virtio console on all production VMs in PHX
by Barak Korren (oVirt JIRA) 17 Jul '18

17 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2334?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2334: -------------------------------- Epic Link: OVIRT-2337 > Enable spice+VNC and virtio console on all production VMs in PHX > ----------------------------------------------------------------- > > Key: OVIRT-2334 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2334 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > We need more alternative ways to reach oVirt infra in case we get locket out of VMs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

1 0

[JIRA] (OVIRT-2337) Ensure emergency access to PHC production VMs
by Barak Korren (oVirt JIRA) 17 Jul '18

17 Jul '18

Barak Korren created OVIRT-2337: ----------------------------------- Summary: Ensure emergency access to PHC production VMs Key: OVIRT-2337 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2337 Project: oVirt - virtualization made easy Issue Type: Epic Components: oVirt Infra Reporter: Barak Korren Assignee: infra Priority: High Make sure that in case of malfunction we have multiple fail-safe ways of gaining access to the PHX production VMs to resolve issues. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

1 0

[JIRA] (OVIRT-2334) Enable spice+VNC and virtio console on all production VMs in PHX
by Barak Korren (oVirt JIRA) 17 Jul '18

17 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2334?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2334: -------------------------------- Issue Type: Improvement (was: Bug) > Enable spice+VNC and virtio console on all production VMs in PHX > ----------------------------------------------------------------- > > Key: OVIRT-2334 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2334 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > We need more alternative ways to reach oVirt infra in case we get locket out of VMs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

1 0

[JIRA] (OVIRT-2336) Ensure the serial console for production VMs is reacahble
by Barak Korren (oVirt JIRA) 17 Jul '18

17 Jul '18

Barak Korren created OVIRT-2336: ----------------------------------- Summary: Ensure the serial console for production VMs is reacahble Key: OVIRT-2336 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2336 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt Infra Reporter: Barak Korren Assignee: infra Priority: High Make sure everyone can reach the serial console for the production VMs (And know how to do it) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

1 0

[JIRA] (OVIRT-2335) Ensure SPICE traffic to PHX engine is not blocked by firewalls
by Barak Korren (oVirt JIRA) 17 Jul '18

17 Jul '18

Barak Korren created OVIRT-2335: ----------------------------------- Summary: Ensure SPICE traffic to PHX engine is not blocked by firewalls Key: OVIRT-2335 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2335 Project: oVirt - virtualization made easy Issue Type: Outage Components: oVirt Infra Reporter: Barak Korren Assignee: infra Priority: Highest In case we get locke out of servers, SPICE is our only option, only it seems to not work at all for now. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

1 0

[JIRA] (OVIRT-2334) Enable spice+VNC and virtio console on all production VMs in PHX
by Barak Korren (oVirt JIRA) 17 Jul '18

17 Jul '18

Barak Korren created OVIRT-2334: ----------------------------------- Summary: Enable spice+VNC and virtio console on all production VMs in PHX Key: OVIRT-2334 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2334 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt Infra Reporter: Barak Korren Assignee: infra Priority: Highest We need more alternative ways to reach oVirt infra in case we get locket out of VMs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

1 0

[CQ]: 92836, 2 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests
by oVirt Jenkins 17 Jul '18

17 Jul '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 577 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Jul '18

17 Jul '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/577/ Build Number: 577 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #577 [Dafna Ron] ovirt-master: skipping deactivae/activate storage tests ----------------- Failed Tests: ----------------- No tests ran.

1 1

oVirt infra daily report - unstable production jobs - 523
by jenkins＠jenkins.phx.ovirt.org 17 Jul '18

17 Jul '18

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/523//artifact/exported-a… Cheers, Jenkins

1 0

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

16 Jul '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/196/ Build Number: 196 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #196 [Dafna Ron] ovirt-master: skipping deactivae/activate storage tests ----------------- Failed Tests: ----------------- No tests ran.

1 1

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

16 Jul '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/131/ Build Number: 131 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #131 [Dafna Ron] ovirt-master: skipping deactivae/activate storage tests ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2264) Cannot deactivate Storage while there are running tasks on this Storage
by Dafna Ron (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2264?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2264: ---------------------------------- [~derez(a)redhat.com] the tests are ci test which are managed by the developers. the tests were written by Kaul but you guys are actually the ones that need to manage the tests/add more tests/improve on the tests. you can download ovirt-system-tests project and look at the current tests including the storage tests and get answers to the questions above :) As for the running tasks list, I think that perhaps you should add that as a line in the tests before the exit on failure? I don't think that we should add this to lago as the tests should be fixed to not exit on running tasks. > Cannot deactivate Storage while there are running tasks on this Storage > ----------------------------------------------------------------------- > > Key: OVIRT-2264 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2264 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > we failed test: 007_sd_reattach.deactivate_storage_domain in vdsm project with error: Cannot deactivate Storage while there are running tasks on this Storage. -Please wait until tasks will finish and try again.]". HTTP response code is 409. > I am opening this as a race in case something changed in OST tests which would cause this to repeat. > https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2506 > https://gerrit.ovirt.org/#/c/92313/2 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2264) Cannot deactivate Storage while there are running tasks on this Storage
by Daniel Erez (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2264?page=com.atlassian.jira.… ] Daniel Erez commented on OVIRT-2264: ------------------------------------ * Is it possible to get a list of running tasks after the failure (i.e. dump of 'command_entities' table)? * Is the script running any tasks in parallel? Or, are you ensuring that the execution steps run tasks consequently? Any 'sleep' period between each step? > Cannot deactivate Storage while there are running tasks on this Storage > ----------------------------------------------------------------------- > > Key: OVIRT-2264 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2264 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > we failed test: 007_sd_reattach.deactivate_storage_domain in vdsm project with error: Cannot deactivate Storage while there are running tasks on this Storage. -Please wait until tasks will finish and try again.]". HTTP response code is 409. > I am opening this as a race in case something changed in OST tests which would cause this to repeat. > https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2506 > https://gerrit.ovirt.org/#/c/92313/2 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2333) Ensure that the docker service inside stdci container is masked
by Gal Ben Haim (oVirt JIRA) 16 Jul '18

16 Jul '18

Gal Ben Haim created OVIRT-2333: ----------------------------------- Summary: Ensure that the docker service inside stdci container is masked Key: OVIRT-2333 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2333 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gal Ben Haim Assignee: infra Since we run systemd inside the stdci container, systemd will try to start docker when the container starts. This action can cause unexpected results, because we mount the host's docker.sock inside the containers /var/run/docker.sock -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2333) Ensure that the docker service inside stdci container is masked
by Gal Ben Haim (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2333?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2333: -------------------------------- Epic Link: OVIRT-2326 > Ensure that the docker service inside stdci container is masked > --------------------------------------------------------------- > > Key: OVIRT-2333 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2333 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gal Ben Haim > Assignee: infra > Labels: POC > > Since we run systemd inside the stdci container, systemd will try to start docker when the container starts. > This action can cause unexpected results, because we mount the host's docker.sock inside the containers > /var/run/docker.sock -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2332) check-patch is failing on 010_local_mainentance.local_maintenance
by Dafna Ron (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2332?page=com.atlassian.jira.… ] Dafna Ron reassigned OVIRT-2332: -------------------------------- Assignee: Dafna Ron (was: infra) > check-patch is failing on 010_local_mainentance.local_maintenance > ----------------------------------------------------------------- > > Key: OVIRT-2332 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2332 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Dafna Ron > Labels: ost_failures, ost_lago > > New test was merged to HE and is failing my check-patch. > failure: http://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1489/t… > I will add a patch to skip test until its stable. > error: https://pastebin.com/9vVMRLM3 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2332) check-patch is failing on 010_local_mainentance.local_maintenance
by Dafna Ron (oVirt JIRA) 16 Jul '18

16 Jul '18

Dafna Ron created OVIRT-2332: -------------------------------- Summary: check-patch is failing on 010_local_mainentance.local_maintenance Key: OVIRT-2332 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2332 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra New test was merged to HE and is failing my check-patch. failure: http://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1489/t… I will add a patch to skip test until its stable. error: https://pastebin.com/9vVMRLM3 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2331) Build an STDCI container
by Gal Ben Haim (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2331?page=com.atlassian.jira.… ] Gal Ben Haim reassigned OVIRT-2331: ----------------------------------- Assignee: Daniel Belenky (was: infra) > Build an STDCI container > ------------------------ > > Key: OVIRT-2331 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2331 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: Daniel Belenky > Labels: POC > > Create a Dockerfile that builds a STDCI container ready to run mock_runner, lago and OST. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2324) Failed to mount docker.sock to "/var/run/docker.sock" in a container which runs systemd
by Gal Ben Haim (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2324?page=com.atlassian.jira.… ] Gal Ben Haim reassigned OVIRT-2324: ----------------------------------- Assignee: Gal Ben Haim (was: infra) > Failed to mount docker.sock to "/var/run/docker.sock" in a container which runs systemd > --------------------------------------------------------------------------------------- > > Key: OVIRT-2324 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2324 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gal Ben Haim > Assignee: Gal Ben Haim > Labels: POC > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2320) Adjust 008_basic_ui_sanity.py to work with OST which runs in a container
by Gal Ben Haim (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2320?page=com.atlassian.jira.… ] Gal Ben Haim reassigned OVIRT-2320: ----------------------------------- Assignee: Gal Ben Haim (was: infra) > Adjust 008_basic_ui_sanity.py to work with OST which runs in a container > ------------------------------------------------------------------------ > > Key: OVIRT-2320 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2320 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: Gal Ben Haim > > The UI tests use a container for running Selenium. > We need to make sure that lago's network bridge is visible to the Selenium container since it > needs to connect to the engine UI. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2329) Connect stdci container to Jenkins via JNLP
by Barak Korren (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2329?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-2329 at 7/16/18 12:34 PM: --------------------------------------------------------------- Since you're probably gonna have to write a systemd unit file to start up the JNLP client, here is some similar work I did before to make puppet do that for the stateless slaves: https://github.com/ifireball/puppet-jenkins/commit/7575ca8d73208a7dc43996ad… was (Author: bkorren(a)redhat.com) Sine you're probably gonna have to write a systemd unit file to start up the JNLP client, here is some similar work I did before to make puppet do that for the stateless slaves: https://github.com/ifireball/puppet-jenkins/commit/7575ca8d73208a7dc43996ad… > Connect stdci container to Jenkins via JNLP > ------------------------------------------- > > Key: OVIRT-2329 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2329 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > In order to utilize stdci containers as Jenkins slaves, we need to run the JNLP service -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2315) /var/lib/lago/subnets shouldn't be shared between lago containers
by Gal Ben Haim (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2315?page=com.atlassian.jira.… ] Gal Ben Haim reassigned OVIRT-2315: ----------------------------------- Assignee: Daniel Belenky (was: infra) > /var/lib/lago/subnets shouldn't be shared between lago containers > ----------------------------------------------------------------- > > Key: OVIRT-2315 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2315 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gal Ben Haim > Assignee: Daniel Belenky > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2329) Connect stdci container to Jenkins via JNLP
by Barak Korren (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2329?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2329: ------------------------------------- Sine you're probably gonna have to write a systemd unit file to start up the JNLP client, here is some similar work I did before to make puppet do that for the stateless slaves: https://github.com/ifireball/puppet-jenkins/commit/7575ca8d73208a7dc43996ad… > Connect stdci container to Jenkins via JNLP > ------------------------------------------- > > Key: OVIRT-2329 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2329 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > In order to utilize stdci containers as Jenkins slaves, we need to run the JNLP service -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2331) Build an STDCI container
by Gal Ben Haim (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2331?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2331: ------------------------------------- Initial PR for building Lago container. You can use this to see how to build systemd container, and what are the required mounts for lago. > Build an STDCI container > ------------------------ > > Key: OVIRT-2331 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2331 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > Labels: POC > > Create a Dockerfile that builds a STDCI container ready to run mock_runner, lago and OST. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2330) Host specific resource allocation for stdci containers
by Barak Korren (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2330?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2330: ------------------------------------- To keep things simple lets just make each container the a round up of the RAM needed by the biggest suit and then split the total RAM in the host between such containers > Host specific resource allocation for stdci containers > ------------------------------------------------------ > > Key: OVIRT-2330 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2330 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > To maximize the utilization of stdci containers, we need a mechanism that can decide how much RAM and CPU each stdci container gets and how many stdci containers we can run on that host -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2331) Build an STDCI container
by Daniel Belenky (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2331?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2331: ---------------------------------- Labels: POC (was: ) > Build an STDCI container > ------------------------ > > Key: OVIRT-2331 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2331 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > Labels: POC > > Create a Dockerfile that builds a STDCI container ready to run mock_runner, lago and OST. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2331) Build an STDCI container
by Daniel Belenky (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2331?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2331: ---------------------------------- Description: Create a Dockerfile that builds a STDCI container ready to run mock_runner, lago and OST. > Build an STDCI container > ------------------------ > > Key: OVIRT-2331 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2331 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > Create a Dockerfile that builds a STDCI container ready to run mock_runner, lago and OST. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2331) Build an STDCI container
by Daniel Belenky (oVirt JIRA) 16 Jul '18

16 Jul '18

Daniel Belenky created OVIRT-2331: ------------------------------------- Summary: Build an STDCI container Key: OVIRT-2331 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2331 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Daniel Belenky Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2331) Build an STDCI container
by Daniel Belenky (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2331?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2331: ---------------------------------- Epic Link: OVIRT-2326 > Build an STDCI container > ------------------------ > > Key: OVIRT-2331 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2331 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2330) Host specific resource allocation for stdci containers
by Daniel Belenky (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2330?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2330: ---------------------------------- Description: To maximize the utilization of stdci containers, we need a mechanism that can decide how much RAM and CPU each stdci container gets and how many stdci containers we can run on that host > Host specific resource allocation for stdci containers > ------------------------------------------------------ > > Key: OVIRT-2330 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2330 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > To maximize the utilization of stdci containers, we need a mechanism that can decide how much RAM and CPU each stdci container gets and how many stdci containers we can run on that host -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2327) Connect user defined container to stdci container network
by Gal Ben Haim (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2327?page=com.atlassian.jira.… ] Gal Ben Haim reassigned OVIRT-2327: ----------------------------------- Assignee: Gal Ben Haim (was: infra) > Connect user defined container to stdci container network > --------------------------------------------------------- > > Key: OVIRT-2327 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2327 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gal Ben Haim > Assignee: Gal Ben Haim > Labels: POC > > In the stdci container, add an env variable which contains the stdci container name. > This env variable can be used later to connect user created containers to stdci container network by using `--network container:NAME` -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2327) Connect user defined container to stdci container network
by Gal Ben Haim (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2327?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2327: -------------------------------- Description: In the stdci container, add an env variable which contains the stdci container name. This env variable can be used later to connect user created containers to stdci container network by using `--network container:NAME` was: In the stdci container, add an env variable which contains the stdci container name. This env variable can be used later to connect user created containers to stdci container network by using ` --network container:NAME1 ` > Connect user defined container to stdci container network > --------------------------------------------------------- > > Key: OVIRT-2327 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2327 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gal Ben Haim > Assignee: infra > Labels: POC > > In the stdci container, add an env variable which contains the stdci container name. > This env variable can be used later to connect user created containers to stdci container network by using `--network container:NAME` -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2327) Connect user defined container to stdci container network
by Gal Ben Haim (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2327?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2327: -------------------------------- Description: In the stdci container, add an env variable which contains the stdci container name. This env variable can be used later to connect user created containers to stdci container network by using ` --network container:NAME1 ` was: In the stdci container, add an env variable which contains the stdci container name. This env variable can be used later to connect user created containers to stdci container network by using --network container:NAME1. {panel:title=My title} Some text with a title {panel} > Connect user defined container to stdci container network > --------------------------------------------------------- > > Key: OVIRT-2327 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2327 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gal Ben Haim > Assignee: infra > Labels: POC > > In the stdci container, add an env variable which contains the stdci container name. > This env variable can be used later to connect user created containers to stdci container network by using ` --network container:NAME1 ` -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2327) Connect user defined container to stdci container network
by Gal Ben Haim (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2327?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2327: -------------------------------- Description: In the stdci container, add an env variable which contains the stdci container name. This env variable can be used later to connect user created containers to stdci container network by using --network container:NAME1. {panel:title=My title} Some text with a title {panel} was: In the stdci container, add an env variable which contains the stdci container name. This env variable can be used later to connect user created containers to stdci container network by using `--network container:NAME1`. > Connect user defined container to stdci container network > --------------------------------------------------------- > > Key: OVIRT-2327 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2327 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gal Ben Haim > Assignee: infra > Labels: POC > > In the stdci container, add an env variable which contains the stdci container name. > This env variable can be used later to connect user created containers to stdci container network by using --network container:NAME1. > {panel:title=My title} > Some text with a title > {panel} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2327) Connect user defined container to stdci container network
by Gal Ben Haim (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2327?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2327: -------------------------------- Description: In the stdci container, add an env variable which contains the stdci container name. This env variable can be used later to connect user created containers to stdci container network by using `--network container:NAME1`. was:In order to connect > Connect user defined container to stdci container network > --------------------------------------------------------- > > Key: OVIRT-2327 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2327 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gal Ben Haim > Assignee: infra > Labels: POC > > In the stdci container, add an env variable which contains the stdci container name. > This env variable can be used later to connect user created containers to stdci container network by using `--network container:NAME1`. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2330) Host specific resource allocation for stdci containers
by Daniel Belenky (oVirt JIRA) 16 Jul '18

16 Jul '18

Daniel Belenky created OVIRT-2330: ------------------------------------- Summary: Host specific resource allocation for stdci containers Key: OVIRT-2330 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2330 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Daniel Belenky Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2330) Host specific resource allocation for stdci containers
by Daniel Belenky (oVirt JIRA) 16 Jul '18

16 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2330?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2330: ---------------------------------- Epic Link: OVIRT-2326 > Host specific resource allocation for stdci containers > ------------------------------------------------------ > > Key: OVIRT-2330 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2330 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0