- Infra - oVirt List Archives

[CQ]: 111009, 3 (ovirt-system-tests) failed "ovirt-master" system tests
by oVirt Jenkins 14 Sep '20

14 Sep '20

Change 111009,3 (ovirt-system-tests) 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/111009/3 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/25765/

1 0

[oVirt Jenkins] deploy-to-gated-ovirt-4.3 - Build #502 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 14 Sep '20

14 Sep '20

Build: https://jenkins.ovirt.org/job/deploy-to-gated-ovirt-4.3/502/ Build Name: #502 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

[oVirt Jenkins] cleanup-gated-ovirt-master - Build #274 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Sep '20

13 Sep '20

Build: https://jenkins.ovirt.org/job/cleanup-gated-ovirt-master/274/ Build Name: #274 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

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

13 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/1313//artifact/exported… Cheers, Jenkins

1 0

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

12 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/1312//artifact/exported… Cheers, Jenkins

1 0

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

12 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: 376 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #376 [Milan Zamazal] basic: Disable smartcard temporarily ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.099_aaa-ldap_pytest.test_add_ldap_provider Error Message: ShellError: Command failed with rc=22. Stdout: Stderr: curl: (22) The requested URL returned error: 503 Service Unavailable Stack Trace: prefix = <ovirtlago.prefix.OvirtPrefix object at 0x7fec8f5de710> engine_restart = <function restart at 0x7fec8f4dede8> def test_add_ldap_provider(prefix, engine_restart): engine = prefix.virt_env.engine_vm() machine_389ds = prefix.virt_env.get_vm(HOSTNAME_389DS) answer_file_src = os.path.join( os.environ.get('SUITE'), 'aaa-ldap-answer-file.conf' ) with open(answer_file_src, 'r') as f: content = f.read() content = content.replace('@389DS_IP@', machine_389ds.ip()) with tempfile.NamedTemporaryFile(mode='w', delete=False) as temp: temp.write(content) engine.copy_to(temp.name, '/root/aaa-ldap-answer-file.conf') os.unlink(temp.name) result = machine_389ds.ssh( [ 'systemctl', 'start', 'dirsrv@lago', ], ) assert result.code == 0, \ 'Failed to start LDAP server. Exit code %s' % result.code result = engine.ssh( [ 'ovirt-engine-extension-aaa-ldap-setup', '--config-append=/root/aaa-ldap-answer-file.conf', '--log=/var/log/ovirt-engine-extension-aaa-ldap-setup.log', ], ) assert result.code == 0, \ 'aaa-ldap-setup failed. Exit code is %s' % result.code > engine_restart() ../basic-suite-master/test-scenarios/099_aaa-ldap_pytest.py:78: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ../ost_utils/ost_utils/pytest/fixtures/engine.py:165: in restart engine_download(health_url) ../ost_utils/ost_utils/pytest/fixtures/engine.py:140: in download return shell(args, bytes_output=True) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ args = ['curl', '-fsS', '-m', '10', '--resolve', 'engine:80:192.168.201.4', ...] bytes_output = True, kwargs = {} process = <subprocess.Popen object at 0x7fec91533350>, out = '' err = 'curl: (22) The requested URL returned error: 503 Service Unavailable\n' 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=22. Stdout: E E Stderr: E curl: (22) The requested URL returned error: 503 Service Unavailable ../ost_utils/ost_utils/shell.py:51: ShellError

1 1

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 371 - 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: 371 Build Status: Failure Triggered By: Started by user Parth Dhanjal ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #371 [Milan Zamazal] basic: Disable smartcard temporarily ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.002_bootstrap_pytest.test_verify_add_hosts Error Message: RuntimeError: 1 hosts failed installation: lago-basic-suite-master-host-0: install_failed Stack Trace: engine_api = <ovirtsdk4.Connection object at 0x7f1d8c97ddd0> @order_by(_TEST_LIST) def test_verify_add_hosts(engine_api): hosts_service = engine_api.system_service().hosts_service() hosts_status = hosts_service.list(search='datacenter={}'.format(DC_NAME)) total_hosts = len(hosts_status) dump_hosts = _host_status_to_print(hosts_service, hosts_status) LOGGER.debug('Host status, verify_add_hosts:\n {}'.format(dump_hosts)) testlib.assert_true_within( lambda: _single_host_up(hosts_service, total_hosts), > timeout=constants.ADD_HOST_TIMEOUT ) ../basic-suite-master/test-scenarios/002_bootstrap_pytest.py:467: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib/python2.7/site-packages/ovirtlago/testlib.py:278: in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) /usr/lib/python2.7/site-packages/ovirtlago/testlib.py:234: in assert_equals_within res = func() ../basic-suite-master/test-scenarios/002_bootstrap_pytest.py:466: in <lambda> lambda: _single_host_up(hosts_service, total_hosts), ../basic-suite-master/test-scenarios/002_bootstrap_pytest.py:238: in _single_host_up _check_problematic_hosts(hosts_service) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ hosts_service = <ovirtsdk4.services.HostsService object at 0x7f1d8c99e0d0> def _check_problematic_hosts(hosts_service): problematic_hosts = hosts_service.list(search='datacenter={} AND status != installing and status != initializing and status != up'.format(DC_NAME)) if len(problematic_hosts): dump_hosts = '%s hosts failed installation:\n' % len(problematic_hosts) for host in problematic_hosts: host_service = hosts_service.host_service(host.id) dump_hosts += '%s: %s\n' % (host.name, host_service.get().status) > raise RuntimeError(dump_hosts) E RuntimeError: 1 hosts failed installation: E lago-basic-suite-master-host-0: install_failed ../basic-suite-master/test-scenarios/002_bootstrap_pytest.py:247: RuntimeError

1 4

oVirt infra daily report - unstable production jobs - 1311
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/1311//artifact/exported… Cheers, Jenkins

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 369 - 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: 369 Build Status: Failure Triggered By: Started by user Parth Dhanjal ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #369 [Milan Zamazal] basic: Disable smartcard temporarily ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.002_bootstrap_pytest.test_verify_add_hosts Error Message: RuntimeError: 1 hosts failed installation: lago-basic-suite-master-host-0: install_failed Stack Trace: engine_api = <ovirtsdk4.Connection object at 0x7f34a5ef3dd0> @order_by(_TEST_LIST) def test_verify_add_hosts(engine_api): hosts_service = engine_api.system_service().hosts_service() hosts_status = hosts_service.list(search='datacenter={}'.format(DC_NAME)) total_hosts = len(hosts_status) dump_hosts = _host_status_to_print(hosts_service, hosts_status) LOGGER.debug('Host status, verify_add_hosts:\n {}'.format(dump_hosts)) testlib.assert_true_within( lambda: _single_host_up(hosts_service, total_hosts), > timeout=constants.ADD_HOST_TIMEOUT ) ../basic-suite-master/test-scenarios/002_bootstrap_pytest.py:467: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib/python2.7/site-packages/ovirtlago/testlib.py:278: in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) /usr/lib/python2.7/site-packages/ovirtlago/testlib.py:234: in assert_equals_within res = func() ../basic-suite-master/test-scenarios/002_bootstrap_pytest.py:466: in <lambda> lambda: _single_host_up(hosts_service, total_hosts), ../basic-suite-master/test-scenarios/002_bootstrap_pytest.py:238: in _single_host_up _check_problematic_hosts(hosts_service) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ hosts_service = <ovirtsdk4.services.HostsService object at 0x7f34a62680d0> def _check_problematic_hosts(hosts_service): problematic_hosts = hosts_service.list(search='datacenter={} AND status != installing and status != initializing and status != up'.format(DC_NAME)) if len(problematic_hosts): dump_hosts = '%s hosts failed installation:\n' % len(problematic_hosts) for host in problematic_hosts: host_service = hosts_service.host_service(host.id) dump_hosts += '%s: %s\n' % (host.name, host_service.get().status) > raise RuntimeError(dump_hosts) E RuntimeError: 1 hosts failed installation: E lago-basic-suite-master-host-0: install_failed ../basic-suite-master/test-scenarios/002_bootstrap_pytest.py:247: RuntimeError

1 1

[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 10 Sep '20

10 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

[JIRA] (OVIRT-3010) [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm"
by Ehud Yonasi (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-3010: ------------------------------------ Hey Nir, Yeah, we need to work on a better mechanism. I will create a ticket and discuss it in the infra meeting. Currently, the ovirt release master rpm is back, and soon the 4.3 + 4.2 will be restored. Thanks for the report! On Tue, Sep 8, 2020 at 2:42 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > On Tue, Sep 8, 2020 at 1:14 PM Ehud Yonasi <eyonasi(a)redhat.com> wrote: > >> I found out the root cause was because of space issues in the nightly >> publisher run. >> >> The 3 ovirt publishers ran in together and the jenkins dir did not have >> that capacity. >> >> Currently, I am restoring the ovirt-master snapshot and then 4.3 + 4.2, >> > > Thanks! > > >> plus sent a patch [1] to ensure they will not run in parallel. >> >> [1]: https://gerrit.ovirt.org/111160 >> > > I probably don't understand the change, but it seems that all jobs > will run now at 00:00? > > I think we need to work on a better mechanism for updating the repository. > For example, we can have a symlink the to current repo: > > current -> 200908143754 > > 200908143754/ > repo files... > > 200908143830/ > repo files... > > When creating a new repo, create a new directory. Update the "current" > symlink only > if creating the new repo succeeded. Then delete the previous respo. > > With this the cases when the entire repo or some files are missing are not > possible. > > On Tue, Sep 8, 2020 at 12:13 PM Ehud Yonasi <eyonasi(a)redhat.com> wrote: >> >>> Hey, >>> >>> I am looking into this. >>> Will update with the results I will find. >>> >>> On Tue, Sep 8, 2020 at 12:00 PM Lev Veyde <lveyde(a)redhat.com> wrote: >>> >>>> Hi Nir, >>>> >>>> It looks like the CI job broke it again, breaking 4.2, 4.3 and master >>>> snapshot release RPM. >>>> >>>> I guess it's the same issue we had last time. >>>> >>>> Thanks in advance, >>>> >>>> On Tue, Sep 8, 2020 at 11:45 AM Nir Soffer <nsoffer(a)redhat.com> wrote: >>>> >>>>> On Mon, Sep 7, 2020 at 2:30 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >>>>> > >>>>> > This is the second time, last time there was an issue during a >>>>> nightly job that >>>>> > left the master snapshot repo broken. >>>>> >>>>> This is still broken today. >>>>> >>>>> In the past sending mail to infra-support created a bug, and someone >>>>> was handling >>>>> issue quickly. This seems to be broken now. >>>>> >>>>> We depend on >>>>> http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm >>>>> for development and CI. When the rpm is missing, CI jobs fail, and >>>>> developers cannot >>>>> update their setup. >>>>> >>>>> Please fix it as soon as possible. >>>>> >>>>> > I have 3 failure builds: >>>>> > >>>>> https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7744/ >>>>> > >>>>> https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7751/ >>>>> > >>>>> https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7755/ >>>>> > >>>>> > All seems to fail in: >>>>> > >>>>> > [2020-09-07T10:00:56.163Z] + dnf install -y >>>>> > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm >>>>> > [2020-09-07T10:01:08.524Z] Status code: 403 for >>>>> > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm >>>>> (IP: >>>>> > 66.187.230.40) >>>>> > >>>>> > Checking manually show: >>>>> > >>>>> > $ curl >>>>> https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm >>>>> > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> >>>>> > <html><head> >>>>> > <title>403 Forbidden</title> >>>>> > </head><body> >>>>> > <h1>Forbidden</h1> >>>>> > <p>You don't have permission to access >>>>> /pub/yum-repo/ovirt-release-master.rpm >>>>> > on this server.</p> >>>>> > </body></html> >>>>> > >>>>> > Looking at: >>>>> > https://resources.ovirt.org/pub/yum-repo/ >>>>> > >>>>> > ovirt-elease-master.rpm does not exist. >>>>> > >>>>> > So we have 2 issues: >>>>> > - The file does not exist >>>>> > - We return "403 Forbidden" instead of "404 Not Found" >>>>> >>>>> >>>> >>>> -- >>>> >>>> Lev Veyde >>>> >>>> Senior Software Engineer, RHCE | RHCVA | MCITP >>>> >>>> Red Hat Israel >>>> >>>> <https://www.redhat.com> >>>> >>>> lev(a)redhat.com | lveyde(a)redhat.com >>>> <https://red.ht/sig> >>>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >>>> _______________________________________________ >>>> 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/B7VMLC7JKYSU2… >>>> >>> > [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm" > ------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-3010 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3010 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > This is the second time, last time there was an issue during a nightly job that > left the master snapshot repo broken. > I have 3 failure builds: > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7744/ > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7751/ > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7755/ > All seems to fail in: > [2020-09-07T10:00:56.163Z] + dnf install -y > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > [2020-09-07T10:01:08.524Z] Status code: 403 for > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm (IP: > 66.187.230.40) > Checking manually show: > $ curl https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>403 Forbidden</title> > </head><body> > <h1>Forbidden</h1> > <p>You don't have permission to access /pub/yum-repo/ovirt-release-master.rpm > on this server.</p> > </body></html> > Looking at: > https://resources.ovirt.org/pub/yum-repo/ > ovirt-elease-master.rpm does not exist. > So we have 2 issues: > - The file does not exist > - We return "403 Forbidden" instead of "404 Not Found" -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[JIRA] (OVIRT-3010) [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm"
by Nir Soffer (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-3010: ----------------------------------- On Tue, Sep 8, 2020 at 1:14 PM Ehud Yonasi <eyonasi(a)redhat.com> wrote: > I found out the root cause was because of space issues in the nightly > publisher run. > > The 3 ovirt publishers ran in together and the jenkins dir did not have > that capacity. > > Currently, I am restoring the ovirt-master snapshot and then 4.3 + 4.2, > Thanks! > plus sent a patch [1] to ensure they will not run in parallel. > > [1]: https://gerrit.ovirt.org/111160 > I probably don't understand the change, but it seems that all jobs will run now at 00:00? I think we need to work on a better mechanism for updating the repository. For example, we can have a symlink the to current repo: current -> 200908143754 200908143754/ repo files... 200908143830/ repo files... When creating a new repo, create a new directory. Update the "current" symlink only if creating the new repo succeeded. Then delete the previous respo. With this the cases when the entire repo or some files are missing are not possible. On Tue, Sep 8, 2020 at 12:13 PM Ehud Yonasi <eyonasi(a)redhat.com> wrote: > >> Hey, >> >> I am looking into this. >> Will update with the results I will find. >> >> On Tue, Sep 8, 2020 at 12:00 PM Lev Veyde <lveyde(a)redhat.com> wrote: >> >>> Hi Nir, >>> >>> It looks like the CI job broke it again, breaking 4.2, 4.3 and master >>> snapshot release RPM. >>> >>> I guess it's the same issue we had last time. >>> >>> Thanks in advance, >>> >>> On Tue, Sep 8, 2020 at 11:45 AM Nir Soffer <nsoffer(a)redhat.com> wrote: >>> >>>> On Mon, Sep 7, 2020 at 2:30 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >>>> > >>>> > This is the second time, last time there was an issue during a >>>> nightly job that >>>> > left the master snapshot repo broken. >>>> >>>> This is still broken today. >>>> >>>> In the past sending mail to infra-support created a bug, and someone >>>> was handling >>>> issue quickly. This seems to be broken now. >>>> >>>> We depend on >>>> http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm >>>> for development and CI. When the rpm is missing, CI jobs fail, and >>>> developers cannot >>>> update their setup. >>>> >>>> Please fix it as soon as possible. >>>> >>>> > I have 3 failure builds: >>>> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7744/ >>>> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7751/ >>>> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7755/ >>>> > >>>> > All seems to fail in: >>>> > >>>> > [2020-09-07T10:00:56.163Z] + dnf install -y >>>> > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm >>>> > [2020-09-07T10:01:08.524Z] Status code: 403 for >>>> > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm (IP: >>>> > 66.187.230.40) >>>> > >>>> > Checking manually show: >>>> > >>>> > $ curl >>>> https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm >>>> > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> >>>> > <html><head> >>>> > <title>403 Forbidden</title> >>>> > </head><body> >>>> > <h1>Forbidden</h1> >>>> > <p>You don't have permission to access >>>> /pub/yum-repo/ovirt-release-master.rpm >>>> > on this server.</p> >>>> > </body></html> >>>> > >>>> > Looking at: >>>> > https://resources.ovirt.org/pub/yum-repo/ >>>> > >>>> > ovirt-elease-master.rpm does not exist. >>>> > >>>> > So we have 2 issues: >>>> > - The file does not exist >>>> > - We return "403 Forbidden" instead of "404 Not Found" >>>> >>>> >>> >>> -- >>> >>> Lev Veyde >>> >>> Senior Software Engineer, RHCE | RHCVA | MCITP >>> >>> Red Hat Israel >>> >>> <https://www.redhat.com> >>> >>> lev(a)redhat.com | lveyde(a)redhat.com >>> <https://red.ht/sig> >>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >>> _______________________________________________ >>> 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/B7VMLC7JKYSU2… >>> >> > [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm" > ------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-3010 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3010 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > This is the second time, last time there was an issue during a nightly job that > left the master snapshot repo broken. > I have 3 failure builds: > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7744/ > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7751/ > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7755/ > All seems to fail in: > [2020-09-07T10:00:56.163Z] + dnf install -y > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > [2020-09-07T10:01:08.524Z] Status code: 403 for > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm (IP: > 66.187.230.40) > Checking manually show: > $ curl https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>403 Forbidden</title> > </head><body> > <h1>Forbidden</h1> > <p>You don't have permission to access /pub/yum-repo/ovirt-release-master.rpm > on this server.</p> > </body></html> > Looking at: > https://resources.ovirt.org/pub/yum-repo/ > ovirt-elease-master.rpm does not exist. > So we have 2 issues: > - The file does not exist > - We return "403 Forbidden" instead of "404 Not Found" -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[JIRA] (OVIRT-3010) [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm"
by Ehud Yonasi (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-3010: ------------------------------------ I found out the root cause was because of space issues in the nightly publisher run. The 3 ovirt publishers ran in together and the jenkins dir did not have that capacity. Currently, I am restoring the ovirt-master snapshot and then 4.3 + 4.2, plus sent a patch [1] to ensure they will not run in parallel. [1]: https://gerrit.ovirt.org/111160 On Tue, Sep 8, 2020 at 12:13 PM Ehud Yonasi <eyonasi(a)redhat.com> wrote: > Hey, > > I am looking into this. > Will update with the results I will find. > > On Tue, Sep 8, 2020 at 12:00 PM Lev Veyde <lveyde(a)redhat.com> wrote: > >> Hi Nir, >> >> It looks like the CI job broke it again, breaking 4.2, 4.3 and master >> snapshot release RPM. >> >> I guess it's the same issue we had last time. >> >> Thanks in advance, >> >> On Tue, Sep 8, 2020 at 11:45 AM Nir Soffer <nsoffer(a)redhat.com> wrote: >> >>> On Mon, Sep 7, 2020 at 2:30 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >>> > >>> > This is the second time, last time there was an issue during a nightly >>> job that >>> > left the master snapshot repo broken. >>> >>> This is still broken today. >>> >>> In the past sending mail to infra-support created a bug, and someone >>> was handling >>> issue quickly. This seems to be broken now. >>> >>> We depend on >>> http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm >>> for development and CI. When the rpm is missing, CI jobs fail, and >>> developers cannot >>> update their setup. >>> >>> Please fix it as soon as possible. >>> >>> > I have 3 failure builds: >>> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7744/ >>> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7751/ >>> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7755/ >>> > >>> > All seems to fail in: >>> > >>> > [2020-09-07T10:00:56.163Z] + dnf install -y >>> > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm >>> > [2020-09-07T10:01:08.524Z] Status code: 403 for >>> > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm (IP: >>> > 66.187.230.40) >>> > >>> > Checking manually show: >>> > >>> > $ curl >>> https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm >>> > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> >>> > <html><head> >>> > <title>403 Forbidden</title> >>> > </head><body> >>> > <h1>Forbidden</h1> >>> > <p>You don't have permission to access >>> /pub/yum-repo/ovirt-release-master.rpm >>> > on this server.</p> >>> > </body></html> >>> > >>> > Looking at: >>> > https://resources.ovirt.org/pub/yum-repo/ >>> > >>> > ovirt-elease-master.rpm does not exist. >>> > >>> > So we have 2 issues: >>> > - The file does not exist >>> > - We return "403 Forbidden" instead of "404 Not Found" >>> >>> >> >> -- >> >> Lev Veyde >> >> Senior Software Engineer, RHCE | RHCVA | MCITP >> >> Red Hat Israel >> >> <https://www.redhat.com> >> >> lev(a)redhat.com | lveyde(a)redhat.com >> <https://red.ht/sig> >> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >> _______________________________________________ >> 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/B7VMLC7JKYSU2… >> > > [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm" > ------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-3010 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3010 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > This is the second time, last time there was an issue during a nightly job that > left the master snapshot repo broken. > I have 3 failure builds: > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7744/ > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7751/ > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7755/ > All seems to fail in: > [2020-09-07T10:00:56.163Z] + dnf install -y > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > [2020-09-07T10:01:08.524Z] Status code: 403 for > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm (IP: > 66.187.230.40) > Checking manually show: > $ curl https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>403 Forbidden</title> > </head><body> > <h1>Forbidden</h1> > <p>You don't have permission to access /pub/yum-repo/ovirt-release-master.rpm > on this server.</p> > </body></html> > Looking at: > https://resources.ovirt.org/pub/yum-repo/ > ovirt-elease-master.rpm does not exist. > So we have 2 issues: > - The file does not exist > - We return "403 Forbidden" instead of "404 Not Found" -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[JIRA] (OVIRT-3010) [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm"
by Ehud Yonasi (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-3010: ------------------------------------ Hey, I am looking into this. Will update with the results I will find. On Tue, Sep 8, 2020 at 12:00 PM Lev Veyde <lveyde(a)redhat.com> wrote: > Hi Nir, > > It looks like the CI job broke it again, breaking 4.2, 4.3 and master > snapshot release RPM. > > I guess it's the same issue we had last time. > > Thanks in advance, > > On Tue, Sep 8, 2020 at 11:45 AM Nir Soffer <nsoffer(a)redhat.com> wrote: > >> On Mon, Sep 7, 2020 at 2:30 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >> > >> > This is the second time, last time there was an issue during a nightly >> job that >> > left the master snapshot repo broken. >> >> This is still broken today. >> >> In the past sending mail to infra-support created a bug, and someone >> was handling >> issue quickly. This seems to be broken now. >> >> We depend on >> http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm >> for development and CI. When the rpm is missing, CI jobs fail, and >> developers cannot >> update their setup. >> >> Please fix it as soon as possible. >> >> > I have 3 failure builds: >> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7744/ >> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7751/ >> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7755/ >> > >> > All seems to fail in: >> > >> > [2020-09-07T10:00:56.163Z] + dnf install -y >> > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm >> > [2020-09-07T10:01:08.524Z] Status code: 403 for >> > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm (IP: >> > 66.187.230.40) >> > >> > Checking manually show: >> > >> > $ curl >> https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm >> > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> >> > <html><head> >> > <title>403 Forbidden</title> >> > </head><body> >> > <h1>Forbidden</h1> >> > <p>You don't have permission to access >> /pub/yum-repo/ovirt-release-master.rpm >> > on this server.</p> >> > </body></html> >> > >> > Looking at: >> > https://resources.ovirt.org/pub/yum-repo/ >> > >> > ovirt-elease-master.rpm does not exist. >> > >> > So we have 2 issues: >> > - The file does not exist >> > - We return "403 Forbidden" instead of "404 Not Found" >> >> > > -- > > Lev Veyde > > Senior Software Engineer, RHCE | RHCVA | MCITP > > Red Hat Israel > > <https://www.redhat.com> > > lev(a)redhat.com | lveyde(a)redhat.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > _______________________________________________ > 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/B7VMLC7JKYSU2… > > [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm" > ------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-3010 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3010 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > This is the second time, last time there was an issue during a nightly job that > left the master snapshot repo broken. > I have 3 failure builds: > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7744/ > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7751/ > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7755/ > All seems to fail in: > [2020-09-07T10:00:56.163Z] + dnf install -y > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > [2020-09-07T10:01:08.524Z] Status code: 403 for > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm (IP: > 66.187.230.40) > Checking manually show: > $ curl https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>403 Forbidden</title> > </head><body> > <h1>Forbidden</h1> > <p>You don't have permission to access /pub/yum-repo/ovirt-release-master.rpm > on this server.</p> > </body></html> > Looking at: > https://resources.ovirt.org/pub/yum-repo/ > ovirt-elease-master.rpm does not exist. > So we have 2 issues: > - The file does not exist > - We return "403 Forbidden" instead of "404 Not Found" -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[JIRA] (OVIRT-3010) [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm"
by Lev Veyde (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jira.… ] Lev Veyde commented on OVIRT-3010: ---------------------------------- Hi Nir, It looks like the CI job broke it again, breaking 4.2, 4.3 and master snapshot release RPM. I guess it's the same issue we had last time. Thanks in advance, On Tue, Sep 8, 2020 at 11:45 AM Nir Soffer <nsoffer(a)redhat.com> wrote: > On Mon, Sep 7, 2020 at 2:30 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > > > > This is the second time, last time there was an issue during a nightly > job that > > left the master snapshot repo broken. > > This is still broken today. > > In the past sending mail to infra-support created a bug, and someone > was handling > issue quickly. This seems to be broken now. > > We depend on > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > for development and CI. When the rpm is missing, CI jobs fail, and > developers cannot > update their setup. > > Please fix it as soon as possible. > > > I have 3 failure builds: > > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7744/ > > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7751/ > > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7755/ > > > > All seems to fail in: > > > > [2020-09-07T10:00:56.163Z] + dnf install -y > > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > > [2020-09-07T10:01:08.524Z] Status code: 403 for > > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm (IP: > > 66.187.230.40) > > > > Checking manually show: > > > > $ curl https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > > <html><head> > > <title>403 Forbidden</title> > > </head><body> > > <h1>Forbidden</h1> > > <p>You don't have permission to access > /pub/yum-repo/ovirt-release-master.rpm > > on this server.</p> > > </body></html> > > > > Looking at: > > https://resources.ovirt.org/pub/yum-repo/ > > > > ovirt-elease-master.rpm does not exist. > > > > So we have 2 issues: > > - The file does not exist > > - We return "403 Forbidden" instead of "404 Not Found" > > -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm" > ------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-3010 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3010 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > This is the second time, last time there was an issue during a nightly job that > left the master snapshot repo broken. > I have 3 failure builds: > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7744/ > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7751/ > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7755/ > All seems to fail in: > [2020-09-07T10:00:56.163Z] + dnf install -y > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > [2020-09-07T10:01:08.524Z] Status code: 403 for > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm (IP: > 66.187.230.40) > Checking manually show: > $ curl https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>403 Forbidden</title> > </head><body> > <h1>Forbidden</h1> > <p>You don't have permission to access /pub/yum-repo/ovirt-release-master.rpm > on this server.</p> > </body></html> > Looking at: > https://resources.ovirt.org/pub/yum-repo/ > ovirt-elease-master.rpm does not exist. > So we have 2 issues: > - The file does not exist > - We return "403 Forbidden" instead of "404 Not Found" -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[JIRA] (OVIRT-3010) [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm"
by Anton Marchukov (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-3010: ---------------------------------------- > Begin forwarded message: > > From: Nir Soffer <nsoffer(a)redhat.com> > Subject: Re: [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm" > Date: 8 September 2020 at 10:44:44 CEST > To: infra-support(a)ovirt.org > Cc: devel <devel(a)ovirt.org>, Lev Veyde <lveyde(a)redhat.com>, Anton Marchukov <amarchuk(a)redhat.com>, "Nisan, Tal" <tnisan(a)redhat.com>, Galit Rosenthal <grosenth(a)redhat.com>, Michal Skrivanek <mskrivan(a)redhat.com>, infra <infra(a)ovirt.org> > > On Mon, Sep 7, 2020 at 2:30 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >> >> This is the second time, last time there was an issue during a nightly job that >> left the master snapshot repo broken. > > This is still broken today. > > In the past sending mail to infra-support created a bug, and someone > was handling > issue quickly. This seems to be broken now. > > We depend on http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > for development and CI. When the rpm is missing, CI jobs fail, and > developers cannot > update their setup. > > Please fix it as soon as possible. > >> I have 3 failure builds: >> https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7744/ >> https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7751/ >> https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7755/ >> >> All seems to fail in: >> >> [2020-09-07T10:00:56.163Z] + dnf install -y >> http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm >> [2020-09-07T10:01:08.524Z] Status code: 403 for >> http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm (IP: >> 66.187.230.40) >> >> Checking manually show: >> >> $ curl https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm >> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> >> <html><head> >> <title>403 Forbidden</title> >> </head><body> >> <h1>Forbidden</h1> >> <p>You don't have permission to access /pub/yum-repo/ovirt-release-master.rpm >> on this server.</p> >> </body></html> >> >> Looking at: >> https://resources.ovirt.org/pub/yum-repo/ >> >> ovirt-elease-master.rpm does not exist. >> >> So we have 2 issues: >> - The file does not exist >> - We return "403 Forbidden" instead of "404 Not Found" > -- Anton Marchukov Associate Manager - RHV DevOps - Red Hat > [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm" > ------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-3010 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3010 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > This is the second time, last time there was an issue during a nightly job that > left the master snapshot repo broken. > I have 3 failure builds: > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7744/ > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7751/ > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7755/ > All seems to fail in: > [2020-09-07T10:00:56.163Z] + dnf install -y > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > [2020-09-07T10:01:08.524Z] Status code: 403 for > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm (IP: > 66.187.230.40) > Checking manually show: > $ curl https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>403 Forbidden</title> > </head><body> > <h1>Forbidden</h1> > <p>You don't have permission to access /pub/yum-repo/ovirt-release-master.rpm > on this server.</p> > </body></html> > Looking at: > https://resources.ovirt.org/pub/yum-repo/ > ovirt-elease-master.rpm does not exist. > So we have 2 issues: > - The file does not exist > - We return "403 Forbidden" instead of "404 Not Found" -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0