- Infra - oVirt List Archives

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 366 - Failure!
by jenkins＠jenkins.phx.ovirt.org 11 Sep '20

11 Sep '20

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 366 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #366 [Milan Zamazal] basic: Disable smartcard temporarily ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.100_basic_ui_sanity_pytest.test_login[firefox] Error Message: test setup failure Stack Trace: engine_fqdn = 'engine', engine_ip = '192.168.201.4' @pytest.fixture(scope="session") def hub_url(engine_fqdn, engine_ip): env_url = _env_hub_url() if env_url is not None: yield env_url else: backend = _grid_backend() if backend == "podman": if os_utils.on_centos(8) and os_utils.inside_mock(): pytest.skip("podman doesn't work in mock") hub_port = network_utils.find_free_port(4444, 4544) with podman.grid(engine_fqdn, engine_ip, hub_port=hub_port) as hub_url: yield hub_url elif backend == "docker": > with docker.grid(engine_fqdn, engine_ip) as hub_url: ../ost_utils/ost_utils/pytest/fixtures/selenium/__init__.py:76: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib64/python2.7/contextlib.py:17: in __enter__ return self.gen.next() ../ost_utils/ost_utils/selenium/docker.py:118: in grid with _network(network_name): /usr/lib64/python2.7/contextlib.py:17: in __enter__ return self.gen.next() ../ost_utils/ost_utils/selenium/docker.py:61: in _network shell(["docker", "network", "create", network_name]) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ args = ['docker', 'network', 'create', 'grid'], bytes_output = False kwargs = {}, process = <subprocess.Popen object at 0x7f98b84743d0>, out = '' err = 'Error response from daemon: network with name grid already exists ' def shell(args, bytes_output=False, **kwargs): process = subprocess.Popen(args, stdout=subprocess.PIPE, stderr=subprocess.PIPE, **kwargs) out, err = process.communicate() if not bytes_output: out = out.decode("utf-8") err = err.decode("utf-8") if process.returncode: > raise ShellError(process.returncode, out, err) E ShellError: Command failed with rc=1. Stdout: E E Stderr: E Error response from daemon: network with name grid already exists ../ost_utils/ost_utils/shell.py:51: ShellError

1 1

oVirt infra daily report - unstable production jobs - 1310
by jenkins＠jenkins.phx.ovirt.org 11 Sep '20

11 Sep '20

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

1 0

[JIRA] (OVIRT-2889) OST fails for unreachable repo 'alocalsync'
by Anton Marchukov (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2889?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-2889: ----------------------------------- Resolution: Fixed Status: Done (was: To Do) This was solved a way ago. > OST fails for unreachable repo 'alocalsync' > ------------------------------------------- > > Key: OVIRT-2889 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2889 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Amit Bawer > Assignee: infra > > Hi > OST fails for unreachable repo 'alocalsync', > Seen at > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6706/testReport/bas… > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[JIRA] (OVIRT-2968) Maintaining Selenium Grid Infrastructure Research
by Anton Marchukov (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2968?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-2968: ----------------------------------- Resolution: Won't Do Status: Done (was: To Do) > Maintaining Selenium Grid Infrastructure Research > ------------------------------------------------- > > Key: OVIRT-2968 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2968 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: infra > > During work on OST conversion it was found that we might benefit from > having selenium grid infrastructure [1] to be available as a general > service inside CI. This is basically by design. You can maintain selenium > grid and worker nodes and then expose it over network for general use. > Right now each OST run sets it up on its own each run. So I think having > dedicated and support infrastructure should be beneficial and could be part > of the infra. > Opening this ticket for research and discussion. > [1] https://www.selenium.dev/documentation/en/grid/ > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[JIRA] (OVIRT-2968) Maintaining Selenium Grid Infrastructure Research
by Anton Marchukov (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2968?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2968: ---------------------------------------- Closing since we found the way to use selenium on RHEL8 in Padman when we get rid of mock (in progress). > Maintaining Selenium Grid Infrastructure Research > ------------------------------------------------- > > Key: OVIRT-2968 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2968 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: infra > > During work on OST conversion it was found that we might benefit from > having selenium grid infrastructure [1] to be available as a general > service inside CI. This is basically by design. You can maintain selenium > grid and worker nodes and then expose it over network for general use. > Right now each OST run sets it up on its own each run. So I think having > dedicated and support infrastructure should be beneficial and could be part > of the infra. > Opening this ticket for research and discussion. > [1] https://www.selenium.dev/documentation/en/grid/ > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[JIRA] (OVIRT-3012) Request for permission to run ovirt-system-tests_manual
by Evgheni Dereveanchin (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3012?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-3012: ---------------------------------------- Issue Type: Task (was: By-EMAIL) > Request for permission to run ovirt-system-tests_manual > ------------------------------------------------------- > > Key: OVIRT-3012 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3012 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Pierre Lecomte > Assignee: infra > > Hello, > I have been told by Sandro I should be emailing this email to get access > rights to trigger manual OST jobs. > My login is plecomte on jenkins. > Thanks! > -- > Pierre Lecomte | Virtualization Sustaining Engineering | Oracle -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[JIRA] (OVIRT-3012) Request for permission to run ovirt-system-tests_manual
by Evgheni Dereveanchin (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3012?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-3012: ---------------------------------------- Resolution: Duplicate Status: Done (was: To Do) Closing duplicate > Request for permission to run ovirt-system-tests_manual > ------------------------------------------------------- > > Key: OVIRT-3012 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3012 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Pierre Lecomte > Assignee: infra > > Hello, > I have been told by Sandro I should be emailing this email to get access > rights to trigger manual OST jobs. > My login is plecomte on jenkins. > Thanks! > -- > Pierre Lecomte | Virtualization Sustaining Engineering | Oracle -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[JIRA] (OVIRT-3011) CI cannot find ioprocess package
by Nir Soffer (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3011?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-3011: ----------------------------------- On Wed, Sep 9, 2020 at 10:41 AM Vojtech Juranek <vjuranek(a)redhat.com> wrote: > > Hi, > CI fails quite often with > > Error: Unable to find a match: python3-ioprocess-1.4.1 It was fixed in master and 4.3 today. The issue was an old requirement in automation for ioprocess-1.4.1. Eyal published 1.4.2 2 days ago, and for some reason 1.4.1 was removed from the repos, breaking the requirement. Since we have now copr repo, the builds are available few minutes after merging, there should not be any reason to add such requirements in automation. > > see e.g. [1, 2]. > Can someone please take a look? > Thanks > Vojta > > [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23502 > [2] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23503______________… > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SYN66JCV4GPYS… > CI cannot find ioprocess package > -------------------------------- > > Key: OVIRT-3011 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3011 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Vojtech Juranek > Assignee: infra > Attachments: signature.asc > > > Hi, > CI fails quite often with > Error: Unable to find a match: python3-ioprocess-1.4.1 > see e.g. [1, 2]. > Can someone please take a look? > Thanks > Vojta > [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23502 > [2] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23503 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[JIRA] (OVIRT-3012) Request for permission to run ovirt-system-tests_manual
by Pierre Lecomte (oVirt JIRA) 10 Sep '20

10 Sep '20

Pierre Lecomte created OVIRT-3012: ------------------------------------- Summary: Request for permission to run ovirt-system-tests_manual Key: OVIRT-3012 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3012 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Pierre Lecomte Assignee: infra Hello, I have been told by Sandro I should be emailing this email to get access rights to trigger manual OST jobs. My login is plecomte on jenkins. Thanks! -- Pierre Lecomte | Virtualization Sustaining Engineering | Oracle -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[JIRA] (OVIRT-3011) CI cannot find ioprocess package
by Vojtech Juranek (oVirt JIRA) 10 Sep '20

10 Sep '20

Vojtech Juranek created OVIRT-3011: -------------------------------------- Summary: CI cannot find ioprocess package Key: OVIRT-3011 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3011 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Vojtech Juranek Assignee: infra Hi, CI fails quite often with Error: Unable to find a match: python3-ioprocess-1.4.1 see e.g. [1, 2]. Can someone please take a look? Thanks Vojta [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23502 [2] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23503 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0