- Infra - oVirt List Archives

[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) 15 Jul '18

15 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2324?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2324: ------------------------------------- As a workaround, the mount point can be changed, for example: `/var/run/docker.sock:/root/docker.sock` this bind mount works, but I guess that the docker instance inside the container should be configured accordingally. > 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: Task > Reporter: Gal Ben Haim > Assignee: infra > -- 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) 15 Jul '18

15 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2324?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2324: -------------------------------- Epic Link: OVIRT-2246 > 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: Task > Reporter: Gal Ben Haim > Assignee: infra > -- 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) 15 Jul '18

15 Jul '18

Gal Ben Haim created OVIRT-2324: ----------------------------------- Summary: 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: Task Reporter: Gal Ben Haim Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

Build fail stopping docker containers
by Nir Soffer 15 Jul '18

15 Jul '18

Seen this failure today: *16:16:05* Stopping and removing all running containers*16:16:05* Stopping and removing name=unnamed, id=b1d61f20b7fd4746ed83f308ab292b1d53a02de2271965268890b35c1344da04*16:16:40* Stopping and removing name=unnamed, id=22a8ace28d96e469bfc8177ee6afb52d6ca7b4578c27475c92862465253caa2b*16:17:16* Stopping and removing name=unnamed, id=5bab561632b6c179446df56dd3aadf10402989047564202f86c6b3989551820c*16:17:28* Stopping and removing name=unnamed, id=4c04d87ec8b55a774c9e6558a814b944d665b4c0984d6677972285209c5eea7c*16:17:41* Stopping and removing name=unnamed, id=5b40e3237c00cb56897b75fbac500d22b81e53894683ff1a872e4f9e4a48fc1d*16:17:41* Traceback (most recent call last):*16:17:41* File "/home/jenkins/workspace/ovirt-imageio_4.2_check-patch-el7-x86_64/jenkins/scripts/docker_cleanup.py", line 290, in <module>*16:17:41* main()*16:17:41* File "/home/jenkins/workspace/ovirt-imageio_4.2_check-patch-el7-x86_64/jenkins/scripts/docker_cleanup.py", line 34, in main*16:17:41* stop_all_running_containers(client)*16:17:41* File "/home/jenkins/workspace/ovirt-imageio_4.2_check-patch-el7-x86_64/jenkins/scripts/docker_cleanup.py", line 125, in stop_all_running_containers*16:17:41* _remove_container(client, container)*16:17:41* File "/home/jenkins/workspace/ovirt-imageio_4.2_check-patch-el7-x86_64/jenkins/scripts/docker_cleanup.py", line 152, in _remove_container*16:17:41* client.stop(container)*16:17:41* File "/usr/lib/python2.7/site-packages/docker/utils/decorators.py", line 21, in wrapped*16:17:41* return f(self, resource_id, *args, **kwargs)*16:17:41* File "/usr/lib/python2.7/site-packages/docker/api/container.py", line 403, in stop*16:17:42* self._raise_for_status(res)*16:17:42* File "/usr/lib/python2.7/site-packages/docker/client.py", line 173, in _raise_for_status*16:17:42* raise errors.NotFound(e, response, explanation=explanation)*16:17:42* docker.errors.NotFound: 404 Client Error: Not Found ("{"message":"No such container: 5b40e3237c00cb56897b75fbac500d22b81e53894683ff1a872e4f9e4a48fc1d"}") Looks like we need to handle docker.errors.NotFound - it is expected error. https://jenkins.ovirt.org/job/ovirt-imageio_4.2_check-patch-el7-x86_64/551/… Nir

3 3

[CQ]: 92995, 3 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jul '18

15 Jul '18

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

2 1

[CQ]: 8dc18dc (ovirt-ansible-cluster-upgrade) failed "ovirt-master" system tests
by oVirt Jenkins 15 Jul '18

15 Jul '18

Change 8dc18dc (ovirt-ansible-cluster-upgrade) 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-cluster-upgrade/commit/8dc18dccdb9ce… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8664/

2 1

[JIRA] (OVIRT-2320) Adjust 008_basic_ui_sanity.py to work with OST which runs in a container
by Greg Sheremeta (oVirt JIRA) 15 Jul '18

15 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2320?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-2320: --------------------------------------- The docker networking was picky in Jenkins. By name didn't work - I needed to use ip. I only used my own network because the docs set it up that way. If you can get it to work another way, fine by me :) > 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: infra > > 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-2320) Adjust 008_basic_ui_sanity.py to work with OST which runs in a container
by Gal Ben Haim (oVirt JIRA) 15 Jul '18

15 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2320?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2320: ------------------------------------- [~gshereme(a)redhat.com] We are looking to run OST inside a container. One of the challenges is allowing other containers to interact with the OST container. One of the possibilities is to reuse OST container's network in other containers. Is there any reason for creating a custom docker network in the UI tests? > 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: infra > > 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-2323) POC - run OST inside a container in the CI
by Gal Ben Haim (oVirt JIRA) 15 Jul '18

15 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2323?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2323: ------------------------------------- Successfully run {{lago-upgrade-from-release-suite-master-engine}} inside a container on my laptop. > POC - run OST inside a container in the CI > ------------------------------------------ > > Key: OVIRT-2323 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2323 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gal Ben Haim > Assignee: infra > -- 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) 15 Jul '18

15 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2320?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2320: ------------------------------------- Running the Selenium container with {{\-\-network container:OST_CONTAINER_ID}} should work. > 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: infra > > 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